Related
MANY THANKS TO REV FOR RE-WRITING THIS FOR ME!
(Post was updated on 3/23/2011)
=======================================
This post is to provide a template for using NVFlash to restore/recover your G-Tablet after suffering some kind of malfunction. Specifically, this document tries to provide ALL the information you need to use the NVFlash tool to recover the bekit 1105 software version, which has been found to be safe as a starting point for rebuilding your tablet after having a problem. This post does not include other methods of setting up NVFlash (such as installing the SDK, etc.) because this method is proven and can be easily supported.
I use Ubuntu Linux and know that the Linux instructions below are correct. Others have written Windows instructions and those too have been checked carefully and have been used before successfully.
A WARNING IN ADVANCE: NVFlash makes changes to the partition structure of your device. You should tread carefully and understand the risks. (MOD EDIT Note: It also has been noted a bunch of times that even NVFlashing your G-Tablet will not completely overwrite everything on it.)
The NVFlash setup process begins with a visit to:
http://db.tt/Wm25t7U
(Note: Sometime this DropBox is cranky. If you have trouble with it, check back later.)
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Note: The above "nvflash_gtablet_2010110500" is commonly referred to as bekit version 1105 in many posts relating to nvflashing (especially my posts).
-------------------------------------------
Installation
First, create a folder named "NVFlash" on your PC to put the needed files into and to work from. (Note: You can call it something else if you want to; we're just using "NVFlash" to keep all of us on the same page.)
Next, extract the files you downloaded from the DropBox above into the "NVFlash" directory. The files with linux and windows in the middle of then are the files for setting up NVFlash. (The are taken from the SDK and do not install the whole SDK -- just a simple, operable NVFlash for us to use here.) The files with gTablet in the middle contains the .img files with the software to go on your G-Tablet.
Third, for Windows users, you'll need to have an APX-specific USB driver for the next steps. (The Windows package bekit supplied has an .inf file in it, but the actual drivers are not there). For Linux users, you don't need an extra driver.
One source for the Windows drivers is at
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files. Extract them and go down two levels to the "USB" folder -- and move that into your "NVFlash" directory. The USB folder has the .inf file for installation in it along with two other directories with drivers for the various operating systems. (Note: These drivers, which are the same as the drivers in the SDK, are proven to work with Win 7 64-bit and have the setup include to load into other versions of Windows.) Follow this narrative for actual installation of the drivers.
CHECKPOINT: At this point, you should have the nvflash files, .img files, and USB directory (and files) in you "NVFlash" directory and are ready to begin the recovery process.
Now, you will need to boot into G-Tablet APX mode: hold down the power and volume - button simultaneousl until your G-Tab comes up and the goes back to a black screen. The black screen means it is in APX mode and it is waiting to display the flashing process. In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Connect your G-Tablet to your PC using your miniUSB to USB cable that came with your tablet.
Linux users: At this point, open up a command window to the folder you created, and run this script:
./nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically. If the script does not work, make sure that the shell script and nvflash binary are set as executables.
Windows users: When you connect to the PC, the PC immediately tries to load a driver -- but since it doesn't know where the USB driver files are it will fail. Click through Start/Control Panel/Device Manager and find "APX" listed in the devices with a yellow "!" (exclamation point) on the icon. Select the APX item and find the "Update Driver" button and click it. When it asks where to search, choose the local computer manual selection choice and tell it to Browse.
Point the Browse (and the USB install) at the "USB" directory under the "NVFlash" folder. When pointed at the "USB" directory, the driver installed and I was ready to nvflash. If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Again, for Windows: Run this script which is in the "NVFlash" folder:
nvflash_gtablet.bat
This will wipe the device back to bekit's original TnT stock image except for user data, which is retained. Should take about a minute to run and the device will reboot itself automatically all the way to the main screen.
POST NVFlash:
When your G-Tablet has booted back to the main screen, you will have to check and make sure everything is set up. Particularly, get the wifi on and connected to the Internet. Almost immediately, you should get a notice about an OTA (over the air) update. This is the OTA Update to software version 3588. If it does, go ahead and have it do the update. From there, you can begin using your "stock 3588" G-Tablet.
If you don't get an automatic OTA notification, you can go the to manual "Update" icon on your tablet and have it check for updates -- and hopefully it will find OTA 3588.
Or, if neither of the above happen, you can download 3588 at the following link and install it manually:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
Note: Following is a STICKY from General Forum on the stock recovery process:
http://forum.xda-developers.com/showthread.php?t=892090
NOTICE: There are many threads out there with tell how to do this process. Others tell individuals' problem solving experiences. A few of them may not be right! The above process is not the only way to do this -- but it is fairly straightforward and it is proven. It is recommended for anyone who does not have experience with nvflashing.
***************************************************
Further references (since I'm not a Windows user): http://forum.xda-developers.com/show...0&postcount=28
and http://forum.tegratab.com/viewtopic....bbde76184e550a and http://wiki.tegratab.com/index.php/Nvflash_FAQ
An additional suggestion if you also want to tack on bekit's clockworkmod recovery versus standard recovery: http://forum.xda-developers.com/show...3&postcount=17
Hope this helps!
03/2011 update -- I've been told that this tool has been useful to erase ALL partitions, including user data. I believe you need to re-flash with the bekit 1105 above, AFTER you use this: http://forum.xda-developers.com/showthread.php?t=974422
04/22/2011 update -- I've built out both 1.1-3588-based and 1.2-4349-based versions that have effectively replaced bekit's 1105 image ("nvflash_gtablet_2010110500.zip"), at least on my own device - I'm also addding a clockworkmod recovery option. It is being hosted in the same location as my 1.2-based mods - I will be making updates there, from this point on (as I might update them from time to time).
(you'd still need bekit's Windows or Linux tools, keep in mind) I've been able to bring back my device back from a soft-brick several times, so I feel they are usable.
05/09/2011 update -- A reminder that these images are not being updated, here. I have a newer nvflash post over in the same site where I have my 1.2-based mods. The 1105 bekit image mentioned here is still relevant for 1.1-based ROM users, or you can use my 3588 ot 4349 solution at the other site.
05/10/2011 update -- I have PM'd the moderator to either unsticky this post and / or assign it to someone else, as I do not plan on updating it, here. I believe that there is a 3588 image in the TegraTab IRC that someone created, for example.
Looks good Roebeet. I wrote a little how to a while back on tegratab. I know you are aware but for the benefit of others I wanted to add the following.
One little thing is sometimes when you are done you will get a boot loop. I think it only may happen once as I never saw it again. The fix is to go into Clockwork and partition the internal sd card again. The old settings said 512 for memory, and 256 swap. Bekit updated Clockwork and now you can format all the way to 4gb if you like, and swap should be 0 as it is not used.
Edit: New wisdom says not to partition the internal sdcard to anything but 2048. Folks have had issues with memory errors in the market with anything bigger. 0 for a swap is also the recommendation as Android apparently does not make use of the swap.
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
I need help. I finally got Windows 7 to recognize the device in APX mode but how do I flash from this point. It only shows up in my Device list with all the subfolders in it.
What is this for? Restoring to factory Rom?
Thanks,
Scott
cscotty said:
What is this for? Restoring to factory Rom?
Thanks,
Scott
Click to expand...
Click to collapse
Yes, you can use it for exactly that. I believe bekit added Launcher Pro and superuser, but other than that it's a way to completely wipe the device. Moreso than a standard recovery would do.
The pre-req link doesnt work. Can you update the link?
Thanks
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
stanglx said:
The pre-req link doesnt work. Can you update the link?
Thanks
Click to expand...
Click to collapse
It seems to go up and down (it's bekit's dropbox). Try this:
https://www.dropbox.com/s/wrcd87u1iy31u4e
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
Roebeet sorry but I just noticed for noobs that the linux command needs to be
. nvflash_gtablet.sh
Also if you unzip those files into a premade directory such as "gtablet" when you unzip them each have their own directories and if you ls you can see that the bash script isn't executable from there. So you need to copy either the gtablet files into the platform folders or copy all the files inside both into your "gtablet" folder. Then you can run the ". nvflash_gtablet.sh" command and voila. Sorry I am on Ubuntu and don't know if it is different, but that is the way I run them.
No worries - all replies are welcome! the more info we have, the better.
This should be stickied. Nvflash has saved my gtab many times and I think its the reason why my gtab doesn't really encounter too many Force closes. Its the perfect method to ensure your gtab is clean.
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
ehunyadi said:
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
Click to expand...
Click to collapse
My limited experience with 64-bit Win7 -- the drivers have to be signed, or else they won't work. There's a way to disable that on boot, but you can't permanently disable it. I'm wondering if the APX USB driver is signed?
Open a command prompt as an admin and type
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
This is the only way.. dont worry if the test watermark shows up.. it wont affect anything.
Also... They have a x64 driver - read this
http://tegradeveloper.nvidia.com/tegra/forum/adb-usb-driver
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Your gonna have problems later if you don't repartition to 2048 and 0
satishraman said:
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Click to expand...
Click to collapse
You only have 16gb to start. Partitioning you internal to 4gb uses part of that. I would go back and only use 2gb, and 0 for swap. There are things, like the new market that break with anything but 2gb.
If you mean the settings menu is not showing your external sd card that's normal. Look in a file explorer program in the / directory. Look for SDcard2. That is your external. Same deal, look for usbdisk if you plug in a usb drive.
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
romanrish said:
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
Click to expand...
Click to collapse
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
roebeet said:
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
Click to expand...
Click to collapse
Yeah I thought about that, but figured some people might get confused and forget which one was which. Either way works as well just as long as you keep both files. You should edit your original post and add that in as an option to do at the end. It will keep some from having to look through and creating a new post cause they can't find it, and keep our forums clean.
This should definitely be stickied. Mods please?
P.S. I cannot believe how awesome this forum is(Viewsonic G Tablet). I have gone to other forums and the other devs and users are not as friendly and awesome as the ones we have here. Almost brings a tear to my eye. Great job Roebeet, this should help us noobs out a lot. LOL!
Hi,
Because of the need of a bootmanager and the lack of patience to type a hack a lot at the console, I created a ubuntu maverick based build system for arm crosscompiling with a script helps by building kernel, ramdisk, recovery archive, debugging via fastboot and so on. As chroot env it is very flexible, needs not to install something and runs inside all linux distris.
just extract it somewhere onto an ext partition goto the directory and type ./start
in the root of the chroot env is a README file which contains infos where is what. read it before.
it contains three tools
build (a script supports different actions, "build help" shows them)
unpack-boot (extracts a boot image into the actual directory)
unpack-ramdisk (extracts a ramdisk into the actual directory)
Download:
http://www.bisme.net/files/xda/bootbs.tar.bz2
TODO:
the chroot env is still based on a desktop version of maverick and bigger than needed, this will change soon.
PS: Bootmanager is still in work, should finish(as a trivial but working version) in the next days and is the first step to support multiboot different linux installations(also different android versions) on android tablets. But this is another story will get an own Thread here. In the meantime I hope all romcookers out there will have fun with this build system.
So following a couple of tuts that I've found on the forums I've been able to install debian linux wheezy armhf build on my tablet in a dual boot configuration with it booting off of a second ext4 partition on the microsd card along with getting the drivers/codecs from Linux4Tegra to be installed and somewhat used on debian linux.
What works:
-Wifi
-USB
-Display (doesnt use tegra drivers)
-Buttons (power, vol, rot switch [acts as wifi switch])
-Touchscreen
What doesnt work:
-Bluetooth (Untested but apparently it finds it and sets it up.)
-Audio (Detects it in the kde info center. System Settings program only says that there's a dummy output. Playing any form of audio crashes the program.)
-HDMI (with the Tegra gfx drivers it finds it but says it's disconnected even when connected.)
-Cameras
-GPS
-Motion Sensing
-Light Sensor
With the display, whenever the tegra drivers are used, it finds HDMI (as HDMI-1) and the LCD screen (as LVDS-1) but says that there is no device on the lcd screen. With that being said, it is using the fbdev driver instead which shows pink and/or inverted colors in some instances but at least it shows a gui.
Guides used:
{HOW TO} Native Debian on A500 and building your own rootfs
[BOOTLOADER][DUALBOOT + RECOVERY][BOOTMENU] Patched ICS bootloader V8 (07/06/2012)
[Dev] Native linux on Iconia
Requirements:
-an A500.
-a 16+GB microsd.
-Linux OS (Debian, Ubuntu, etc.)
-Linux 4 Tegra: Download the Ventana files under "Additional Information" and "Driver Packages"/"Codec Packages".
Ok, so here's how I've done it.
1) Make sure you have a multiboot loader and have flashed the appropriate bootloader image to the second boot partition. get the boot image from the 3rd guide under "precompiled kernel image" and flash that to the second boot partition. (be sure to check the dualboot guide above on flashing the image if you are using the bootloader that is in the guide.)
2) Have a microsd card partitioned with two partitions, one for normal data (can be any format) and a second one that is in ext4. you can do 3 partitions by adding a swap partition but the ext4 partition must be the second partition.
3) Install qemu on the host system.
Code:
For Ubuntu - sudo apt-get install qemu-user-static
4) Mount the microsd's ext4 partition.
Code:
sudo mount -t ext4 /dev/<microsd 2nd partition> /mnt/Linux
5) Run:
Code:
sudo qemu-debootstrap --arch armhf wheezy /mnt/Linux
6) Chroot into the installed environment.
Code:
chroot /mnt/Linux /bin/bash
7) Add sources to /mnt/Linux/etc/apt/sources.list. you can get debian sources from http://debgen.simplylinux.ch/. Be sure to choose "Testing (wheezy)" and all the sources check boxes along with where you live to find the nearest repository.
8) Install the wifi drivers pt1.
Code:
apt-get update ; apt-get install broadcom-sta-common broadcom-sta-source firmware-b43-installer firmware-b43legacy-installer b43-fwcutter
9) Install the wifi drivers p2. In the "{HOW TO} Native Debian on A500 and building your own rootfs" guide, there is a download from mediafire for the firmware files for the drivers. Extract that and put it into /lib/firmware. I dont know if the individual files in the brcm should be in the /lib/firmware or not so i just copied the folder into it and the files within it into /lib/firmware.
10) Install the GUI:
Code:
apt-get install <gui>
List of GUI's (that i know of):
Code:
KDE (takes a long time to install): kde-full
XFCE: xfce4
11) extract the ventana_Tegra-Linux-R16.1.0_armhf.tbz2 file and the ventana_Tegra-Linux-codecs-R16.1.0_armhf.tbz2. you should get a folder called "Linux_For_Tegra" and a file called "restricted_codecs.tbz2". go into the "Linux_For_Tegra/nv_tegra" folders and extract the nvidia_drivers.tbz2 file. from there you should get 3 folders: etc, lib, usr. copy those to "/mnt/Linux" (you are going to have to do this as root). back out of those folders and extract the restricted_codecs.tbz2. you should get a folder called "lib" copy that to "/mnt/Linux". after that, it's time to make a hard link so that the X11 can find the tegra driver:
Code:
ln /usr/lib/xorg/modules/drivers/tegra_drv.abi12.so /usr/lib/xorg/modules/drivers/tegra_drv.so
Note: without using an xorg.conf file, by default it will use fbdrv instead of the tegra driver.
12) set the root password:
Code:
passwd root
13) add a normal user:
Code:
adduser <username>
14) exit chroot by typing "exit" and unmount /mnt/Linux:
Code:
sudo umount /mnt/Linux
15) pop that sucker into the the tablet and boot into it by holding power and vol down to get into the boot menu. select "boot into second partiton".
If everything went ok, you should be presented with a gui, if not and you are at a command line, log into root and type "startx". if that doesnt work then something wrong must have happened.
Untested easy script:
Code:
#! /bin/sh
set -e
#if there is a tegra_install.deb file.
hasTegraDeb=0
tegraDeb=acer-iconia-tab-a500+tegra+brcm+wheezy_1.0-1_armhf.deb
#change these if you do not like default install of kde.
arch=armhf
build=wheezy
rootDir=/mnt/Linux
guiEnv=kde-full
newUser=User
#setup the basics of debian linux using armhf and wheezy build.
qemu-debootstrap --arch $arch $build $rootDir
#copy the tegra_install.deb file for the tegra specific drivers.
if ["$hasTegraDeb" = "1"] then
cp $tegraDeb $rootDir/$tegraDeb
fi
#setup sources.list for apt-get.
echo "deb http://ftp.us.debian.org/debian testing main contrib non-free" >> $rootDir/etc/apt/sources.list
echo "deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free" >> $rootDir/etc/apt/sources.list
echo "deb http://security.debian.org/ wheezy/updates main contrib non-free" >> $rootDir/etc/apt/sources.list
#create the chroot_install.sh script and set it up.
echo "#! /bin/sh" > $rootDir/chroot_install.sh
echo "set -e" >> $rootDir/chroot_install.sh
#update apt-get inside the chroot.
echo "apt-get update" >> $rootDir/chroot_install.sh
#install the wireless card drivers inside the chroot.
echo "apt-get install broadcom-sta-common broadcom-sta-source firmware-b43-installer firmware-b43legacy-installer b43-fwcutter" >> $rootDir/chroot_install.sh
#install the desktop in the chroot. (note: this will take a long time)
echo "apt-get install $guiEnv" >> $rootDir/chroot_install.sh
#install the tegra specific drivers inside the chroot
if ["$hasTegraDeb" = "1"] then
#install the tegra drivers.
echo "dpkg -i $tegraDeb" >> $rootDir/chroot_install.sh
#hard link the tegra_drv.abi12.so as tegra_drv.so in /usr/lib/xorg/modules/drivers/ to enable X11 to find the display driver.
echo "ln /usr/lib/xorg/modules/drivers/tegra_drv.abi12.so /usr/lib/xorg/modules/drivers/tegra_drv.so" >> $rootDir/chroot_install.sh
fi
#set the root password in the chroot.
echo "passwd root" >> $rootDir/chroot_install.sh
#add normal user in the chroot.
echo "adduser $newUser" >> $rootDir/chroot_install.sh
#execute the final stage of the install.
chroot $rootDir /chroot_install.sh
#cleanup
rm $rootDir/chroot_install.sh
if ["$hasTegraDeb" = "1"] then
rm $rootDir/$tegraDeb
fi
Script sets up everything along with installing kde window manager. Please note that the tegra_install.deb file does not exist, it is something that i am thinking of making in the future that has all the drivers and what not needed that is from the Linux 4 Tegra site. you are still going to have to manually install the tegra drivers in step 11.
Edit: Experimental copies of the deb files that has all the files needed from Linux 4 Tegra and the wifi drivers can be found at the bottom of the post.
xorg.conf to enable tegra driver (found in the Linux_for_Tegra/nv_tegra/config.tbz2/etc/X11 folder):
Code:
# This is the minimal configuration necessary to use the Tegra driver.
# Please refer to the xorg.conf man page for more configuration
# options provided by the X server, including display-related options
# provided by RandR 1.2 and higher.
# Disable extensions not useful on Tegra.
Section "Module"
Disable "dri"
Disable "dri2"
Disable "glx"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
EndSection
Section "Device"
Identifier "Tegra"
Driver "tegra"
# OverlayDepth is a 32-bit integer which is used to control overlay
# stacking order. The overlay with the lowest depth is in front of
# all others. This value has meaning only when multiple overlays are
# present on a display.
# Option "OverlayDepth" "255"
# ARGBHWCursor controls whether the X driver uses an overlay to
# display 32-bit "true-color" cursors, or whether such cursors are
# emulated in software. Valid values are "true" to enable hardware
# cursors, and "false" (default) to disable them.
# Option "ARGBHWCursor"
EndSection
At the moment, I have looked through the config.tbz2 file and may have to stick the stuff in there into the tablet's linux filesystem. will test this later.
NOTE:
I am not a linux developer, I have no idea how to create linux drivers. All I can do is mash things together and hope things work out.
In theory, this should work for all tegra2 and tegra3 (using cardhu drivers instead of ventana) devices with some minor differences.
Edit:
Apparently it is using kernel version 2.6.38. I'm going to see if I can update the kernel to 3.2.23-1 which is the latest version for armhf in the debian package list (http://packages.debian.org/wheezy/kernel/linux-headers-3.2.0-3-all-armhf).
Edit2:
Looks like updating the kernel from apt-get doesn't necessarily enable the kernel to load as it seems that the boot loader loads a prepackaged kernel that has been flashed into mmcblk0p7. Tried out kexec and the kernel doesn't support it so adding it to the /dev/inittab script is useless for loading up new kernels. I tried making the new kernel into a flashable image using mkbootimg that is found within the Linux 4 Tegra folder but it doesn't do anything and the image apparently isn't valid when i tried booting it from fastboot (black screen). along with that, apparently it changed my password on my encrypted /data partition's password (when i flashed it within linux using dd) so a word of caution with that. If anyone can help me out, i would like to try to create something similar to grub (or even port it) where it loads up new kernels from the microsd or a specified place based on a boot list.
deb Files (Install using "dpkg -i acer-iconia-tab-a500+tegra+brcm+wheezy_<version>_armhf.deb" within the linux environment of the tablet.):
1.0-1: acer-iconia-tab-a500+tegra+brcm+wheezy_1.0-1_armhf.deb
--takes care of steps 9 and 11 sans hard linking the X11 tegra drivers.
1.0-2: acer-iconia-tab-a500+tegra+brcm+wheezy_1.0-2_armhf.deb
--has pre-depends for the first part of the wifi driver installation so this should, in theory, install both part 1 and 2 of the wifi drivers.
--takes care of steps 8, 9, and 11 sans hard linking the X11 tegra drivers.
Update log:
10/17/2012: added updated version of the deb package.
10/16/2012: first version.
Ok, so since I cant post anything including into ongoing threads in the android development forum due to the 10 post required thing i'll just have to ask development questions here till i reach the 10 post requirement.
Can anyone point me into the direction for how the second boot image that you flash for the dual boot bootloader is created? Trying to figure out how to create an image so that it boots everything off the microsd card including the kernel. It seems that the kernel used in the guide is locked to 2.6.38 and if you update the kernel within the tablet's linux environment it doesnt load it up. so i need to figure out how to create a boot image so that it loads it up or create a boot image that has grub (or other bootloaders) installed on it to boot different linux images.
alatnet said:
Ok, so since I cant post anything including into ongoing threads in the android development forum due to the 10 post required thing i'll just have to ask development questions here till i reach the 10 post requirement.
Can anyone point me into the direction for how the second boot image that you flash for the dual boot bootloader is created? Trying to figure out how to create an image so that it boots everything off the microsd card including the kernel. It seems that the kernel used in the guide is locked to 2.6.38 and if you update the kernel within the tablet's linux environment it doesnt load it up. so i need to figure out how to create a boot image so that it loads it up or create a boot image that has grub (or other bootloaders) installed on it to boot different linux images.
Click to expand...
Click to collapse
You are on the right track with mkbootimg. I have not figured it all out myself yet.
You have to compile your arm linux kernel then make a bootable image with mkboot
I don't know if you have seen this or if. this will help---Nethams kernel compile commands are;
make ARCH=arm menuconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueable--j16
./mkbootimg --ramdisk dev/zero --kernel arch/arm/zimage -o ../recovery.img
I believe these are the commands he uses to compile his recovery image (boot.img)
It is my understanding that mkboot combines the kernel with a ram disk to make an image file that will boot the system
That image file can be placed in several places 1-primary boot position 2 recovery position 3 and if you have Skrilax dual boot secboot position
So it depends on what mkboot compiled as to what happens when that boot point is activated.
I am still trying to work out how Spdev and Netham combine or configure the kernel + initramfs+ ramdisk to create their bootable images.
I know these images boot and point to the file system which can be stored on internal or external sd card or even usb drive it all depends on how the boot image is configured.
Still learning myself
Here is a link I found explanes about Linux ram disk and initram
http://www.ibm.com/developerworks/linux/library/l-initrd/index.html
And more info here downloads a PDF presentation on how to.
http://www.google.com/url?sa=t&rct=...poCoAw&usg=AFQjCNHLTHE3DaroC71FAjOjQWU2A61qEQ
All about that mkbooting after you get your kernel
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
themechaniac said:
snip (freaking 10 post limit...)
Click to expand...
Click to collapse
Yea, i did find some stuff with mkbootimg including the last link that you posted.
The kernel was already compiled when i downloaded it using apt-get and it is placed in /boot folder.
I did make a boot.img from that kernel using mkbootimg and looking at "/proc/cmdline" at the arguments that were passed to the kernel in the other kernel image and it made it, flashed it to secboot and it didnt do anything except use the same kernal as before, though i did flash the image via dd in linux. Apparently this sorta screwed up my /data partition or something in where it wouldnt recognize my password for de-encryption to mount it. (fixing it by just erasing "/data" [bye bye data... TT.TT]) So i tried booting it using "fastboot boot <kernel>" and it didnt boot, only showing a black screen, but using the other boot.img it would boot linux up.
So I'm thinking of somehow creating a kernel image that can use kexec to make a grub like bootloader kernel that you flash onto the secboot partition that has something similer to grub.cfg in which you can easily select which kernel to load.
As for looking for a grub.cfg file, it would look in a few different places:
-in internal storage (probably recovery partition or the "/system" partition as the "/data" partition can potentially be encrypted and not mountable.)
-sd card (has to be in first partition and in fat32 format)
-usb drive (same as sd card)
from these places it will load each grub.cfg. that way it'll make the grub like bootloader kernel extendable in which kernel to load (i.e. have a linux system on usb that you want to boot from.)
I may be wrong but it is my understanding that the compiled kernel is in the boot image packed by mkbootimg.
The kernel is compiled to look for the compatible root file system in a particular place.
So when you change or use a boot image you change the kernel you are using.
So we have a system that;
Has a modified Linux kernel that selects the Android file system from internal memory installed in the first boot position.
We can put a Linux kernel compiled to find a compatible root file system say on external sd card in the second boot position.
We can replace the recovery image with a Linux kernel that finds a compatible root file system on the internal sd card.
That gives us a hardware selective three different systems (triple boot)
With fastboot on the PC we can quickly change any of the Three boot images, replace the recovery image or repair system.
I think all we need is a 3.2.23 kernel compiled thee separate ways and packaged with mkbootimg.
1st find root file system internel, 2nd find file system externel 3rd find file system usb
We already have two 2.6.38 kernels. One from Spdev (external root file system)and One from Netham {internal file system)
They are different kernels as Nethams has added modules.
I believe the were both compiled from the same Git.
I have tried switching the two boot images in second boot position with both root file systems installed and when you boot the second position
it switches to it's own file system.
I haven't tried swapping the root file positions yet.
themechaniac said:
I may be wrong but it is my understanding that the compiled kernel is in the boot image packed by mkbootimg.
The kernel is compiled to look for the compatible root file system in a particular place.
So when you change or use a boot image you change the kernel you are using.
So we have a system that;
Has a modified Linux kernel that selects the Android file system from internal memory installed in the first boot position.
We can put a Linux kernel compiled to find a compatible root file system say on external sd card in the second boot position.
We can replace the recovery image with a Linux kernel that finds a compatible root file system on the internal sd card.
That gives us a hardware selective three different systems (triple boot)
With fastboot on the PC we can quickly change any of the Three boot images, replace the recovery image or repair system.
I think all we need is a 3.2.23 kernel compiled thee separate ways and packaged with mkbootimg.
1st find root file system internel, 2nd find file system externel 3rd find file system usb
We already have two 2.6.38 kernels. One from Spdev (external root file system)and One from Netham {internal file system)
They are different kernels as Nethams has added modules.
I believe the were both compiled from the same Git.
I have tried switching the two boot images in second boot position with both root file systems installed and when you boot the second position
it switches to it's own file system.
I haven't tried swapping the root file positions yet.
Click to expand...
Click to collapse
Interesting. Though i think it needs to be a specific type of kernel (i.e bzImage or uImage instead of vmlinuz) to actually run. also, the precompiled kernel in the guide that i had used in the opening post had a command line where one option was "root=/dev/mmcblk1p2" which pretty much says for the kernel to look for the linux file system in the second partition on the sd card.
Yes with the way the system is formatted you cannot change out the kernel on the fly. It is basically hard coded in the boot image. Skrilax has given us a way to change boot positions so we don't have to sacrifice recovery position to boot second kernel. I have not seen any pre configured 3.2.23 kernels yet. The one that Netham posted boots from internal SD but causes problems for some people as not all a500 have their internal SD card formatted in the same memory block. It works great for me I prefer to have my root file system on a fast external SD so would like to modify or compile a kernel like Netham's. I find I run out of space when I have it internal. Netham's kernel has USB sound and seems to boot differt than Spdev's.
themechaniac said:
Yes with the way the system is formatted you cannot change out the kernel on the fly. It is basically hard coded in the boot image. Skrilax has given us a way to change boot positions so we don't have to sacrifice recovery position to boot second kernel. I have not seen any pre configured 3.2.23 kernels yet. The one that Netham posted boots from internal SD but causes problems for some people as not all a500 have their internal SD card formatted in the same memory block. It works great for me I prefer to have my root file system on a fast external SD so would like to modify or compile a kernel like Netham's. I find I run out of space when I have it internal. Netham's kernel has USB sound and seems to boot differt than Spdev's.
Click to expand...
Click to collapse
Right, but this is how the linux boot loader is going to go with, instead of loading the linux system (sans kernel and initrd) from the sd card, we create a boot.img that has a linux system built in that has a sole purpose of loading other linux systems using kexec.
Edit:
Here's how the path is going to go:
Startup-->Bootloader-->Linux Bootloader (loads linux on external drives)-->Linux (on external drives)
Well I am happy with Ubuntu on my external SD card, I even ran a kernel compile on it and it ran pretty fast. I am stuck on the mkbootimg part. It can't be done on the tablet, has to be a PC. I tried unpacking the Two ready made boot images to see how they are configured but they don't seem to have a ram disk. Still working on that. It is learning how the system is put together that is half the fun, Getting it to work the way you want is the goal. When it is all squared away it will be time to move on to the next puzzle. I have enough computers that I could just put a system on each one and be done with it. Where's the fun in that. Most of them are dual booted already.
themechaniac said:
Well I am happy with Ubuntu on my external SD card, I even ran a kernel compile on it and it ran pretty fast. I am stuck on the mkbootimg part. It can't be done on the tablet, has to be a PC. I tried unpacking the Two ready made boot images to see how they are configured but they don't seem to have a ram disk. Still working on that. It is learning how the system is put together that is half the fun, Getting it to work the way you want is the goal. When it is all squared away it will be time to move on to the next puzzle. I have enough computers that I could just put a system on each one and be done with it. Where's the fun in that. Most of them are dual booted already.
Click to expand...
Click to collapse
Well, even though mkbootimg is suppose to be run on linux, i don't think it was compiled for arm so you are going to have to use a pc for that program. as for the initrd, i did find a website that may help in creating an A.L.B.L. (Android Linux Boot Loader): http://www.thewireframecommunity.com/node/14
Essentially what is needed to create the A.L.B.L. is to create a kernel with kexec in it and an initrd that mounts the external drives along with an easy to use interface to be loaded before loading any kernels to allow for selecting kernels. with that said, how do you figure out how to use the volume buttons and the power button within linux using a c\c++ program?
BUMP!
any progress?
also
-Audio (Detects it in the kde info center. System Settings program only says that there's a dummy output. Playing any form of audio crashes the program.)
Click to expand...
Click to collapse
But
Code:
cat /any/file/for/ex/bin/bash > /dev/dsp
works properly
Unfortunetly no.
Been to busy with other stuff to work on this.
tegra driver
I have ubuntu 12.10 armf runing on my a500 thanks to the "Linux on A500: The Future" thread. I am using the ferrariforzaleo mod of rogro82's kernel.
The problem I had was getting the xorg tegra module to load. I fixed this by getting the "https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1"]https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1 and installing with
sudo dpkg -i
after I rebooted it started using the tegra video driver.
Cheers
HardlyAbelson said:
I have ubuntu 12.10 armf runing on my a500 thanks to the "Linux on A500: The Future" thread. I am using the ferrariforzaleo mod of rogro82's kernel.
The problem I had was getting the xorg tegra module to load. I fixed this by getting the "https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1"]https://launchpad.net/ubuntu/quantal/armhf/nvidia-tegra/16.0-0ubuntu1 and installing with
sudo dpkg -i
after I rebooted it started using the tegra video driver.
Cheers
Click to expand...
Click to collapse
can you explain me the steps you done ? I also want ubuntu 12.10 running but I can't install any desktop on it ( show error and other error )
ubuntu 12.10
Forzaferrarileo said:
can you explain me the steps you done ? I also want ubuntu 12.10 running but I can't install any desktop on it ( show error and other error )
Click to expand...
Click to collapse
Hi, I used the debootstrap and and qemu / chroot to setup my rootfs. i found post #61 in the "Linux on A500: future" very helpful.
Also, make sure you have a usb keyboard handy. After you run "apt-get install -d ubuntu-desktop" (assuming you have a pc running ubuntu to use) in a qemu chroot, you can move to the a500 and boot up and login as root and run "apt-get install ubuntu-destop". since the stuff is cached. I found this faster than installing the desktop while in the chroot. After that finishes, you should boot up with a desktop available. If something is wrong and you can't login, try doing "ctrl-alt-f1" to get to the getty command line login and look at the /var/log/ folder for clues in the logs.
How to compile the kernel?
I succesfully got debian running on my iconia a500 :laugh:
Building my own rootfs and getting the wifi to work were not that hard, but I still don't know how to compile the Linux kernel for the a500 from source.
I already found the git repository of rogru82 (https://github.com/rogro82/picasso-kernel) and I downloaded the source to my pc (running ubuntu 13.04). Can someone point me to a tutorial explaining how to compile this source?
Also, can someone explain what sort of partition table the internal memory uses? I am running the 3.0 kernel and I can see a block memory device in the /dev folder but there are no partitions. How can I mount the internal memory?
###############-------------------------------------WARNING-------------------------------------------------------##############
I AM NOT RESPONSIBhttp://youtu.be/Zl767IukT5sLE FOR ANY REPERCUSIONS FROM FOLLOWING THE INSTRUCTIONS
LISTED BELOW. THIS INFORMATION IS PROVIDED AS IS AND DOES NOT IMPLY FUNCTIONALITY
OR SAFETY FOR YOUR DEVICE. PROCEED AT YOUR OWN RISK.
##########################################################################################
I realize this should probably be posted in the Development forum, however I am relatively new to the TF300T and xda will not allow me to post it there.
REFERENCES
Kernel and initramfs are taken from [DEV] ArchLinux on the TF300T(G) which is credited to cb22, with a few modifications of my own to the initramfs to allow ubuntu to boot.
The root filesystem is based on an image I found created by lilstevie for the tf201. From everything I researched the tf201 is nearly identical to the tf300t so it boots extremely well. If the original disk image is flashed to a microSD and the original kernel from the ArchLinux post is used the system is more stable. However my method below was adapted to work with the internal storage, and still works nearly as well.
WORKING
Power Management - Shutdown, Reboot, Battery Status
USB Host Controller
SD and microSD slots
NetworkManager
Ethernet works with a USB Ethernet adapter. I'm using an RTL8150.
Dock Keyboard
Updates Work -- I just don't recommend doing an Upgrade at this time since I haven't tried it. All my experience with getting 12.10 running
shows some problems with Unity which I cannot resolve yet.
You tell me....
NOT WORKING
WiFi -- should be working soon, just need to talk to cb22 since it works in ArchLinux
3G -- same as WiFi for TF300TG models
TouchPad -- data is visible just need driver from cb22's ArchLinux
Touchscreen -- same as TouchPad
Sound -- gets picked up by Ubuntu however no sound can be heard, likely just a setting somewhere
You tell me....
REQUIREMENTS
Asus TF300T
Requires the JB bootloader so you must be updated to atleast 10.4.2.13 Stock Firmware ONLY
--I will try and release a compatible boot blob for Cyanogen builds.
Keyboard Dock
USB Mouse
INTRO
[UNOFFICIAL][TF300T] Ubuntu 11.10 v0.01 Alpha for Asus Transformer Pad TF300T (G untested)
The system installs on the internal storage on the data partition. Installation is the same as for cb22's ArchLinux port.
Part 1 - Kernel Blob
Reboot your device into fastboot mode.
From your computer run:
fastboot flash staging hybridubuntu.blob
fastboot reboot
Your system should now reboot back to Android OS.
Part 2 - Root Filesystem
First copy the rootfs (ubuntu.tar.gz) to your device's internal SD.
Either through adb or the android terminal run the following:
su
cd /media
mkdir linux
chmod 755 linux
cd linux
tar -xzvf /data/media/linux.tar.gz
Lastly, to control which OS is booted the boot blob checks for the file .boot_linux in /storage/sdcard0 or /data/media/
To create the file just run the following commands in adb or terminal:
su
touch /data/media/.boot_linux
chmod 755 /data/media/.boot_linux
Reboot and your system will boot into the Ubuntu 11.10 Configuration followed by the desktop.
To get back into Android just remove the file from within Ubuntu and restart.
*Note the Data partition isn't getting mounted in this release so when you open the terminal run the following:
sudo mount /dev/mmcblk0p8 /mnt
sudo rm /mnt/media/.boot_linux
If anyone has any questions or problems please feel free to let me know.
DOWNLOADS
Kernel Blob - http://depositfiles.com/files/j1mlor3v1
RootFS Tar Ball - http://depositfiles.com/files/rjhu1pwuo
Root Disk Image - http://lilstevie.geek.nz/downloads/ubuntu.img.gz_11.10-0.1a_TF201_52f6273e6ad672358d2ebb181b24c200
This is going to bring a lot of excitement! Hope the development goes smoothly and you're able to work out the kinks.
Hi gjx86,
Im working with your kernel blob and root disk image: wired network works (module dm9601.ko), I can login to ubuntu via ssh.
One important issue with dock keyboard - it hangs after 5-10 min. I can kill gnome session using ssh and keyboard start again, but after few min it hangs again.
Btw, hdmi not working.
How You can use microSD as root file system:
" If the original disk image is flashed to a microSD and the original kernel from the ArchLinux post is used the system is more stable."
Why 11.10 and not 12.04? :'(
Ubuntu 12.04 Kernel and Rootfs
Hey,
I just realized that the Ubuntu porting going on for the TF700 runs on the TF300T!!
Check out this link: http://forum.xda-developers.com/showthread.php?t=1988174
There is an image for Unity2D their however so far I've found the Lubuntu to be the most stable.
I am in the process of replacing the firmware with that from the TF300T, specifically the WiFi firmware and driver needs to be rebuilt. I will post an updated TF300T kernel asap and a modded root that will allow WiFi to work.
Have fun and any feedback on issues specific to the TF300T would be great, thanks.
gjx86 said:
Hey,
I just realized that the Ubuntu porting going on for the TF700 runs on the TF300T!!
Check out this link: http://forum.xda-developers.com/showthread.php?t=1988174
There is an image for Unity2D their however so far I've found the Lubuntu to be the most stable.
I am in the process of replacing the firmware with that from the TF300T, specifically the WiFi firmware and driver needs to be rebuilt. I will post an updated TF300T kernel asap and a modded root that will allow WiFi to work.
Have fun and any feedback on issues specific to the TF300T would be great, thanks.
Click to expand...
Click to collapse
That's exactly what I'm up to... trying to make firmware and modules from cb22's arch to work with Lubuntu (I tried Ubuntu first but couldn't get past the log on screen, something about ICEAuthority if I remember correctly.
Let me know if there's anything you need help with... I'm kinda taking my first steps with linux but I know how to google! :laugh:
Touchpad and 3G works
gjx86 said:
There is an image for Unity2D
Click to expand...
Click to collapse
First of all thank you for your efforts.
The second good thing for me - tried this TF700 Unity2D image - it works. Touchpad and 3G works also for me
I did notning special - just flashed your kernel and tried several rootfs.
btw. I have extracted rootfs for Nexus 7 Ubuntu 12.10. May it be useful to post it here?
At least it boots But with rotaded screen and without Unity
This looks awesome! I'll try as soon as I can! Only thing, can you upload it to another mirror? It's quite annoying to only be able to download 1 file every 20 min from DepositFiles... Also DepostiFiles is extreamly slow. 1 hour to download...
great work guys!
I want to be able to boot Backtrack.
Just decided that I wanted to dual boot Linux, so very interested in this. Just one question: I'm assuming that as I would need to flash a blob using fastboot that I would need to be unlocked. Is this the case as it is not specified?
Thanks,
Stephen.
Another question: as it's based on cb's kernel which is based on unter's kernel I think this won't work with AOSP based ROMs I think because they have another kernel?
@pukeboy: As you need to be unlocked to flash recovery's via fastboot I think you need to be unlocked to flash kernels too
So, I have rooted my stock JB running the latest firmware. Would it be possible to flash this Ubuntu when it's already been rooted? If so, is there a chance I can destroy the bootup that I can't recover from with my ClockworkMod Recovery?
I'd really love for this to work!
It'd be a fun desktop experience
Keep up the awesome work, and no offence to the guy doing ArchLinux (which is awesome!), but ArchLinux is just too hard for me to use. I'm not much of a Linux Power User, so Ubuntu is numba 1!
Keep up the good work GJX, big up to both you and CB22 working on Arch!
By the way, isn't the mounting of the stock filesystem just a quick fix in /etc/fstab?
What about progress?
What about porting rabit's Ubuntu from TF700 thread? They have Ubuntu working now only with small bugs.
need some help
In the last two days i tried to port rabits (http://forum.xda-developers.com/showthread.php?t=2026919) native ubuntu solution to the TF300T. I followed the Instructions on this github page: https://github.com/rabits/tf700
I compiled the ASUS TF300T stock kernel code with rabbits .config file. Packed the compiled kernel together with rabits ramdisk and flashed everything to the boot partition. But i wasn't able to boot into the multiboot menu. The tablet just booted into android. Has somebody an Idea why this isn't working? Maybe in the kernel config? Do I need to change something in the ramdisk?
Thanks for your help
any news ?
Qub! said:
In the last two days i tried to port rabits (http://forum.xda-developers.com/showthread.php?t=2026919) native ubuntu solution to the TF300T. I followed the Instructions on this github page: https://github.com/rabits/tf700
I compiled the ASUS TF300T stock kernel code with rabbits .config file. Packed the compiled kernel together with rabits ramdisk and flashed everything to the boot partition. But i wasn't able to boot into the multiboot menu. The tablet just booted into android. Has somebody an Idea why this isn't working? Maybe in the kernel config? Do I need to change something in the ramdisk?
Thanks for your help
Click to expand...
Click to collapse
OK
I heave today don nasty staff
i used Kernel Blob from first post
and rabits / tf700 ubuntu 12.10 rootfs-ubuntu-12.10-0.8.0.tar.lzma (687 Mb) from http://forum.xda-developers.com/showpost.php?p=34655444&postcount=1
extracted rootfs-ubuntu-12.10-0.8.0.tar.lzma to /data/linux
flashet hybridlinux.blob from Kernel Blob
created file .boot_linux in /storage/sdcard0
rebooted tf300t
and walla ubuntu on
i heave no time to play with tf300t but i tray and started ubuntu 12.10 in 20 min.
i heave 2 hurs more to tray more
P.S. no credits to me. I joust play Lego on tf300t
P.S.S don't bee sad on me if something not leagal ( copyright ) or so
Sorry for me bad English
Edited
Simple multi boot ?
create file .boot_linux in /storage/sdcard1 (external sdcard)
remowe external sdcard - boot to android
insert sdcard - boot to ubuntu
Keshukas said:
OK
I heave today don nasty staff
i used Kernel Blob from first post
and rabits / tf700 ubuntu 12.10 rootfs-ubuntu-12.10-0.8.0.tar.lzma (687 Mb) from http://forum.xda-developers.com/showpost.php?p=34655444&postcount=1
extracted rootfs-ubuntu-12.10-0.8.0.tar.lzma to /data/linux
flashet hybridlinux.blob from Kernel Blob
created file .boot_linux in /storage/sdcard0
rebooted tf300t
and walla ubuntu on
i heave no time to play with tf300t but i tray and started ubuntu 12.10 in 20 min.
i heave 2 hurs more to tray more
P.S. no credits to me. I joust play Lego on tf300t
P.S.S don't bee sad on me if something not leagal ( copyright ) or so
Sorry for me bad English
Edited
Simple multi boot ?
create file .boot_linux in /storage/sdcard1 (external sdcard)
remowe external sdcard - boot to android
insert sdcard - boot to ubuntu
Click to expand...
Click to collapse
Which ROM did you use with this? I tried with CleanROM with no success.
I use stock 10.4.4.20 rooted and unloked .
Sent from my GT-I9100 using xda app-developers app
This guide was written to provide more specific information for installation instructions than the OP below.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
OP for Tubutnu by x3maniac
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Instructions for installing new kernels for SBK1.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.2. Download the updated kernel from the OP.
a. Extract the .img file into the \bins directory of the installation application. You do not need to rename it because the command you enter in step 3 part b indicates the name of the kernel file.3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 6 whatever_the_kernel_filename_is.img
c. The filename is the name of the kernel you extracted and copied into the \bins directory. This name can really be anything so long as the command you enter reflects that filename.4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android. Boot to Linux now.
6. Download the supplemental kernel file to the root of your filesystem That is the / directory.
a. Open terminal and type this and press enter: sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
b. Then type this command and press enter: sudo tar zxvf /kernel_sup.tar.gz
c. This supplemental is installing modules and drivers to the appropriate locations.
d. Reboot.7. Please understand names of files especially the kernels and updates will change periodically. The commands and methods of extracting have not changed at this point so substitute the appropriate filename and you should be good to go.
For SBK1 devices, the installation of a custom Android ROM using recovery is very similar to updating the kernel instructions in the post above.
Instructions for installing custom ROM's for SBK1 with Lubuntu installed.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.3. Copy the file cwrrecovery.img to the \bins folder.
a. You should be able to substitute a newer recovery file than what comes with the Tubuntu installation application.2. Download the zip file of the custom Android ROM you wish to install.
a. Copy it to either your Internal SD card or External SD card. Depending on the recovery version you flash you may not be able to use your Internal SD card.3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 cwrrecovery(orwhateverfilenameyourrecoveryis).img
c. The filename cwrrecovery.img is the name of the recovery that comes with the installer application. Please substitute appropriately if you are going to flash a different recovery application. You can also use TWRP just use the appropriate .img file name.4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android.
a. Now you want to boot to the Android recovery. Do that by powering off the tablet and booting like normal into recovery mode. This should be volume down and power. Hit volume up when prompted to do so. Flash your ROM according to the ROM owner's instructions. I recommend to complete your ROM's installation set up before proceeding to step 6.6. You must now flash your Tubuntu Linux kernel back or you will not be able to boot into Linux. Follow the instructions again from the \bins directory using the command prompt and putting your tablet back into APX mode which is volume up and the power button until the Tubutnu installation application shows green for APX Detected.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 whatever_the_kernel_filename_is.img
c. Type this command and hit enter: nvflash -r --go7. You should now be back into your Android ROM again. From here simply power off and boot into recovery using volume down and power. Then hit volume up when it says to on the screen. If Linux boots without issue then you have successfully reinstalled your kernel.
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
Click to expand...
Click to collapse
sainthout said:
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
Click to expand...
Click to collapse
0.4.7 fixes the issue with sbk1 and you don't have to do it with these instructions anymore.
However I did try the newer kernel and got stuck at the same spot you did using my instructions just before the 0.4.7 was uploaded. Go to the original thread and post the issue there.
Thanks for the quick reply! Will post the issues
Outdated Thread But Valid Information
This thread is now outdated. X3Maniac has updated his Tubuntu installation application (0.4.7) to fix the issues with installing kernels and recoveries for SBK1 devices.
The information in this thread is still valid for behind the scenes and you can still use the wheelie and nvflash as standalone items if you wish to do something with your device outside the scope of the main thread.
Thanks for all the thanks from users!
Found a bug with 0.4.7. It's possible the tab may not reboot into Prime automatically with this version. When the dev has time it will get updated. If it doesn't reboot and the Tubuntu application says everything is done, manually hold power and let it reboot to Prime to finish installation.
question..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Click to expand...
Click to collapse
i just succeeded dual booting into ubunto.the prime rom just booted...can i install eos jb rom and still dual boot to ubuntu? thanks in advanced
Yes you can. You will need an updated recovery .img file that supports jb. You temporarily flash the new recovery boot into it then install the new rom. See my post on installing updated android roms. Its the third one I think.
oh sorry for the silly question,,i got it now thanks a lot.. nice job
Hi there,
First off, thanks for the tutorial and hard work!
I've been able to successfully install Lubuntu v1.2 and Lubuntu V1.1-rc1 but I've run into issues with both that I'm hoping you can help me with.
When I installed v1.2, my wireless adapter didn't work and I wasn't able to copy any files (kept saying I was out of space, probably a mounting issue).
When I installed v1.1-rc1, things seemed to work well (wireless worked) but when I tried to upgrade the kernel to 3.1 following the instructions, my mouse pad stopped working and so did my wireless adapter again. I saw that there is a way to fix the mouse pad but it seemed to require an internet connection. Any idea what I did wrong or how to fix the wireless on either v1.2 or on v1.1-rc1 with the 3.1 kernel?
Thanks!
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
TomTcom said:
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
Click to expand...
Click to collapse
Awesome, works like a charm. Thanks again!
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Treizy said:
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
See KingZaks post for sound settings. It's in the op and his signature.
The clicking shouldn't do that every time. Did you extract the supplemental zip and are you using the 1.2-1.6ghz kernels?
Hmm, I'm thinking of installing fresh to see if things get fixed. Is there a way to do that without touching the Android partition? I don't want to have to reflash EOS and what not. Do I just not include the Prime img in the images folder?
Thanks!
A Terribly Confused Noob!
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
TheArtfulDodger said:
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
Click to expand...
Click to collapse
Hey Sparky, there's no more active development on this just so you are aware. That means you can make your own images for newer Linux builds if you wish but things such as hardware acceleration and kernels will not be updated.
In step 1 of my guide you are going to the OP link by the dev who made the Windows based Tubuntu application.
Go to where you see these links:
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
Download tubuntu v0.4.2beta (78mb).
Download tubuntu v0.4.7 (1mb).
Extract the files to whatever location on your Windows machine.
The 1mb file is a replacement of tubuntu.exe file. So just copy/paste and overwrite that file on your Windows machine.
Do you know how to put your tablet in APX mode? If not, you open tubuntu.exe (you might need .net 4.0 Microsoft framework to run the tubuntu.exe). With the tablet off and usb connected to your windows machine, hold volume up and power. The application tubuntu.exe should have a green indicator that it's connected. Change the dropdown to sbk1.
From there you can choose how you want to flash, such as android as the default boot and linux as the secondary boot.
Ignore.