Ok, So I thought I would post this guide to installing ubuntu 14.04 on the Pipo W2. This guide might help on some of the similar tablets out there too, like the voyo a1 mini. But I can't be certain about the others
Also, to give credit where credit is due, this guide is mostly adapted with little adaptation from the following guides:
http://asus-t100-ubuntu.blogspot.com/
http://linuxnorth.wordpress.com/2014/08/23/installing-linux-on-the-asus-transformer-book-t100/
and work on wifi wouldnt be possible without help on the ubuntu forums
http://ubuntuforums.org/showthread.php?t=2249936&p=13151763#post13151763
and the wifi drivers were posted for the rlt8723bs by this guy here
http://www.hadess.net/2014/09/and-now-for-some-hardware-onda-v975w.html
First the information as to what works, and what doesn't . As of 11/02/2014 stock ubuntu 14.04 works, the touchscreen works. However wifi, sound, bluetooth, suspend, hibernation, power button, volume buttons, and the micro sd card do not.
Updating to newer kernels changes what works and what doesn't. I was able to get wifi working on kernels 3.16.2 and the power button, and volume buttons, but the touchscreen didn't work on 3.16.2 on kernels 3.17.0 and 3.17.1 I was able to get wifi working, and the touchscreen works, but the volume buttons and power button didn't. you can still boot up with these later kernels, but it's not as easy. I had to go into ubuntu advanced options and boot to recovery for each kernel, then from the recovery menu boot to desktop. A bit of a pain. I think it's a graphics related problem, and I'm working on it, but as of this writing, the kernels I tested from 3.15.x on wouldn't boot without this. (if they booted at all, 3.18.rc2 didnt boot at all)
I am still testing various kernels, to see which one seems the most stable and enables the most features I will update this as new information is worked out.
Ok, starting. Part 1. The Prep work.
--------------------------------------------------------------------------------------------------------------------
Things you will need. A USB hub, a USB keyboard, USB wireless adapter, (or USB LAN adapter) and a mouse. (or trackball) And a USB thumbdrive of course. Without these things, you wont be able to complete the installation easily. Plug them all in, and connect them to the tablet.
Download An ubuntu 14.04.1 lts image (you can substitute ubuntu gnome, 14.04.1 lts, or lubuntu 14.04.1 lts image etc) here's a link to Ubuntu though. you can do this on your tablet, or your desktop. up to you.
http://www.ubuntu.com/download/desktop
Select 32 bit. (NOT AMD64) and click on download, then unless you wish to donate, click on the link that says "not now, continue to the download"
now download Rufus from here
http://rufus.akeo.ie/ and use rufus to install the ISO image on your thumbdrive by clicking on the disk icon next to ISO image near the bottom, and selecting the ubuntu-14.04.1-desktop-i386.iso file (or ubuntu-gnome-14.04.1-desktop-i386.iso or whatever flavor you downloaded) The top option on the rufus menu should automaticly list the thumbdrive, if it doesnt, select the thumbdrive unless you want to screw up whatever drive it's pointing at. (you might be able to make your system unbootable if you don't do this carefully so PAY ATTENTION) Is it listing your thumbdrive? if so, click on start on rufus and let it finish.
now you need to download this file here: https://drive.google.com/folderview...&usp=sharing&tid=0B9C1WK1FQhjfcXNrbzN6djQzajg
Leaving the thumbdrive in, unzip the unpackit.tar.gz file to the thumbdrive root directory, and overwrite all files. when you are done, if you did this on your desktop, safely remove the thumbdrive and plug it into the hub connected to your tablet. if you did this with your tablet, leave it plugged in and continue.
Now, for the windows setup.
First, get to control panel. (you can access it by pressing the windows key to get to the start menu, then going to PC settings, and selecting control panel) click the view to small icons, then click on Power Options. Next click on "Choose what the power button does" and from the next menu, click on "change settings that are currently unavailable"
now scroll down and uncheck the box that says "turn on fast startup" then save.
IMPORTANT NOTE: if you want to screw up windows, so that it wont boot, do the next step in a hurry and pay little attention to what you are doing.
Next you need to set up up some space for Ubuntu. (NOTE: you must have 8-10GB or so empty space on windows partition first, so if you don't have 8-10GB free, go delete some things until you have enough space free.) Ready? Ok you need disk management. go to your desktop then right click on on the start button. and select Disk Management from the menu Expand the window so you can see what you are doing, and right click on "Windows (C select "Shrink Volume" from the list. You will see a window that lists
"Total size before shrink in MB"
"Size of available shrink space in MB"
"Enter the amount of space to shrink in MB"
"Total size after shrink in MB"
Now, using the "Enter the amount of space to shrink in MB" option, type in 10000 or so, (8000 works too) to shrink the volume by 10 gb or 8gb (yes I know it's overly rounded, forgive my OCD) and leave the space as unallocated. do NOT shrink to the max it will let you. always give windows some space to work with.
IMPORTANT NOTE: If you shrink the volume by more then the free space, you will probably screw up your windows installation. I am NOT going to help you figure out how to fix windows, if you ignored these warnings and screw it up. Mostly because I haven't the faintest idea how to fix your windows installation if you shrink the volume too much.
Next eject any Micro SD card you have in the tablet, and pull it out.
Lastly for windows side of things, go back to your desktop, and again right click the start menu, open the shut down options list, then hold shift down and click on restart
You should now be faced with a blue screen with several options, click on "Use a Device" then select "UEFI:Removable Device" and allow the tablet to restart. it will boot back up to windows, but now you should have the USB drive in your UEFI settings boot options. Power the tablet down, all the way, and this time, when you see it start to boot up, press f7 over and over and over until you see the boot option menu, select your thumbdrive and hit enter.
You should be faced with the Grub menu now, press e to edit, and arrow over to where it says video=VGA-1:1368x768e delete the 1368x768 and replace it with 800x1280 now the end of that line should say:
video=VGA-1:800x1280e reboot=pci,force
then hit f10 to boot. it should take a few min, but boot to desktop, if it doesnt, power off the tablet by holding down the power button for 12 seconds, and try again. If it doesn't boot and just errors with rpmb timeout errors for more then 5 min, just try again. (and unplug anything but the keyboard and usb thumbdrive from your hub until you reach desktop.
Once you hit desktop, wait a good 15 seconds before touching anything, otherwise kernel panic hits sometimes.
Once you are at your desktop, click in the upper right corner and go to system settings, and go to Brightness & Lock and uncheck the box that says "dim screen to save power" and change "Turn screen off when inactive for" to never.
Next exit that screen and connect to your wifi or make certain your wired network is working. check to make certain you have internet access. then hit ctrl-alt-t to open a terminal. type the following
sudo umount /dev/mmcblk0p*
now kill that window. you are now ready, FINALLY ready to install ubuntu.
Part 2 : Installing Ubuntu
-------------------------------------------------------------------------------------------------------------------------------------
Click on the icon to install ubuntu, then when the window pops up, select your language and continue
On the next window check both boxes to install updates and third party software, (third party is probably optional) and click continue
Now, we wait. wait wait wait and wait. the next window will take quite a while to pop up. probably rpmb timeout errors as it checks all the drives. might be 30 min or so. no way to speed this up.
Now PAY ATTENTION: Next window, click on the last option that says "Something Else" if you click standard install, you can kiss windows goodbye.
Following window, will list all your drives. do you see that 10000 or 8000 MB of space you created earlier? nice and round and most importantly, easily recognizable? click on that it should say "free space", then click on the "+" button., when the create partition box pops up, select logical instead of primary, and select the mount point to / and Use As: should say "Ext4 journaling file system" it will list the partition as something like mmcblk0p5 (might be mmcblk0p6 or mmcblk0p4 or whatever. pay ATTENTION to this, write it down. you will need it later.
don't worry about swap space, the installer crashes if you try to set any space aside as swap space. so just leave the entire unallocated space for the ext4 partition
click on "Install Now" and a warning will pop up, just click continue (this is a warning about it suggest swap space. you cant, so just continue)
select your timezone, keyboard layout, then username, computer name, password on the next screens, and DON'T encrypt your home partition. and let it install
It should run for a while and finish installing
When it finishes, don't reboot, and instead exit the installer and power off instead of rebooting. you will see it stops after system halted. once you see that, hold the power button for 12 seconds to power off the device.
Leave everything plugged in, and power on, when you see the grub menu, this time hit "C" to drop to a command line. and remember the number at the end of your partition where you installed linux? get out that paper. you need it now. now type:
linux (hd1,gpt5) (dont hit enter yet) if your partition was 6 instead of 5 (mmcblk0p6 instead of mmcblk0p5) then instead of gpt5 use gpt6 etc.
now continue and add /boot/vmlin so that the command line reads
linux (hd1,gpt7)/boot/vmlin now hit Tab
it should autofill and read something like
grub> linux (hd1,gpt5)/boot/vmlinuz-3.13.0-32-generic
still dont hit enter. now add root=/dev/mmcblk0p5 (or whatever your partition was) followed by video=VGA-1:800x1280e reboot=pci,force
the final line should read something like
grub> linux (hd1,gpt5)/boot/vmlinuz-3.13.0-32-generic root=/dev/
mmcblk0p5 video=VGA-1:800x1280e reboot=pci,force
NOW you can hit enter.
next line. type:
Initrd (hd1,gpt5)/boot/initrd and press Tab again
now it should read something like
grub> initrd (hd1,gpt5)/boot/initrd.img-3.13.0-32-generic
now hit enter
now type boot then hit enter.
it should boot to desktop now
ok now we need to fix grub so you can boot without the thumbdrive in
make certain you are connected to the internet, via wired or usb wireless adapter, and open another terminal by hitting ctrl-alt-t
now copy and paste this in and hit enter:
sudo apt-get update && sudo apt-get install git bison libopts25 libselinux1-dev autogen m4 autoconf help2man libopts25-dev flex libfont-freetype-perl automake autotools-dev libfreetype6-dev texinfo
when it asks to install hit a y and let it continue
when it finishes and you see a terminal prompt again, type or copy:
git clone git://git.savannah.gnu.org/grub.git
and hit enter at the next prompt type
cd grub
followed by enter again, then type or copy:
./autogen.sh
hit enter again and at the next prompt type or copy:
./configure --with-platform=efi --target=i386 --program-prefix=""
enter again, at when it finishes, at the next prompt type
make
and hit enter. At the next prompt (will take a while to finish) type or copy:
cd grub-core
and hit enter. then copy and paste in:
sudo ../grub-install -d . --efi-directory /boot/efi/ --target=i386
hitting enter again. At the next prompt, type or copy and paste in:
cd /boot/efi/EFI
hit enter then paste in:
sudo cp grub/grubia32.efi ubuntu/grubia32.efi
and hit enter
now we get to edit grub.
next command you type or paste in should be:
sudo nano /etc/default/grub
and we get to edit the following line
GRUB_CMDLINE_LINUX_DEFAULT
find that line, and delete the words quiet and splash. and replace with
video=VGA-1:800x1280e reboot=pci,force
hit ctrl-x and save as you exit.
now we have the LAST command you need to type here. it's:
sudo update-grub
and of course hit enter.
once you have the terminal prompt again, you can exit the terminal, and power off the tablet again. (you will need to hold the power button for 12 seconds after system halts. get used to this.)
Now, I'm going to assume you don't want ubuntu to be the default OS to boot into yet. if you really do, skip this part, if not, continue.
Disconnect the usb thumbdrive and then press the power button on your tablet., Now press F7 over and over until the UEFI boot menu shows up Select "Enter Setup"
arrow over to the boot menu, and select windows as the number 1 option.
now, your tablet should be set up, to boot into windows by default.
To boot to ubuntu, use F7 to enter the boot menu on startup, and select grub and ubuntu
you can leave it with grub as the bootloader if you want. there are ways to configure grub to boot into windows by default, but you will need to keep a keyboard with the tablet at all times then. since sometimes it wont auto boot, and will wait forever for the enter key to be pressed to select your boot option.
I'll add information to my next post to explain how to rotate the screen in ubuntu, as well as information for updating kernels and getting the internal wifi to work.
ok, tips and tricks. to rotate the screen, you need to enter two commands into the terminal
first to rotate the view to the right, you type:
xrandr -output VGA1 -rotate right
on my most recent installation (ubuntu mate 14.04) this didnt work. so I needed instead to use
xrandr -o right
then hit enter of course. this WONT rotate the touchscreen. to rotate that, we need xinput.
first you can type xinput list to list what devices are present. I assume you will see FTSC1000:00 2808:5056 listed. if so, this will work, if not, you will need to adjust this command to fit what you see listed. (most important if you are adapting this guide to another bay trail tablet other then the pipo w2) the command that you want, assuming that's your touchscreen is
xinput set-prop "FTSC1000:00 2808:5056" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
and hit enter of course. your touchscreen should now be rotated to the right as well,
-----------------------------------------------------------------------------------------------------
ok, Wifi, to get wifi up and running, you will break screen rotation. Also it will break your normal boot process, requiring you to boot though advanced options for ubuntu, and recovery mode after that. The wifi is also unstable, and prone to hanging, requiring you to disconnect and reconnect at random intervals. It's not a perfect workaround, pretty far from it in fact, but it does at least prove the wifi is possible to get working. we probably need a better driver. Overall, you will get much much MUCH better performance with a usb wifi module. but that's extremely annoying to use so feel free to experiment here.
step one, go to here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/
and download the following files. http://kernel.ubuntu.com/~kernel-pp...eneric_3.18.0-031800rc4.201411091835_i386.deb
http://kernel.ubuntu.com/~kernel-pp...1800rc4_3.18.0-031800rc4.201411091835_all.deb
http://kernel.ubuntu.com/~kernel-pp...eneric_3.18.0-031800rc4.201411091835_i386.deb
now copy them to your desktop in ubuntu.
now in terminal type:
cd Desktop
then type:
sudo dpkg -i linux*.deb
once it's done, reboot your tablet. now go to grub, and select advanced options for ubuntu, then select recovery mode for the 3.18-rc4 kernel. and resume normal boot once you see the recovery menu show up
this should allow you to boot to desktop. after which go back to terminal, and type the following commands in, one line at a time of course, waiting for the next prompt before typing the next line
sudo apt-get install build-essential linux-headers-generic git
git clone https://github.com/hadess/rtl8723as.git
cd ~/rtl8723as
make clean
make
sudo make install
sudo depmod -a
sudo modprobe 8723bs
reboot. go through the recovery mode menu again to boot to desktop. wifi should now be working. you will need to use recovery mode to boot from this point on. since 3.18-rc4 wont boot without it. Be forwarned, suspend mode breaks wifi it seems. one time of the suspend, and you will need to reboot to get it working again. So I would suggest disabling everything applicable to your tablet screen shutting off. also, the wifi is extremely unstable. as noted above. it can quit for no reason, and need to disconnect and reconnect to use it more.
information for how to install the wifi driver was gained here:
http://ubuntuforums.org/showthread.php?t=2249936&p=13151763#post13151763
information as to why the wifi won't work, even with the drivers, on 14.04 default kernels was obtained from this thread https://bugzilla.kernel.org/show_bug.cgi?id=67921
would this work on a clovertrail device?
I don't think so. I don't think clovertrail is Linux friendly at all. Clovertrail+ should be, but not clovertrail. However the clovertrail+ devices I know of are the Asus padfone the Asus zenfone and the lenovo k900. All of which use droidboot. (Can't load grub). And have PowerVR graphics which are not open source, so no Linux drivers. There are probably more clovertrail+ devices out there I just haven't looked into them much.
I added information to the second post about screen rotation, and relevant information to the workaround for wifi. Be advised that it's not a perfect workaround. wifi works, and so does the power button. but it requires booting through recovery mode
It's cool. Do you know whether it works well on the latest W2f?
No idea. Probably though. But I can't be certain. I don't have a pipo w2f to test with.
Arch Linux
Have you tried to install ArchLinux on this tablet?
nope, sorry so far i've just experimented with ubuntu and fedlet. I have not installed fedlet, just booted and looked around a bit.
StridAst said:
nope, sorry so far i've just experimented with ubuntu and fedlet. I have not installed fedlet, just booted and looked around a bit.
Click to expand...
Click to collapse
I tried this guide , my interest was just trying to live mode ubuntu , but unfortunately the screen is distorted even changing resolution.
My though is a Pipo W6 .
Did you try to start Live Android X86 ?
Tony Evo said:
I tried this guide , my interest was just trying to live mode ubuntu , but unfortunately the screen is distorted even changing resolution.
My though is a Pipo W6 .
Did you try to start Live Android X86 ?
Click to expand...
Click to collapse
I've not tried android at all on mine. I keep meaning to do so, but have not found the time yet. Hmm though on the W6. did you try setting resolution settings at 1200x1920 or just 1920x1200? which number you put first matters and can result in a distorted screen. the w2 is listed as 1280x800 resolution, but to get ubuntu to work without the screen going all wonky, you have to reverse the numbers to 800x1280.
I tried different resolutions, the problem is that the screen is like tripled
---------- Post added at 04:37 PM ---------- Previous post was at 04:13 PM ----------
The solution was obvious ... Put the real screen resolution 1920x1200
{
"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"
}
Touch screen no works
hmm, which kernel are you using? I've found some of the newer kernels made the touchscreen on the W2 work, some made it not work. things to try.
first post the results of
xinput --list
that might offer some clues. also you could try downloading and installing the 3.18.1 kernel from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.1-vivid/
assuming you are using the 32 bit version not the 64 bit version of ubuntu, you would want to download both of the generic i386.deb files, (not the low latency) as well as the all.deb file. I'm assuming that updating the kernel on a live-USB works. I've never tried it actually.
to install you go to terminal, and assuming the files are placed in desktop, type:
cd Desktop
sudo dpkg -i linux*.deb
reboot and see if it helps. if not, you can try some of the other more recent kernels. I've noticed a huge difference from one RC to another. a rc1 file might have working touchscreen and power buttons for the W2, and a rc2 file breaks the touchscreen but the power button works, while a rc3 would have the touchscreen work again, but fail on the power button, etc. see here for all the other kernels. top of the list is the oldest, bottom is the most recent.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Sorry for my slow replies, I've only really had any spare time in the mornings lately.
StridAst said:
hmm, which kernel are you using? I've found some of the newer kernels made the touchscreen on the W2 work, some made it not work. things to try.
first post the results of
xinput --list
that might offer some clues. also you could try downloading and installing the 3.18.1 kernel from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.1-vivid/
assuming you are using the 32 bit version not the 64 bit version of ubuntu, you would want to download both of the generic i386.deb files, (not the low latency) as well as the all.deb file. I'm assuming that updating the kernel on a live-USB works. I've never tried it actually.
to install you go to terminal, and assuming the files are placed in desktop, type:
cd Desktop
sudo dpkg -i linux*.deb
reboot and see if it helps. if not, you can try some of the other more recent kernels. I've noticed a huge difference from one RC to another. a rc1 file might have working touchscreen and power buttons for the W2, and a rc2 file breaks the touchscreen but the power button works, while a rc3 would have the touchscreen work again, but fail on the power button, etc. see here for all the other kernels. top of the list is the oldest, bottom is the most recent.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Sorry for my slow replies, I've only really had any spare time in the mornings lately.
Click to expand...
Click to collapse
But I have a problem .
I dowload ubuntu 14:04 32bit , I create the key with rufus , once finished the process I copy and paste the files that you had put in the folder called " unpackit " .
Starting my PIPO , I press esc , I go in and do the boot devices on the pendrive .
and everything ok .
If you want to try to create another pendrive with another Distro ( 64bit ubuntu , fedora or other ) when I create the key , I start the PIPO but I do not recognize the key ,
can not find the pendrive between devices boot .
Install a 64-bit version of Ubuntu, with a 32-bit bootloader
Take a look at this link: linuxnorth,wordpress,com/2014/12/11/installing-64-bit-linux-on-the-asus-transformer-book-t100/
(change , with .)
I tried to install Arch Linux but couldnt boot it, neither any Arch-derivated. I tried also fedlet and its not bad at all.
Sorry if my questions are a bit stupid. Using this instruction we can install ubuntu OS as the 2-nd OS in parallel with windows, can't we?
If I have ubuntu installed on my tablet am I able to run android apps on it? Is ubuntu equals to android?
StridAst said:
Ok, So I thought I would post this guide to installing ubuntu 14.04 on the Pipo W2. This guide might help on some of the similar tablets out there too, like the voyo a1 mini. But I can't be certain about the others
Click to expand...
Click to collapse
Superb! Works 100% on my £20 Voyo A1 Mini, thank you!
Better guide, no offence (and no need to edit anything in Grub):
https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md
Working (for the majority of the hardware) on my Voyoa A1 Mini (5V2A version.)
mbwf said:
Better guide, no offence (and no need to edit anything in Grub):
https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md
Working (for the majority of the hardware) on my Voyoa A1 Mini (5V2A version.)
Click to expand...
Click to collapse
no offense taken! much appreciated posting a newer/better guide that's the beauty of xda. theres always something newer and better showing up. I wish my pipo tablet still worked so I could experiment with it, But a factory reset with windows 10 bricked it with the TPM bug. It wants confirmation to clear or to not clear the Trusted platform module, but this request boots up before usb. so there is no way to answer the request. no buttons work, and no keyboard input works. =/ afaik its bricked for good.
Related
I've posted this inside another thread but decided to make a new one so others can see.
To all of you guys who are giving up - DON'T !
Here's how I finally got root on my DINC after about 3 days of trying.
I've read and watched almost every post and walk-throughs available in this forum and few others and was still unable to get into ADB Shell using any of the methods and tricks available and even though none of them worked I kept trying until I found a post on adndroidforums.com by Centsy. So along with his instructions and combination of many others here's how I achieved root:
1. Download the file from the 10 minute incredible root video on YouTube by mejdam. (can't post the link cause I'm new to the forum).
2. Unzip the file and run SDK setup.
3. As soon as SDK setup runs it gives an error message. Close it. then hit Cancel on next window.
4. While still in Android SDK and AVD Manager click on Available Packages (on the left) and then hit the plus sign in the right window for the repository. It will give you a list of packages available. Download the very last one which is the USB_Driver. It will add 'usb_driver' folder to your SDK folder where you ran sdk setup from.
5. Modify android_winusb.inf file inside the 'usb_driver' folder by adding these lines at the end of [Google.NTx86] and [Google.NTamd64] sections:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
6. I used the 2 gig Sandisk memory card that came with the phone. Had it FAT32 full formatted on the pc.
7. insert the card into the phone wait for it to be recognized
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed. Note that I do not have HTC Sync installed on my pc.
9. on the phone go to settings->applications->development->turn on USB Debugging. wait for the phone to be recognized
10. open command prompt, navigate to your SDK\Tools folder and type in: adb devices. when you hit enter it should list your phone as being connected.
11. at the prompt type: adb reboot recovery, hit enter
12. as soon as the prompt is back type: loop and hit enter to start the adb shell loop. As soon as the loop starts running, the phone should show the white HTC Incredible screen, start clicking in and out the sd card before you hear the device disconnected sound on your pc. keep clicking the card in and out until you hear device connected sound on you pc. If you still don't see THE message we are looking for after another 10, 15 seconds stop clicking the card. take the battery out of the phone, put it back in, wait for it to reboot and repeat steps 11 and 12.
I had to do steps 11 and 12 about 3 times when I said to myself - next time is the last time and if it doesn't work then I'm going to get the 2gig PNY card that everyone is saying helps them achieve root. Then all of the sudden it took a little longer for the device connected sound to come up and the mouse cursor turned to the Waiting Hour-Glass and as soon as I heard the sound I saw the good old error message we are all striving to see. After that I just followed the instructions on the 10 minute root video to get the phone rooted.
Never give up, Never surrender !
Hopefully this will help some of you guys to achieve root and thanks to everyone who's hard at work on getting this great phone rooted.
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
sonypete said:
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
Click to expand...
Click to collapse
Basically once the white screen comes up, start clicking the card in and out until about 10, 15 seconds after the 2nd connect sound that windows give you. However, you MUST start pushing the card in and out before the 1st disconnect sound.
Okay cool. Fingers crossed I have been trying since yesterday and about to jump out the window hah.
- Pete
Wow, I got it first time with this method! Thanks a lot! I am also using the stock 2gb card that came with the phone.
Thanks man. I got this to work twice in about 4 tries. 1st time it worked I accidently selected reboot option. So had to retry this method. My clicks were medium speed not very fast and not excessively slow in case that helps anyone. About 1 a second.
- Pete
(2G Sandisk Rooter hehe)
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
I think this will help
KingJ50 said:
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
Click to expand...
Click to collapse
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
dreamersipaq said:
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
Click to expand...
Click to collapse
Same here, i still can't get to adb shell . . .
I got into adb doing the click on the 3d try but it kept failing to push the payload and then I accidentally restarted the phone. AHHHH, just spent 30 minutes doing the same thing and couldn't get back in.
Awesome, I got it to work using your method.
First I tried the "10 min..." video, but it was unclear in some areas. I had to try a few times (10+) to get it to work. Problem for me was the speed at which I was putting in and out the SD Card. I did it at some odd pattern like In (4 sec), out (.5 Sec), in (4 sec), etc. Then all of a sudden it worked.
Got it rooted .
Thanks again!
Finally got it. Thanks
Spent probably 6 hours messing with it. Not worth it anymore.
What does this mean:
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed.
Click to expand...
Click to collapse
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
dmauro said:
What does this mean:
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
Click to expand...
Click to collapse
if your phone shows up then you may proceed further. Howerver if after quite a few tries you still can't root then you should try updating the driver with the modified inf file.
go to your device manager, you should see the very first item should be Android Phone. right click on the phone and choose update driver and point to the modified INF file.
if your pc tells you that it cannot find a better driver, just uninstall the phone from device manager (right click and choose uninstall), unplug the phone from the pc, wait about a minute and plug the phone back in - but use a different usb port just in case. Then when found new hardware manager comes up point it to the modified INF file.
Good luck.
Doesnt work for me. annoying
*edit* Finally got it 7 seconds awesome
I cannot get my inc to take the driver .inf file. I have edited it correctly, tried forcing the driver to it, and it keeps telling me that the driver is not valid for a 64-bit os. Tried doing it as a legacy device as well.
Win 7 ultimate 64-bit
dont see the plus sign
hit the plus sign in the right window for the repository well for some reason i dont see any plus sign in there to hit tell me what i might be doing wrong
Please Help If You Can
I am logged in; got the recovery; followed the instructions, and it didn't say unrevoked. so i did it again and
did a whole bunch of things
Finding update packge
opening update package
verifying update package
installing update
veridying curernt system
unpacking patches
removing unneeded files
patching system fioles
symlinks and permission s...
then I got
e:multiple firmware images
e: can't store zip image
installation aborted
Now I also cant get into ADB SHELL
when I type adb shell I get
- exec '/system/bin/sh' failed: No such file or directory (2) -
but no prompt
I will try to stay logged in and everything BUT PLEASE HELP. What do I do?
Thanks for these instructions, Op.
I was successful by exactly following your steps.
Edit to provide additional details -- I tried unsuccessfully upwards of 100 times following the instructions in the 10min video. A couple things that probably attributed to the success of this method for me:
1) Formatted 2GB card to FAT32 (4096) as recommended.
2) Uninstalled HTC Sync / HTC Driver Installer. I used the "SDK Setup" to download the USB drivers.
A tip if you're having trouble getting the USB drivers to download... I had to go to the "Settings" menu in the Android SDK and AVD Manager, and check the "Force https://... sources to be fetched using http://..." otherwise the Available Packages menu would fail to get the repository.xml.
I then applied the recommended changes to android_winusb.inf in C:\sdk\usb_driver\ and used this .inf as the Android Phone driver. It was possible to assign the driver after setting to "Debug" mode in the OS.
3) I started clicking the SD card as soon as the white screen would come up, instead of waiting for a few seconds after it appeared. I used a 2 seconds in, .5 seconds out, 2 seconds in, ... pattern.
4) After each failed attempt, instead of pulling the battery and holding volume- + pwr, I went with the ops method. This was to abort the "loop" tool on the PC, pull the battery, boot the phone normally to the OS, verify the phone was recognized by typing "adb devices" on the PC cmd prompt, commanding "adb reboot recovery" to reset the phone into recovery mode, starting "loop" as soon as the command prompt came back, and finally clicking the SD card as described above.
DUAL-BOOTING WINDOWS 7 & LINUX
The following guide is to help would-be developers install Linux. If you are unsure how to partition a hard drive or run a backup, you probably should not attempt this. You've been warned, also I am not responsible for anything bad that may happen to your computer, this is simply a guide. If you have questions or run into a stumbling block, don't hesitate to ask. Lastly this guide was written for users using Windows 7, though it should work for other Windows versions I have no personal knowledge of how to accomplish this. Lastly read the guide the whole way through, there are two different methods one appears easier than the other.
METHOD 1 (TRIED AND TRUE)
Downloads for method 1)
Ubuntu 12.04 (LTS): This is the most current Ubuntu Linux release.
PowerISO: PowerISO is a small program that allows you to mount an .iso file as a physical drive, and allows for easy CD/DVD creation.
EasyBCD: EasyBCD is an excellent way to edit MBR so that it is easy to go from one OS to the next.
Prep-Step 1) Back up your work (This should be a no-brainer but all too many times have I seen someone in a sticky spot because they didn't have a good backup). Its not unheard of for a hard drive to become corrupted after repartitioning, but I can say that its not common either.
Prep-Step 2) Make a Windows recovery disc, if you have OEM installed Windows. If you did a clean Windows install or have the Windows disc for the operating system you are running, grab it. When installing a second OS you have to mess with the Master Boot Record (MBR), and the easiest way to repair the Windows MBR is with the recovery function on the disc.
Prep-Step 3) If you are like me and insisted on clean installs on your PC (I get not doing it every time on your phone, but I don't get in the habit of installing OS' on my PC), make sure that Windows is installed first. This step will save you a potential headache, and $50 bucks when you break your keyboard for not following Pre-Steps 1 and 2. The long and short of it is that Windows when it is installed will over-write whatever is on the hard drive its being installed on, including the Linux bootloader.
Optional Prep-Step I personally have found it easiest to partition my disc from Windows, so I am including this step.
a) [CLICK] "Start" in Windows
b) Type "disk management" and press [ENTER]
c) Choose the drive you wish to partition, in this case we will use the C drive, in the bottom pane, then [RIGHT-CLICK] on the main partition, [CLICK] "Shrink Volume"
d) Shrink the partition by entering how many MB you want to take from that partition, keep in mind for any of you people like myself who like to see even numbers on hard drives that 1 GB = 1024 MB, not 1000. Then [CLICK] on "Shrink" Please keep in mind that Ubuntu recommendsAT LEAST 10 GB and requires 4.4 GB If you are planning to do ROM development you should consider shrinking by around 100 GB or more if you have it.
You will now see unallocated space on your hard drive and for now thats a good thing. I typically do the actual format of the new partition during the Ubuntu install.
Prep-Step 4) Download Ubuntu and either a) burn it to a disc using an app like PowerISO, or b) put it on a USB stick. For ROM development you need to run the 64 bit version of Ubuntu.
OTHER RELEVANT INFO: While doing more in depth research I found several posts in forums about installation errors on hard drives larger than 1TB. The work around for this seems pretty easy. BEFORE PARTITIONING run a defrag, the goal is to get the new partition as close to the beginning of the disc as possible. Once again, if you have not already done so...BACKUP your data. If you have over 500 GB used on your hard drive you will most likely have issues booting Linux on a single hard drive, but you can still dual-boot when both OS' are on different hard drives.
INSTALLATION
Step 1) Insert the Ubuntu CD you burned into the CD/DVD tray of your PC and reboot your computer.
Step 1.5) If your BIOS is not set to boot from the CD drive you will need to tell the BIOS to boot from the CD, by pressing either F2, F12, Escape, or Delete depending on your BIOS. BIOS option are different for most PC manufacturers so I will not include how to change your boot order in this guide.
Step 2) Continue the installation and follow the prompts until you are asked this question: "How do you want to partition the disk?".
Step 3) If you followed the optional step and have room for Ubuntu then select the partition that you have already formatted select "Install Ubuntu alongside Windows 7" follow the installer through the rest of the steps. If you did not do the optional step, select "Something else" which will open up the "advanced disk partitioning tool"
Step 3.5) Not Applicable if you did the optional step in the preinstallation. When the Advanced disk partitioning tool opens you will see two (2) NTFS file systems (/dev/sda1, and /dev/sda2) DO NOT RESIZE /dev/sda1 unless you know what you are doing. It is ill advised to say the least and can cause boot issues. That said select /dev/sda2 (for most users this is their Windows partition) and [CLICK] "change". This will open a pop-up so that you can select how much of the Windows partition you want to use for Linux.
Step 4) In the "Installation Type" window at the bottom you should now see an area called "free space", select it, then [CLICK] "add" to add a new partition.
Step 5) The first partition we will add is the boot partition. For the partition type the default should be logical, if it is then leave it there, if not select logical. The recommended size is 500 MB. Keep the "Use as" box at its default which should be ext4, and the mount point is /boot. [CLICK] "ok"
Step 6) In the "Installation Type" window [CLICK] on "free space" and [CLICK] "add" to add a new partition, this partition will be / (root). Once again this will be a logical partition which will be used as a ext4 file system, and the mount point is /. The root partition does not need to be HUGE, 75% of the minimum 4.4 GB should be fine (Even if you are using much more than the minimum there is not much need for a / that is more than a few GB in my own experience. [CLICK] "ok" when finished.
Step 7) In the "Installation Type" window [CLICK] on "free space" and [CLICK] "add" to add a new partition, this partition will be /home. Once again this is a logical partition, using ext4 and the mount point is /home. The size of this partition is going to vary from user to user. You are only creating one more partition for Linux after this, and that partition is relatively small (1GB per 1GB RAM installed), so do not hesitate to use the majority of the space you allocated for Linux on this partition. [CLICK] "ok" when finished
Step 8) In the "Installation Type" window [CLICK] on "free space" and [CLICK] "add" to add a new partition, this last partition is for your swap. Once again this is a logical partition, but it will not be used as a ext4 file system, in the dropbox select "swap area". For the partition size I recommend using the rest of whats available for the swap, which should be 1GB per 1GB of RAM installed, for example if you have 4GB of RAM your swap should be 4GB. Once finished [CLICK] "ok".
Step 9) Once again you should be in the Advanced Disk Partition Tool ("Installation Type" screen), there you can see the partitions you have created. Because the /boot partition is logical it should be listed as /dev/sda5 (Always check...I can not express enough that anomalies happen). In the "Device for bootloader installation:" dropbox select /dev/sda5 or whatever it was labeled (EX /dev/sda#) [CLICK] "install now"
Step 10) Follow through the rest of the installation and enter your user information. After the install is completed successfully reboot your PC, it will reboot into Windows (which is 100% expected since we did not tell the MBR to look for our Linux system.
Step 11) Download and install EasyBCD from here, it is a free download.
Step 12) Open EasyBCD and [CLICK] "Add New Entry" , then [CLICK] the Linux/BSD tab. From the "Type" dropbox select "GRUB 2". I believe the name box comes filled with the OS info by default, if not in the "name" type "Ubuntu 12.04 (LTS)" and [CLICK] "add entry" (Not "Add New Entry")
Step 13) [CLICK] on "Edit Boot Menu", select your default OS and set the time out options.
Step 14) [CLICK]"Save Settings"
At this point you should have a dual-booting computer with both Windows 7 and Linux...Congrats.
MAKE WINDOWS BOOT BY DEFAULT ON PREVIOUSLY INSTALLED DUAL BOOT SYSTEM
Step 1) Restore the MBR from your Windows installation disc
Step 2) Download EasyBCD from here its pretty easy to use. The non commercial version is free too. This program will allow you to select the boot priority.
If you require more detailed instruction please PM me and I will add to the OP
METHOD 2 (USING THE WINDOWS INSTALLER)
I want to start by stating that I personally have never used this method, but it seems like its pretty easy (perhaps easier than Method 1). Credit for this part of the guide goes to Ubuntu.com.
Prep-Step) Download the Windows Installer from HERE. I suggest using Internet Explorer for this since IE gives you the option to just run the installer, rather than downloading it, only to delete the installer off your hard disk later.
Step 1) Run the installer if you have not already
Step 2) When prompted, enter the username you would like to use and the password for that account. Then [CLICK] "Install"
Step 3) Wait...The download is about 500MB so it may take a while to download and install but apparently you can still use your computer while this install is taking place. Once prompted [CLICK]"Finish" to restart.
Since I have not used this method I can not tell you at this point if it is necessary to repartition your hard disk when using this method. I will format my other PC and try it out later today or tomorrow and update this post as necessary.
INSTALLING UBUNTU THROUGH VirtualBox
Please read through the entire guide BEFORE attempting to do the tasks detailed in this guide. For this portion of the guide I used Ubuntu 11.10-Desktop, which is no longer a current release. The steps should be pretty close to the same, but after Step 7, things may get a little out of order.
Step 1) Open VirtualBox and [CLICK] "New" to add new virtual machine
Step 2) In the name field You are going to name your virtual machine, generally I use the distro name (EX "Ubuntu 12.04 (LTS)"), if you name like this the next box will automatically change to Linux, and the version will say "Ubuntu" [CLICK] "next".
Step 3) Select how much RAM you want to use for your virtual machine, generally I will use 2 GB, if I am going to use a virtual machine (This is where a dual boot has its biggest advantages. Your hardware is only running one OS, when virtualized your hardware is essentially running two.). [CLICK] "next".
Step 4) Now you are going to create your virtual hard drive, keep in mind if you are running a virtual machine to develop (I don't recommend this), you are going to want to dedicate more than a few GB for Linux (100GB+). [CLICK] "create". I use the VDI disk image type so I made sure that was the one selected, and [CLICK] "next", now at this next screen you can choose if you want your virtual hard disk to be dynamic (Only as large as it needs to be), or a fixed size. I chose dynamic, but again this may not be effective for development purposes. I have no personal knowledge of this so I can not answer that question. Finally [CLICK] "create"
Step 5) In the VirtualBox main screen [RIGHT-CLICK] your Linux virtual machine and select start.
Step 6) You will be prompted for which drive the installer for whichever distro you are using, at this point you want to go to the box to the right of the drop menu and select the .iso for the distro you want to use. Now [CLICK] "start"
At this point you should have a virtual machine running and ready to install Ubuntu.
Step 7) You are going to select your language and [CLICK] "Install Ubuntu". [CLICK] "continue" on the next screen.
Step 8) At this point you will be asked how you want to install Ubuntu, whether you want to erase the entire disk and install Ubuntu or if you want to do something else. You can do either one, without risking damage to your PC on a virtual machine, which is part of why we had to create the virtual disk. For this guide I am going to choose to Erase the disk and Install Ubuntu make your selection then [CLICK] "continue", then [CLICK] "install now".
Step 9) Choose your timezone then [CLICK] "Continue"
Step 10) Select your keyboard layout then [CLICK] "continue"
Step 11) Enter the user information you wish to use then [CLICK] "continue"
Allow the virtual machine some time to install the OS and once installation is completed it will prompt you to reboot [CLICK] "restart now". Congrats you should now have a working virtual Linux desktop!
RESERVED FOR DUAL BOOT ON 2 HARD DISKs GUIDE
ItzCrooK2UxD said:
RESERVED FOR DUAL BOOT ON 2 HARD DISKs GUIDE
Click to expand...
Click to collapse
Bro, can u show a guide to install inside virtual box cos i try to install it. Always fail at i686 kernel problem. Tks
Sent from my LG-P990
orbital_71 said:
Bro, can u show a guide to install inside virtual box cos i try to install it. Always fail at i686 kernel problem. Tks
Sent from my LG-P990
Click to expand...
Click to collapse
I can add in a virtual machine guide too. You're using Virtual Box, and not VMWare Player? If you are getting kernel failures I would try redownloading Ubuntu.
Also which settings are you using for your virtual machine?
ItzCrooK2UxD said:
I can add in a virtual machine guide too. You're using Virtual Box, and not VMWare Player? If you are getting kernel failures I would try redownloading Ubuntu.
Also which settings are you using for your virtual machine?
Click to expand...
Click to collapse
i am using virtualbox V4.2, i am able to dual boot but when i try to install inside virtualbox no success. I had try i386 and amd64 uninstall ubuntu and try install inside ubuntu but still fail. Using the storage setting to mount the disc. Tks
orbital_71 said:
i am using virtualbox V4.2, i am able to dual boot but when i try to install inside virtualbox no success. I had try i386 and amd64 uninstall ubuntu and try install inside ubuntu but still fail. Using the storage setting to mount the disc. Tks
Click to expand...
Click to collapse
Also a few things I forgot to ask...What kind of computer are you using, please be detailed and include things like Processor speed (chip number if you know it), RAM, and which OS you are using, and which version of Ubuntu (or other Linux distro) you are attempting to run in VM. I am going to try to replicate your error, so I can walk you through it.
Also you state that you had no success, please elaborate. Did the virtual machine not boot? Did it boot, but you could not get logged in? The more details the better...Thanks
ItzCrooK2UxD said:
Also a few things I forgot to ask...What kind of computer are you using, please be detailed and include things like Processor speed (chip number if you know it), RAM, and which OS you are using, and which version of Ubuntu (or other Linux distro) you are attempting to run in VM. I am going to try to replicate your error, so I can walk you through it.
Also you state that you had no success, please elaborate. Did the virtual machine not boot? Did it boot, but you could not get logged in? The more details the better...Thanks
Click to expand...
Click to collapse
Mine system 2nd gen i5 2 gb ram window 7 home premium. since i already duat boot ubuntu 12.04 amd64 bit and how actually to install inside virtualbox? I f i follow the instruction from askubuntu i will get stuck at the boot image of ubuntu saying the kernel i686 kind of stuff error. Was vmware player are better to use it for? tks
orbital_71 said:
Mine system 2nd gen i5 2 gb ram window 7 home premium. since i already duat boot ubuntu 12.04 amd64 bit and how actually to install inside virtualbox? I f i follow the instruction from askubuntu i will get stuck at the boot image of ubuntu saying the kernel i686 kind of stuff error. Was vmware player are better to use it for? tks
Click to expand...
Click to collapse
I have always used VMWare Player myself. Once I get home I will install VirtualBox and do a write up and walk you through it. Aside from RAM we have similar setups. Give me a few hours and I'll try to walk you through it.
ItzCrooK2UxD said:
I have always used VMWare Player myself. Once I get home I will install VirtualBox and do a write up and walk you through it. Aside from RAM we have similar setups. Give me a few hours and I'll try to walk you through it.
Click to expand...
Click to collapse
But if vmware is a good virtual machine to use then i just follow u with it. i can just uninstall virtualbox no problem for me.
orbital_71 said:
But if vmware is a good virtual machine to use then i just follow u with it. i can just uninstall virtualbox no problem for me.
Click to expand...
Click to collapse
OK...I got home and booted into Windows for the first time in a few weeks to do this. I am going to do an install, just to see if I get any errors come up. Not saying its something you did or didn't do, maybe a bad download. I got my VirtualBox from HERE
Updating the OP here in a few minutes...
ItzCrooK2UxD said:
OK...I got home and booted into Windows for the first time in a few weeks to do this. I am going to do an install, just to see if I get any errors come up. Not saying its something you did or didn't do, maybe a bad download. I got my VirtualBox from HERE
Updating the OP here in a few minutes...
Click to expand...
Click to collapse
i install this version VirtualBox-4.2.0-80737-Win.exe
orbital_71 said:
i install this version VirtualBox-4.2.0-80737-Win.exe
Click to expand...
Click to collapse
When you open VirtualBox does it show your Linux install on the left side? Also are you getting to a terminal prompt when it tells you this? If it does give you a terminal prompt try typing
sudo dpkg-reconfigure virtualbox-dkms [ENTER]
sudo dpkg-reconfigure virtualbox[ENTER]
Click to expand...
Click to collapse
ItzCrooK2UxD said:
When you open VirtualBox does it show your Linux install on the left side?
Click to expand...
Click to collapse
No terminal prompt when i install it, i never install on mine startup bar but on mine desktop screen there are. Anyway tonight when i reach home i uninstall mine virtualbox and try install the amd64 version and see how to see whether is the version problem not.
Sent from my LG-P990
Bro, one thing i don't understand since i already dual boot window and ubuntu. When i try to install ubuntu inside virtualbox why must i install ubuntu again inside virtualbox with the iso. and repeat the installation for ubuntu again. Wasn't there suppose a walk through with it? Tks
Sent from my LG-P990
orbital_71 said:
Bro, one thing i don't understand since i already dual boot window and ubuntu. When i try to install ubuntu inside virtualbox why must i install ubuntu again inside virtualbox with the iso. and repeat the installation for ubuntu again. Wasn't there suppose a walk through with it? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
You need to reinstall Ubuntu on to the Virtual disk you are creating, because the virtual machine is not looking at your entire disk. It only sees what you tell it to see on the virtual disk.
Also I edited my second post to include a walk through of a VirtualBox install
Bro, in step 8 installation of ubuntu inside virtualbox, if i choose erase. What will be erase of this selection? Tkd
Sent from my LG-P990
orbital_71 said:
Bro, in step 8 installation of ubuntu inside virtualbox, if i choose erase. What will be erase of this selection? Tkd
Sent from my LG-P990
Click to expand...
Click to collapse
It will format your virtual hard disk. Sounds risky but its not. Basically with a virtual machine the emulator (VirtualBox, in this case) uses a section of your hard disk and creates your virtual machine. The virtual machine has most of the capabilities as the host machine (your physical PC that you boot up), but is limited to the resources that you want to allow it to use (EX. How much RAM do you want to dedicate to your virtual machine, how much disk space will you allow it to have. So erasing it basically means it is going to clear that space within that virtual machine. It has no effect on other Windows or Linux OS' you may be using within the emulator...does that make sense? Bottom line, yes its safe to erase and in your particular case I would encourage it.
ItzCrooK2UxD said:
It will format your virtual hard disk. Sounds risky but its not. Basically with a virtual machine the emulator (VirtualBox, in this case) uses a section of your hard disk and creates your virtual machine. The virtual machine has most of the capabilities as the host machine (your physical PC that you boot up), but is limited to the resources that you want to allow it to use (EX. How much RAM do you want to dedicate to your virtual machine, how much disk space will you allow it to have. So erasing it basically means it is going to clear that space within that virtual machine. It has no effect on other Windows or Linux OS' you may be using within the emulator...does that make sense? Bottom line, yes its safe to erase and in your particular case I would encourage it.
Click to expand...
Click to collapse
Ok and i should go with ur recommendation for 100gb space if i am gonna compile rom in step 4 right? Thanks u so much Bro.
Sent from my LG-P990
orbital_71 said:
Ok and i should go with ur recommendation for 100gb space if i am gonna compile rom in step 4 right? Thanks u so much Bro.
Sent from my LG-P990
Click to expand...
Click to collapse
If you are going to be doing ROM development and compiling I would really lean more towards a dual boot than a virtual machine. Compiling is CPU intensive and on a virtual machine you aren't just running one operating system with the resources your computer has, but now you're talking about running two OS' and putting a heavy CPU load on one of them.
To answer your question, 100GB should be enough, but I do not know how development will go in a virtual machine...I have no experience in this. Perhaps someone who has developed on a virtual machine can chime in.
Just as the title states - the power button will light up, but just a black screen.
I've read around, holding this button and that button, loading zip files on the sd card - holding this and that, still nothing.
I get no vibration and still a black screen like it's turned off.
Perhaps a bad logic board? - If so, I'll stop wasting my time and yours.
Thanks in advance for any replies.
samething here...power light on , black screen. Is it totally bricked?
Helps to see that I'm not the only one with the same issue.
I can only hope someone chimes in to direct us both in the right direction.
I think you should try to enter apx mode (you have to keep pressing reset with a needle or something like that, press the power button for 3-4 seconds, and after 1 second release the reset), and see if you can flash a new bootloader and recovery with the A500APXFlash tool (search in the web). But you have to retrieve the cpuid of your tablet, in order to use the flash tool...It's a kind of mess, but it can be done.
omniastrider said:
I think you should try to enter apx mode (you have to keep pressing reset with a needle or something like that, press the power button for 3-4 seconds, and after 1 second release the reset), and see if you can flash a new bootloader and recovery with the A500APXFlash tool (search in the web). But you have to retrieve the cpuid of your tablet, in order to use the flash tool...It's a kind of mess, but it can be done.
Click to expand...
Click to collapse
I'm lost.
Let me just say, when I mean a black screen, I mean it's black - no lcd back-lighting or vibration from the unit.
I've tried what you described w/o a micro sd card in the slot and nothing hooked up to the tablet what so ever - nothing happens, except the power light coming on.
I've searched for the tool, read a little bit, but I'm getting lost within the terms.
Nothing I come across really explains what and how to do from a dummy standpoint.
Velocity_Stack said:
I'm lost.
Let me just say, when I mean a black screen, I mean it's black - no lcd back-lighting or vibration from the unit.
I've tried what you described w/o a micro sd card in the slot and nothing hooked up to the tablet what so ever - nothing happens, except the power light coming on.
I've searched for the tool, read a little bit, but I'm getting lost within the terms.
Nothing I come across really explains what and how to do from a dummy standpoint.
Click to expand...
Click to collapse
I know that feeling...It's non easy, even for those who knows a bit of pc and electronic devices (like me). In these days I have tried all I could try in order to revive the Acer of my friend. At one point it didn't even show the Acer logo, neither anything on screen, only the power light on. I suppose that the bootloader was corrupted somehow. So, if you wanna try, you will need:
1) the CPUID of your tablet. For this you can use usbdeview, if you have ever connect the tablet to your pc (if you haven't it's much more difficult!). Double click on USBdeview.exe, click on "edit" and then on "find" (or simply CTRL+F). Search for "Acer Iconia" and then double click on the result. Now copy the serial number somewhere.
2) If you got the cpuid you can get the SBK (copy the serial numer on this site, and click on "generate my SBK". Now copy all the SBK and paste it on notepad or similar. All the 4 parts, with all the spaces!)
3) Now the tricky part: open the A500APXFlash tool, click on "Bundle market", "view bundles" and select one of the bootloader with a decent recovery (for example the bundle number 17). Type the number of the bundle, and click on "download". You can download it on your pc, or you can download the bundle in a temporary file. It doesn't change much, you choose.
4) You can skip the "BTC selection", and go on. Now follow the instructions on screen, and if your tablet get in apx mode maybe you are lucky enough to recover it.
I don't remember if you have to install the Iconia drivers in advance, but maybe you already have them on your pc.
If you manage to flash the bootloader, then you could flash whatever rom you want. If something is not clear, feel free to ask.
omniastrider said:
I know that feeling...It's non easy, even for those who knows a bit of pc and electronic devices (like me). In these days I have tried all I could try in order to revive the Acer of my friend. At one point it didn't even show the Acer logo, neither anything on screen, only the power light on. I suppose that the bootloader was corrupted somehow. So, if you wanna try, you will need:
1) the CPUID of your tablet. For this you can use, if you have ever connect the tablet to your pc (if you haven't it's much more difficult!). Double click on USBdeview.exe, click on "edit" and then on "find" (or simply CTRL+F). Search for "Acer Iconia" and then double click on the result. Now copy the serial number somewhere.
2) If you got the cpuid you can get the SBK (copy the serial numer , and click on "generate my SBK". Now copy all the SBK and paste it on notepad or similar. All the 4 parts, with all the spaces!)
3) Now the tricky part: open the A500APXFlash tool, click on "Bundle market", "view bundles" and select one of the bootloader with a decent recovery (for example the bundle number 17). Type the number of the bundle, and click on "download". You can download it on your pc, or you can download the bundle in a temporary file. It doesn't change much, you choose.
4) You can skip the "BTC selection", and go on. Now follow the instructions on screen, and if your tablet get in apx mode maybe you are lucky enough to recover it.
I don't remember if you have to install the Iconia drivers in advance, but maybe you already have them on your pc.
If you manage to flash the bootloader, then you could flash whatever rom you want. If something is not clear, feel free to ask.
Click to expand...
Click to collapse
I hooked the tablet up to my pc and saw the term APX pop up at the bottom right of the pc screen, like any new usb device does.
I ran usbdereview in section 1 of your instructions. Found APX in the list, double clicked and it brought up very little info about the device, but no serial number. Is the serial number on the original box the box the tablet came in possibly be the same serial number I might be trying to find? Cause I have the original box with all the bar code label info.
I won't go any farther until I hear back from you.
Thank you very much for attempting to walk me through this process, it really means a lot.
By the way, I'm a pc guru too, on a hardware platform mostly. I've built may puters and enjoy overclocking them to see how far I can push them, but when it comes to phones and tablets, I'm lost.
Thanks again.
Velocity_Stack said:
I hooked the tablet up to my pc and saw the term APX pop up at the bottom right of the pc screen, like any new usb device does.
I ran usbdereview in section 1 of your instructions. Found APX in the list, double clicked and it brought up very little info about the device, but no serial number. Is the serial number on the original box the box the tablet came in possibly be the same serial number I might be trying to find? Cause I have the original box with all the bar code label info.
I won't go any farther until I hear back from you.
Thank you very much for attempting to walk me through this process, it really means a lot.
By the way, I'm a pc guru too, on a hardware platform mostly. I've built may puters and enjoy overclocking them to see how far I can push them, but when it comes to phones and tablets, I'm lost.
Thanks again.
Click to expand...
Click to collapse
Unfortunately the serial numbers are not the same....
Now, if you can't find the cpuid using usbdeview, there is another option, you have to use Linux! Here is the guide to follow to get the cpuid. After obtaining the cpuid, the rest is pretty easy. I hope this will help!
omniastrider said:
Unfortunately the serial numbers are not the same....
Now, if you can't find the cpuid using usbdeview, there is another option, you have to use Linux! Here is the guide to follow to get the cpuid. After obtaining the cpuid, the rest is pretty easy. I hope this will help!
Click to expand...
Click to collapse
I got lost pretty quick.
This is how far I made it: I downloaded Ubuntu 14.04.2, burned the image to disc, ran it live as a trial (wow, it's different than windows), used the embedded Firefox to install all of the needed libusb (not sure I did all that correctly).
The thread said "grab the code eppeP posted and save to to a text file as apx.c", so that is where I got lost.
I restarted the PC to come back here for more guidance.
I'm also unclear on the following from where I left off in the guide "fire up terminal, brouse to where the apx.c file is ........ect" What terminal are they talking about? How do I get there?
Then farther down in the thread it says "run the following commands: sudo su gcc apx.c -o apx -apx -lusb-1.0 ............ How do run these commands?
Like I said, I'm lost and very sorry I can't grasp this.
Velocity_Stack said:
I got lost pretty quick.
This is how far I made it: I downloaded Ubuntu 14.04.2, burned the image to disc, ran it live as a trial (wow, it's different than windows), used the embedded Firefox to install all of the needed libusb (not sure I did all that correctly).
The thread said "grab the code eppeP posted and save to to a text file as apx.c", so that is where I got lost.
I restarted the PC to come back here for more guidance.
I'm also unclear on the following from where I left off in the guide "fire up terminal, brouse to where the apx.c file is ........ect" What terminal are they talking about? How do I get there?
Then farther down in the thread it says "run the following commands: sudo su gcc apx.c -o apx -apx -lusb-1.0 ............ How do run these commands?
Like I said, I'm lost and very sorry I can't grasp this.
Click to expand...
Click to collapse
Sorry if I didn't answer before, but I was a little busy...So, Linux can be a little tricky, especially if you're not a developer (I learned something in school). By the way, all you have to do is to install those softwares, and then compile this piece of code, using gcc (the Gnu C Compiler). The linux terminal is basically like the Dos terminal, known as command line terminal, as you may know. There may be many kind of terminals in the Linux environment, one of the most used is the Bash Shell. In Ubuntu you can open a terminal by pressing CTRL + ALT + T.
So, just to be sure to be clear:
1) save this code in a file called apx.c
2) Boot Ubuntu, install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev
3) Open the terminal, change the "working directory" with the "cd" (it's "change directory" in short) command. You have to get to the directory where the apx.c file is.
4) Run the following commands
sudo su
gcc apx.c -o apx -lusb-1.0
5) Next, pop your tablet into APX mode - plug in microUSB, hold the RESET button, and press power for around 4 sec
6) Run the following commands (assuming same root terminal permissions. If not run sudo su beforehand)
./apx
If all went well, you should obtain the cpuid, or whatever it's called. Don't forget to write that damned number somewhere (even taking a screenshot or a photo of the screen!!). I hope this can help you.
Just a minor update to what I've done so far, with questions. LOL
I decided to load Ubuntu as a side OS on my old laptop, which Vista resides on. I didn't want to screw with my tower in case of a crash, but wanted to retain my downloads and work instead of working on a *live" platform. (not knowing anything about dual boot OS)
Went well I guess, but Ubuntu takes over as the main OS if no action is taken on the boot screen, then if action is taken and you don't log into Windows, Ubuntu resorts back and loads. (lame IMO)
Ubuntu does not recognize any kind of wireless signal and wanted me to set it up manually (like I know all the numbers to make this happen, not), so I just hooked a CAT5 cable from the living room router for my next steps.
I attempted to to download the files mentioned, but remembering when I was running the *live DVD" there was a Ubuntu site for software packages, so I went there to grab what I needed. (I think this method was a fail)
When on the Ubuntu package site, I had the option of AMD64 and i386 for each file, I chose the AMD64 first and it gave a error window, then I followed up with the i386 and got nothing but a window with the circular icon and nothing in the window after that, so I closed the window.
I really have no idea if any of the downloads and installs actually work at this point. The laptop does have Intel hardware, so I'm thinking maybe the AMD64 software error-ed out because of that, but it doesn't explain why I never got a confirmation running the i386 software.
Should I have just stayed away from the Ubuntu site all together and just installed for a basic Linux system?
I'm done for tonight, but on vacation for the next week, so hopefully I can gain some ground and move forward to revamp this bricked Acer tablet.
I really appreciate your help and patients you've provided me to this point.
Now I'm really stuck.
I saved that code on my windows desktop and in Ubuntu desktop - as a windows text file. (not sure if that is the correct way)
Anyway, I did open the terminal using the 3 keys as described.
It shows: user [email protected] name:~$
I can't navigate away from that prompt....... I get: Bash: command not found or file or directory not found.
I started by using: cd/home/user name/Desktop/APX and various combinations.
Man I feel dumb.
We could try another approach: you could create a new file on the Linux desktop called "apx.c", and paste into it the source code. Then, using the command "ls" (which is the same dos "dir" command) and "cd" you could find the path to the file.
I report here some commands I used to compile the application needed to get the cpuid:
[email protected]:~$ sudo su
[sudo] password for white:
[email protected]:/home/white# ls
Desktop Downloads Music Public Videos
Documents examples.desktop Pictures Templates
[email protected]:/home/white# cd Desktop
[email protected]:/home/white/Desktop# ls
apx.c
[email protected]:/home/white/Desktop# apt-get install libusb
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libusb
[email protected]:/home/white/Desktop# apt-get install libusb-1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libusb-1.0-0' for regex 'libusb-1.0'
Note, selecting 'libusb-1.0-0-dbg' for regex 'libusb-1.0'
Note, selecting 'libusb-1.0-0-dev' for regex 'libusb-1.0'
Note, selecting 'libusb-1.0-doc' for regex 'libusb-1.0'
libusb-1.0-0 is already the newest version.
libusb-1.0-0 set to manually installed.
The following NEW packages will be installed:
libusb-1.0-0-dbg libusb-1.0-0-dev libusb-1.0-doc
0 upgraded, 3 newly installed, 0 to remove and 90 not upgraded.
Need to get 245 kB of archives.
After this operation, 1,795 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/main libusb-1.0-0-dev amd64 2:1.0.17-1ubuntu2 [54.7 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty/main libusb-1.0-doc all 2:1.0.17-1ubuntu2 [115 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty/main libusb-1.0-0-dbg amd64 2:1.0.17-1ubuntu2 [76.0 kB]
Fetched 245 kB in 3s (74.4 kB/s)
Selecting previously unselected package libusb-1.0-0-dev:amd64.
(Reading database ... 163905 files and directories currently installed.)
Preparing to unpack .../libusb-1.0-0-dev_2%3a1.0.17-1ubuntu2_amd64.deb ...
Unpacking libusb-1.0-0-dev:amd64 (2:1.0.17-1ubuntu2) ...
Selecting previously unselected package libusb-1.0-doc.
Preparing to unpack .../libusb-1.0-doc_2%3a1.0.17-1ubuntu2_all.deb ...
Unpacking libusb-1.0-doc (2:1.0.17-1ubuntu2) ...
Selecting previously unselected package libusb-1.0-0-dbg:amd64.
Preparing to unpack .../libusb-1.0-0-dbg_2%3a1.0.17-1ubuntu2_amd64.deb ...
Unpacking libusb-1.0-0-dbg:amd64 (2:1.0.17-1ubuntu2) ...
Processing triggers for doc-base (0.10.5) ...
Processing 32 changed doc-base files, 1 added doc-base file...
Setting up libusb-1.0-0-dev:amd64 (2:1.0.17-1ubuntu2) ...
Setting up libusb-1.0-doc (2:1.0.17-1ubuntu2) ...
Setting up libusb-1.0-0-dbg:amd64 (2:1.0.17-1ubuntu2) ...
[email protected]:/home/white/Desktop# gcc apx.c -o apx -lusb-1.0
[email protected]:/home/white/Desktop# ./apx
Error: Failed to open device! //failed because there wasn't any tablet attached!!!
Click to expand...
Click to collapse
Hello All
I was able to successefuly install Ipython(jupyter) on my nexus(2013) and wanted to share the procedure with all that could be interested.
You could learn and read about Ipython[Jupyter] here
CAUTION:
> To the best of my knowledge this is the first tutorial of it's kind.
> I strongly recomend that you try this on a fresh rom. Use MultiROM for instance
> This was tried on Nexus 7(2013) with android 4.4.4. But I see no reason why it shouldn't work on lolipop 5.0 or on another android tablet. [You could try at your own risk and report your findings]
> Allow minimum 4Gb free space. I used rougthly 2.2 Gb, but i installed more than just ipython
> Hackers Keyboard is VERY HANDY if not NECESSARY
> I apologize for typos and gramar mistakes in advance
> Some of the following steps take time (a long time). Just make sure your tablet is connected to the charge and chose to keep the screan ON while it's on charge
> I am UNLOCKED and ROOTED. I can't tell whether it is required. If it is it would have to be with the prerequired apps. YOU WANNA VERIFY THAT before anything
> MOST IMPORTANTLY, DO THIS AT YOUR OWN RISK. I'm NOT RESPONSIBLE for any INCONVENIANCE whatsoever.
Procedure:
1-: Install GNURoot WheezyX . I am more confortable with debian, tryFedora or Gentoo ... If you know what you are doing.
2- Install GNURoot
3- Open GNURoot
4- Chose wheezyx (or fedora or gentoo ... depending on the distro you like) in the "Select Rootfs to Create " drop-down menu.
5- Click on 'Create New Rootfs' button
6- Chose wheezyx(or fedora or gentoo ... depending on the distro you chose) in the "Select Rootfs to Launch " drop-down menu
7- Check 'Lauch as Facke Root' box. This will give us root privilege
8- Click on 'Lauch Rootfs' button
At this point you shoud have 'Terminal Emulator" open up a window with '[email protected]:/# ' and a prompt ready to take instrucktions
Welcome to linux !!!
Now we need to install "python" and "pip", but before that we need to install 'build-essentials' which will make 'gcc' and all tools required to build a package available on our linux platform:
In the following: if you chose wheezy distro it's the same procedure; if you chose fedora distro replace apt-get with yum; if you chose gentoo you are on your own because I'm not familiar with it
Anyways I assume no responsability anyhow whatsoever.
9 - At the prompt type 'apt-get update' and press Enter
10 - Type 'apt-get upgrade' and press Enter'
11 - Type 'apt-get install build-essential' and press Enter' : This will install "build essential"
12- - Type 'apt-get install python' and press Enter' : This will install "python". I got the version 2.7.3 . You could find the version you installed by typing "python -V" and pressing Enter
13 - Type 'apt-get install python-pip' and press Enter' : This will install "pip", the python package manger
At this point we have python setup in the linux environement. Let's finally install ipython:
14-a Type 'pip install ipython' and press Enter if all you want is the ipython interpreter
15-a Type 'pip install ipython --upgrade' and press Enter to make sure you got the latest version
or
14-b Type 'pip install ipython[all] ' and press Enter if you want ipython and all the goodies like notebook
15-b Type 'pip install ipython [all]--upgrade' and press Enter to make sure you got the latest version
I do scientific work with ipython, so if you are on the same boat as me you could install scientific packages numpy,sympy,pandas,nose,.... with:
"apt-get install python-numpy python-scipy python-matplotlib ipython ipython-notebook python-pandas python-sympy python-nose" !!! This is a lot about 1.2Gb !!!
At this point everything is set up. "when the wine is drawn, we now just have to drink it"
16-a Type ' ipython ' and press Enter to run ipython interpreter
or
16-b Type ' ipython notebook' and press Enter to run ipython notwbook. If you get an error message say that ''no web browser could be found" ignore it. look for the server address (looks like http://localhost:8888)
17-b Enter that adress (http://localhost:8888 in my case) in Chrome (I had no problem with chrom so far, but you could try on your favorite web browser) press Enter. Et voila you should be in the ipython notebook tree
I have been here for a couple of years, and never got to share anything.
This is my first thread, and i hope it is the beging of a very long series of contributions
> I will upload screenshots later to better guide noobs (I was one onece)
> PM me if you like to donate. I would appreciate it
> Please support the GNURoot developpers, or ipython[Jupyter] developpers if you can. They are all doing a terrific work. (I'm in no way associated to them, but love and support their work)
> I'm not very good at making videos, but I welcome any initiative.
You now Know how to install ipython, I trus you could be very creative since you now got linux at your finger tip :laugh:
Help to use pandas + matplotlib: no $DISPLAY environment variable
First of all thank you for this pretty cool tutorial
i did it and everything else works after all that huge pip installation!
my problem is that i need to see the result of my codes which sometimes is to show me plots of my data using the library matplotlib.pyplot
when i do that i get the following error:
TclError: no display name and no $DISPLAY environment variable
i found someone with the same problem in another situation (not on android but something like trying to save the plots in a pdf) and the problem was solved doing the import like this:
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
plt.plot([1,2,3])
plt.show()
By using matplotlib.use('Agg'), python knows to use the non-interactive back-end Agg instead of trying to display to the screen
this means that i don't have anymore the error but the plot won't be shown either
this happens not only when i do python file.py from command line but also when i run the same codes on jupyter notebook
so is there a way to execute file.py so they do what ever pandas want to do in this android environment (especially pop up windows with my plots when I execute the files)?
if there is no way how do i get rid of android to install some better OS on my tablet that can do all this kind of stuff?
thank you but all of this that you have done it's really not that useful if i cant see my plots
let me know!
paolotamag said:
First of all thank you for this pretty cool tutorial
i did it and everything else works after all that huge pip installation!
my problem is that i need to see the result of my codes which sometimes is to show me plots of my data using the library matplotlib.pyplot
when i do that i get the following error:
TclError: no display name and no $DISPLAY environment variable
i found someone with the same problem in another situation (not on android but something like trying to save the plots in a pdf) and the problem was solved doing the import like this:
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
plt.plot([1,2,3])
plt.show()
By using matplotlib.use('Agg'), python knows to use the non-interactive back-end Agg instead of trying to display to the screen
this means that i don't have anymore the error but the plot won't be shown either
this happens not only when i do python file.py from command line but also when i run the same codes on jupyter notebook
so is there a way to execute file.py so they do what ever pandas want to do in this android environment (especially pop up windows with my plots when I execute the files)?
if there is no way how do i get rid of android to install some better OS on my tablet that can do all this kind of stuff?
thank you but all of this that you have done it's really not that useful if i cant see my plots
let me know!
Click to expand...
Click to collapse
You should know that the linux running GNURoot doesn't have an X-session. You kinda need x11 installed on it to be able to have windows popping up and showing your plots. I remember trying apt-get install x11 without success on "Wheesy". Now, I know there is the "wheesy X" distro of GNURoot, but I don't know whether the X stands for X-session capability; I suggest you try that. (I no longer have my nexus7 to try, but it would be nice to see what happens).
I was able to go around this problem by working on the notebook. I could see my plots fine. I remember firefox beeing the best browser to work on the notebook.
Plots at least on jupyter and transfer files
hey so i found this : (i dont have authorization to post links normally)
stackoverflow .com / questions / 18353203 / using-python-and-matplotlib-on-android
where someone is stating is a big deal to have plotlib working on android
jupyter notebook is not displaying plots not even on firefox, it always give the "TclError: no display name and no $DISPLAY environment variable". It would be awesome if you'd give me a straight solution so i can see plots on jupyter! that would be more than enough to follow lessons in class
the temporary solution i found for now is to remote control my pc at home from the tablet to do all the coding but i cannot work without connection this way
i also found out about this website Wakari but they are saying now there isn't anymore free space for new subscription..
the best solution would be to have plots displaying on jupyter with your help
so the plan for now is to stick to let the pc at home do all the work and remote control it with the samsung remote pc app or to find a good website to log in from the tablet and write codes on browser
ill still use this command line of yours when ever i can thou, when ever there is nothing to display i guess.. but how do I find the folders so i can move to the desktop computer the .py files or the notebook files i create? i was expecting to find the files when i was connecting the tablet with usb wire.. is there anyway to transfer those files?
thank you
izzox said:
You should know that the linux running GNURoot doesn't have an X-session. You kinda need x11 installed on it to be able to have windows popping up and showing your plots. I remember trying apt-get install x11 without success on "Wheesy". Now, I know there is the "wheesy X" distro of GNURoot, but I don't know whether the X stands for X-session capability; I suggest you try that. (I no longer have my nexus7 to try, but it would be nice to see what happens).
I was able to go around this problem by working on the notebook. I could see my plots fine. I remember firefox beeing the best browser to work on the notebook.
Click to expand...
Click to collapse
Use:
%matplotlibe inline
Instead of:
matplotlib.use('Agg')
Nextbook Flexx 11
A 200-250$ 2-in-1 laptop.
CPU: 1.83 GHz Intel Atom Z3735F Quad-Core
RAM: 2 GBs
SSD: 64GBs
Screen: 11.6" Touchscreen
Ports: 1 x MicroHDMI, 1 x MicroUSB 2.0, 2 x USB 2.0
Micro SD Card slot
Installing every linux based OS(Android, RemixOS, Linux Distros)
Prerequisites:
A bootia32.efi file (Found in attachments)
A copy of your favorite linux distro
Rufus, UNetbootin, or a USB disk image write of your choice.
A flash you can wipe, and boot from
A little bit of time
Step 1: Setting up
First thing you'll need to do is use your image writer to write the iso to your USB.
MAKE SURE YOU SELECTED THE RIGHT USB DRIVE!
I cannot stress this enough, if you don't want to lose everything on another flash drive, or your hard drive, check and make sure you are using the right drive letter.
Do not restart now. We need to add some files to it.
Extract bootia32.efi and copy it to /boot/efi on your flash drive.
So this was some instructions I made for booting it, but this is much more complicated than it should be. You can totally disregard this spoiler.
Step 2: Booting
Plug your USB into your nextbook (if you haven't already) and turn it on/reboot it.
As its powering on, hold ESC to get into the boot options.
Click "Boot Manager" and select your USB drive.
IF IT DOESN'T SHOW UP, FORMAT YOUR USB DRIVE TO FAT32 AND GO BACK TO STEP 1.
Now, 2 things may happen, it may boot up perfectly, and from there, just follow the steps to install.
If it doesn't boot properly, we'll need to type a few commands.
Step 2.1: Grub Command Line.
So if it doesn't boot up properly, which chances are it wont, you'll be dropped into a command line.
This is grub, if you didn't know, and to boot we need to locate the drive its on.
First press FN+Ins to turn off NumLk, then type,
Code:
linux (hd
now if you press tab, it should list everything you have attached, for example:
Code:
hd0, hd1, hd2, hd3
The usb will most likely be hd0. So now you should have
Code:
linux (hd0,
If you press tab again, it will list off all of your partitions, or autofill one in.
Now you should have either:
Code:
1. linux (hd0,msdos1)
2. linux (hd0,gpt1)
Now, if you have this, type this(replace hd0,gpt1 with what you got):
Code:
set root=(hd0,gpt1)
then type
(new)Step 2: Creating a boot file.
So, now that you have the files copied over, you need to name the drive.
Right click your drive, and click Rename... (Remember the drive name, its important)
After you renamed your drive, create a folder at DriveLetter:/boot/grub
In that directory, create a file named grub.cfg
Now depending on your linux version, you'll have either syslinux, or grub already.
If grub: The file should already be there, so you can move on to step 3.
If syslinux: Find the isolinux.cfg or syslinux.cfg (probably in /syslinux or in /isolinux)
It will look something like:
Code:
label LinuxVersion
kernel /kernelFile
append initrd=/initrdFile (more options)
We're going to use these options to create our grub.cfg file.
Use this as a template.
Code:
menuentry 'LinuxVersion' {
search --set=root --label THIS_IS_WHERE_THE_LABEL_YOU_SET_EARLIER_GOES
linux /kernelFile (more options)
initrd /initrdFile
}
Step 3: Boot into your new OS.
Reboot your PC. When it turns back on, hold ESC.
You should be brought back to the BIOS area.
Press "Boot Manager" (you will need a mouse for this), and select your USB drive.
If you did everything correctly, it should boot.
Step 4: Go wild!
You should be booted, GO CRAZY!
There are a few problems with most distros, including:
No Wifi
No Bluetooth
No Gyroscope
No Audio
There are drivers online for these, but you need to be able to patch a kernel, and build/install a driver.
Wifi
Is the guide not working?
Go ahead and ask some questions, don't be afraid of help.
Useful resources:
Ubuntu with Wifi (Source)
Thats all the links for now. I will add more as I find them (hopefully to fix audio, power button, and rotation)
Huge thanks to Ian Morrison for the Ubuntu iso.
TAG
Any chance you're going to do the linux?
Reserved
I'm guessing that is where the linux how to, is going.
Dude.. You gonna finish this?
set code=(hd0,msdos1)
Then type
Type what? Need a complete tutorial here...
I'm so sorry
Chaosmstr said:
Dude.. You gonna finish this?
set code=(hd0,msdos1)
Then type
Type what? Need a complete tutorial here...
Click to expand...
Click to collapse
I apologize for the delay, busy with school and all.
You can't leave us hanging like this!
I'm not sure about OP here, but I have the smaller model of this device being the Flexx 10. Now I haven't tried to boot Android on it, but I have successfully booted Linux Mint with it.
First I would recommend using a USB OTG capable flash drive (they are available at office stores, walmart, and so on and so forth,) or an OTG adaptor instead of using a full sized usb. The reason for this is stability of the booted system as the connection of the keyboard dock does not appear to be extremely reliable. This may vary by model or device but I would still recommend it as you may need the full sized USB ports later.
Now instead of using Unetbootin, I used Rufus. I used the settings of GTP for efi and bios to write the image to the drive. I didn't mess with any other settings there. After that I had to get a file called bootia32.efi and then add it to the /efi/BOOT/ before the system would even try to recognize it. From there it was just waiting patiently while it booted. (use the instructions in the earlier post to get to the boot options of the UEFI) It took it a while to boot as I suspect the USB speed was rather slow.
As I didn't really have time to really mess with it and get to the point of install, I will list the issues I came across.
1: Automatic rotation of the screen did not work.
2: wifi (RTL8723BS SDIO)
3: bluetooth
4: sound
everything else seemed to work just fine though, even the volume rocker, windows button and power button on the tablet section reacted and did things. not entirely useful, but they did work.
Edit: forgot to mention that if you go through with the install, you will have to finish the install by doing some grub modifications to make it boot without a live disk. just a heads up.
Hmfan said:
I'm not sure about OP here, but I have the smaller model of this device being the Flexx 10. Now I haven't tried to boot Android on it, but I have successfully booted Linux Mint with it.
First I would recommend using a USB OTG capable flash drive (they are available at office stores, walmart, and so on and so forth,) or an OTG adaptor instead of using a full sized usb. The reason for this is stability of the booted system as the connection of the keyboard dock does not appear to be extremely reliable. This may vary by model or device but I would still recommend it as you may need the full sized USB ports later.
Now instead of using Unetbootin, I used Rufus. I used the settings of GTP for efi and bios to write the image to the drive. I didn't mess with any other settings there. After that I had to get a file called bootia32.efi and then add it to the /efi/BOOT/ before the system would even try to recognize it. From there it was just waiting patiently while it booted. (use the instructions in the earlier post to get to the boot options of the UEFI) It took it a while to boot as I suspect the USB speed was rather slow.
As I didn't really have time to really mess with it and get to the point of install, I will list the issues I came across.
1: Automatic rotation of the screen did not work.
2: wifi (RTL8723BS SDIO)
3: bluetooth
4: sound
everything else seemed to work just fine though, even the volume rocker, windows button and power button on the tablet section reacted and did things. not entirely useful, but they did work.
Edit: forgot to mention that if you go through with the install, you will have to finish the install by doing some grub modifications to make it boot without a live disk. just a heads up.
Click to expand...
Click to collapse
Sorry I'm coming back so late, I've been busy with life.
The Wifi issue can be fixed by building the driver (https://github.com/hadess/rtl8723bs)
The bluetooth wont work on most OS' because it relies on some windows drivers to work.
I might be able to find a driver for screen rotation/audio.
Another issue is the power doesn't get registered, and the touch screen is VERY flaky.
Kitsumi said:
Sorry I'm coming back so late, I've been busy with life.
The Wifi issue can be fixed by building the driver (URL removed per post restrictions.)
The bluetooth wont work on most OS' because it relies on some windows drivers to work.
I might be able to find a driver for screen rotation/audio.
Another issue is the power doesn't get registered, and the touch screen is VERY flaky.
Click to expand...
Click to collapse
I didn't really notice that power one as I did not use it long, but I think that is just an atom thing. My old n270 based aspire one does that too.
Really though, the way I would use it, I wouldn't miss screen rotation or the bluetooth, but the touch screen is the nuisance. What I noticed with it is that when the screen is forced into proper orientation (by use of screen rotation in the settings, you know without using the command line) is that the touch screen doesn't follow the new orientation correctly. It appears to have the portrait resolution set to the top left of the screen in landscape. That said, it works fine in portait. Or at least managably.
Hmfan said:
I didn't really notice that power one as I did not use it long, but I think that is just an atom thing. My old n270 based aspire one does that too.
Really though, the way I would use it, I wouldn't miss screen rotation or the bluetooth, but the touch screen is the nuisance. What I noticed with it is that when the screen is forced into proper orientation (by use of screen rotation in the settings, you know without using the command line) is that the touch screen doesn't follow the new orientation correctly. It appears to have the portrait resolution set to the top left of the screen in landscape. That said, it works fine in portait. Or at least managably.
Click to expand...
Click to collapse
Well, I decied to try and boot remixOS, and it works VERY well, so does android-x86 5.0
That being said, audio is a glaring issue.
When you tried Remix OS and say it worked very well. What do you mean? What actually worked? Obviously audio is what doesn't since you mentioned it. But am I to assume that screen rotation works as expected then?
I'm not willing to use REMIX OS personally as the whole android bit is a limiting factor to me. Unless it rooted of ccourse. but even then some of my prefered uses for Linux is lost.
Also hows the hardware acceleration?
How do I install the x64 version of Windows? I downloaded the ISO with the Media Creation Tool and it won't boot from the USB drive. I enabled USB booting and made sure secure boot was off, but it's not working. It keeps saying there's no USB device available.
Unfortunately due to the way that Windows works, the 64 bit version is not usable due to the bootloader difference. Even though the hardware of the device is capable of 64 bit code execution, the 32 bit UEFI Bootloader will only allow a 32 bit version of Windows or a 64 bit version of Linux with some EFI fiddling. And as far as I know there is not a way to fiddle with the EFI related workings of a Windows ISO so 64 bit Windows is not possible on these Nexbook devices or others with similar hardware (Asus t100 is a good example of similar device)
Hmfan said:
Unfortunately due to the way that Windows works, the 64 bit version is not usable due to the bootloader difference. Even though the hardware of the device is capable of 64 bit code execution, the 32 bit UEFI Bootloader will only allow a 32 bit version of Windows or a 64 bit version of Linux with some EFI fiddling. And as far as I know there is not a way to fiddle with the EFI related workings of a Windows ISO so 64 bit Windows is not possible on these Nexbook devices or others with similar hardware (Asus t100 is a good example of similar device)
Click to expand...
Click to collapse
That's really dumb. Most Windows devices are 64-bit nowadays. Why would they put in a 64-bit processor but not allow x64 operating systems?
You're guess is as good as mine on that one. Ask Microsoft on that one. They used the 32 bit version because Microsoft will only give the "Windows XX (originally 8.1) with bing 32bit for free. Which keeps the device cost down. Kinda hard to to sell a cheapskate device when it ends up costing as much as a better speced laptop.
Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
You can try this web site from Efun themselves
http://nextbookusa.com/recovery/index.html That is their official recovery download site.
(apparently I can post links...)
Hmfan said:
You can try this web site from Efun themselves
http://nextbookusa.com/recovery/index.html That is their official recovery download site.
(apparently I can post links...)
Click to expand...
Click to collapse
I tried that. It says there's no recovery option for this model....
Do you have this tablet? Do you think you could do a driver backup and upload it here? Or create a recovery image and share it?