Database Info

[HowTo] Native Ubuntu - Post Install Questions Here not in [DEV]

PLEASE DO NOT POST QUESTIONS ON HOW TO GET THIS TO WORK IN THE [DEV] Native Ubuntu !! THREAD... POST THEM HERE
I would like to thank all those who spent a lot of time working on this project. I do not have the required skills and have not contributed other than writing this tutorial. This is a combination of steps and files from the Nvflash unbricking released! and [DEV] Native Ubuntu !! threads. Please thank those who brought this to us!
The download contains the windows drivers and dlls for this to work (thanks to Bumble-Bee (Apache14), rayman84) and my edits of Jhinta's scripts flash.sh and restore.sh. All I did was convert the coding from linux to windows.
Downloads are in the first post of the DEV forum with the newest version from 15 July.
Disclaimer:
Please be aware that this may cause your transformer not to boot. If this happens please see the Nvflash thread above to restore to Prime 1.4. After this you can install a recovery to flash any rom you want. YOU COULD LOSE ALL YOUR DATA but if all goes to plan you will not. Neither I nor any of the devs are responsible for any damage or loss of data.
This should not affect any data from your Android Install.
It only changes the boot.img and boots a root file stem that is located on the removable Micro SD card. When restoring android this will restore the boot.img (from prime) which will allow you to boot into your android ROM without making any changes.
Tutorial:
Backup!!
Code:
1. Backup everything
Download and unzip required files
Code:
2. Download Nvflashtf.zip file above (files from 10 Jul 2011) and unzip
3. Download the rootfs and unzip (available in [URL="http://forum.xda-developers.com/showthread.php?t=1147062"][DEV] Native Ubuntu !![/URL])
4. Place unzipped rootfs.ext2 in /removable/microsd/Ubuntu
(You will need to create the ubuntu folder)
Boot into APX mode
Code:
5. Plug your transformer into your computer using the USB cable
6. Shut down your transformer (cable must be plugged in)
7. Boot into APX mode: Hold down the Vol+ and Power buttons.
The screen will not turn on but the computer will recognize the transformer
Install Windows Nvflash Driver
Code:
8. Install the new drivers provided in the download folder
(Control Panel --> Device Manager --> APX Device -->
Update Driver --> Choose from file --> Navigate to unzipped Nvflashtf folder
--> Select usbpcdriver directory
9. Accept the warning message stating the driver is not signed
Install Ubuntu boot.img
Code:
10. If it is not already, Put transformer into APX mode (steps 5-7)
11. Navigate to the unzipped nvflashtf folder
12. Run (Double Click) flash.bat
13. Transformer will Say "!!!!!phone update successful!!!!!"
14. Eject APX device from windows
15. Reboot Transformer (Hold Power for 10 seconds) then press power
Connect to an Open Wifi Access point
Code:
16. Open Terminal and run
sudo ifconfig eth0 down
sudo iwconfig eth0 mode managed
sudo iwconfig eth0 essid "my network"
sudo ifconfig eth0 up
Open WICD Manager and click connect
Password is astf101
If your network uses encryption see the second post
Revert to Android boot.img
Code:
1. If it is not already, Put transformer into APX mode (steps 5-7)
2. Navigate to the unzipped nvflashtf folder
3. Run (Double Click) restore.bat
4. Transformer will Say "!!!!!phone update successful!!!!!"
5. Eject APX device from windows
6. Reboot Transformer (Hold Power for 10 seconds) then press power

Tips and Tricks
Working
Code:
Wifi - using terminal commands
Audio - Headphone Output only
Touchscreen
USB Host
Not Working
Code:
Touchpad (on dock)
HDMI Audio Out??
Speakers
Battery Stats
For future development including fixes being worked on please see the [DEV] thread
Scan for wireless networks
Code:
iwlist eth0 scan
Connect to encrypted networks
Code:
WPA:
sudo ifconfig eth0 down
sudo iwconfig eth0 mode managed
sudo iwconfig eth0 essid "nameofmyrouter"
sudo iwconfig eth0 key s:mypassword
sudo ifconfig eth0 up
[URL="http://forum.xda-developers.com/showpost.php?p=15528059&postcount=252"]WPA2[/URL]: thanks to belzebub40k
Automated Script for Wifi on Boot: Thanks to lugiber
advanced iwconfig information
Changelog
If you have any tips and tricks please post them here or PM me.

suggestion: maybe post the bugs/ working/ and being worked on. * just saying, so not so much clutter in this thread

I was building this very kind of zip archive and instructions for it earlier but got interrupted. I'm waiting for my backordered dock to arrive before I try ubuntu. This will be helpful.

Just to confirm then, you would need to switch the boot image via PC when you wanted to switch OS then?
BTW - thanks for the writeup, and directing traffic out of the dev thread.

DroidxRage said:
Just to confirm then, you would need to switch the boot image via PC when you wanted to switch OS then?
BTW - thanks for the writeup, and directing traffic out of the dev thread.
Click to expand...
Click to collapse
yep. 10 characters

Wow...this looks totally manageable. Thanks for the Guide!

What file system does the (micro) SD card need to be? I heard in the dev thread that it only works with FAT32, which would suck since it has a 4 GB limit (and I have a 16 GB card).

rdnetto said:
What file system does the (micro) SD card need to be? I heard in the dev thread that it only works with FAT32, which would suck since it has a 4 GB limit (and I have a 16 GB card).
Click to expand...
Click to collapse
no sir FAT had 4 GB limit. You are good with 16GB FAT32.
I'm loving 3.1 right now. I may try this down the road.

EDIT: Disregard this post =.= I managed to post in the wrong thread... might fill this in later...

EDIT: Alright... I managed to mis-post again... I'm really sorry for spamming your thread, OP, I must look like an idiot. Can someone please remove my posts... these were meant for the developement Ubuntu thread

ToyTank said:
no sir FAT had 4 GB limit. You are good with 16GB FAT32.
I'm loving 3.1 right now. I may try this down the road.
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/FAT32 said:
The maximum possible size for a file on a FAT32 volume is 4 GiB.
Click to expand...
Click to collapse
You must be thinking of the volume size. The file size limitation is the main reason everyone uses NTFS on Windows these days (improved access controls being the other reason).
The filesize limitation is why MS went to the trouble of creating exFAT - FAT32 can handle TB sized volumes, and journalling file systems like NTFS shorten the lifespan of flash media.

GadgetViews said:
suggestion: maybe post the bugs/ working/ and being worked on. * just saying, so not so much clutter in this thread
Click to expand...
Click to collapse
I wish I could do this, but unfortunately this will only be updated in the DEV thread. I will try to add some things in the second post to help with this.

rdnetto said:
What file system does the (micro) SD card need to be? I heard in the dev thread that it only works with FAT32, which would suck since it has a 4 GB limit (and I have a 16 GB card).
Click to expand...
Click to collapse
Main thing was buidling it , now add and fix optional things.
soon

When restoring to android, it restores the previous system state, or a fresh install of prime?
Are there any developments in order to make a dual boot mode along with standard Android?
This kind of implementation are great: http://www.alwaysinnovating.com/, allowing switch between os without restart. I would love to see some thing like this in the transformer.
Good work!

That stuff is kinda secondary. They're mostly trying to get ubuntu fully working right now. But if you have any good ideas for a dual boot process please share. Also it restores the previous rom on. It never actually touches the system or data partition.
Sent from my HTC Vision using XDA Premium App

Where is ubuntu installed? Internal mem? and can we you it with just the touchscreen? I haven't bought a keyboard yet.

SwiftLegend said:
Where is ubuntu installed? Internal mem? and can we you it with just the touchscreen? I haven't bought a keyboard yet.
Click to expand...
Click to collapse
It's ran from the root.fs on your sd card. The actual sdcard.
Sent from my HTC Vision using XDA Premium App

david279 said:
That stuff is kinda secondary. They're mostly trying to get ubuntu fully working right now. But if you have any good ideas for a dual boot process please share. Also it restores the previous rom on. It never actually touches the system or data partition.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I will update the OP to more prominently reflect that this does not modify the current install of android other than the boot.img

So far, mp3 playback and sound is very good. I have a question about the flash plugin, I recall that the Jhinta had a snapshot of Youtube up. I am unclear how to get the plugin, has anyone else gotten this working? Thanks in advance, loving this!

[US/WW/JP/TW/DE/TB] One-Click Universal root for stock firmware - V4

Here I am again...
This time I have written a shell script (linux only) and made a live-cd (for all windows/linux users) to automatically root the stock firmware on the TF101. Every stock firmware.
Today in Europe Asus rolled out the 3.2 upgrade. If you are on stock and you have alredy upgraded then download attached tar file and do as follows:
NOTE: Unfortunately, this script won't work with the latest revision of TF101 (3G version, B80 and some B70)
NOTE2: As someone pointed out (thank you Pieter) you need to be root on your linux box in order to make it work.
Code:
tar -xvf universal.tar
cd universal
./universal.sh
In Ubuntu the last command would be:
Code:
sudo ./universal.sh
Follow the instructions and you're done.
If you have a stock US/DE/TW/JP/TB firmware you can do the same.
If you are running an older version of Honeycomb the process is the same.
When ASUS will pull out another upgrade... same commands as above.
So this probably is the closest thing to one-click-root for the Transformer.
This won't install custom rom/CWM/strange other things (V2 version added the support for CWM); it's only root.
I've tested this morning after the 3.2 upgrade and it worked like a charm.
However this is in testing stage so, as always, if you brick/ruin/burn/crash something don't blame on me.
This package includes the Bootunpack tool, courtesy of Rayman84
LIVE CD INSTRUCTIONS
It's based on slitaz (http://www.slitaz.org/).
Burn the image into a cd or if you want it on a thumb usb drive follow this (http://doc.slitaz.org/en:guides:liveusb).
Put the cd/usb in your pc and reboot.
Follow the indication on screen (for setting locale and keymap).
When the desktop shows up, double click on "Universal Root for ASUS TF101".
Again follow the indication and you'll be ok.
For a guide on how to boot from cd/usb try this: http://www.passwordunlocker.com/knowledge/change-bios-settings.html
or search with google.
The option to install a stock boot/recovery (added on V3) is working even if not fully tested.
The program has correctly rebuilt a stock recovery on my WW version.
From version V4 root checker correctly says that the rom is not rooted after you do an unroot.
If you like the work i did take a look at that funny button under my name with the "donate to me" caption
Seriously, I appreciate even only a "Thanks".
FAQ
[Q] I'm running on Windows, how can I burn the live-cd?
[A] Try with cdburnerxp (it's the easiest way).
You can download one installer frome here:
http://cdburnerxp.se/en/download
or the portable package if you don't want to install other software:
http://download.cdburnerxp.se/portable/CDBurnerXP-4.3.8.2568.zip
Start the program (for the portable version the file is cdbxpp.exe) and click on "Burn iso image". Then select the .iso file you have downloaded and click "burn disk". All Done.
[Q] How can I reboot in APX/recovery mode?
[A] Do as follows:
VOL UP + POWER BUTTON for ~5sec = boot in APX mode. The screen will stay black as if it is turned off. This mode is used only when you use nvflash to flash boot/recovery/data partition (this is the first step in my script).
VOL DOWN + POWER BUTTON ~5sec = will appear a screen where it says to press vol down again to wipe all data (obviously you don't want to do it now), or press up to enter RCK (recovery mode). If you installed CWM you will see the main menu navigable with vol up / vol down / power button.
If you have the stock recovery you will see a green android with a esclamation mark on a yellow triangle.
[Q] Help! I can't reboot in recovery mode!
[A] I think the main problem here is that it is a bit tricky to get into CWM recovery, once you see the small text come up don't try to read anything, just hit volume up.
Hold volume down plus power until the text in upper left shows,if you let go too early it just boots up and you never see the text. If you wait too long you don't get the option to boot into recovery. Hope that helps..
Thx to ckuke4 for this answer http://forum.xda-developers.com/showpost.php?p=16306342&postcount=60
[Q] The live-cd gave me this error: "connection failed NvError 0x8" what is it?
[A] This means that either you are not in APX mode (read above), or that you have one of the latest revision of the tf101 (B7O) which have an unknown (for now) sbk.
For what i know, there's no knew method for rooting your device.
Maybe someone will find a way, but for now you have to be patient.
[Q] I'm running your scripts from my linux box, but it keep me saying "Permission Denied". Why?
[A] You need the root privileges on your local machine.
If you are running Ubuntu:
Code:
sudo ./universal.sh
[I](it will asks for your password)[/I]
If you are running another linux distro:
Code:
su
[I](it will asks for your password)[/I]
./universal.sh
[Q] I have rooted my tablet with this method, but I can't find the superuser app and Titanium Backup says that I am not rooted.
[A] The root script will asks you to reboot your tablet, make sure that usb debugging is turned on and then press any key.
You have to wait until you see a little bee on the bottom right of your tablet's screen, near the clock. Then press any key.
[Q] I've installed CWM but every time i try to do a backup, it says it can't find sdcard. But my microsd card work fine with root explorer!
[A] Don't get me wrong but, are you sure?
In root explorer you see a sdcard folder but it's not your microsd, it's the internal memory (it's weird, i know). In root explorer the microsd card is mounted under the "/removable/microsd" folder. You should also see a little sd card icon in the bottom right, near the clock.
Also you need to make sure the card is formatted correctly. Try reformat it with this: https://www.sdcard.org/consumers/formatter_3/
Thanks to skeeterpro for the link (http://forum.xda-developers.com/showpost.php?p=16385872&postcount=6)
[Q] The live cd stops at the command prompt, I can't see the desktop.
[A]The live cd doesn't include every driver for every video card, mouse, keyboard, etc.. (keep in mind that the original slitaz livecd is only 30MB).
You can do all the process in the text console, it's not much more difficult.
If it asks for a login insert "tux" (without quotes).
At the command line enter the following:
Code:
cd
cd universal
./universal.sh
Then the magic will start. The unroot script is called ./unroot.sh
CHANGELOG:
V4:
- Corrected some text
- Added a link on the Desktop to this thread
- Added stock ramdisk for all SKU (though JP, CN and DE are not the latest versions) (thanks to kovla for the latest TB recovery)
- Added a script on the Desktop to increase the font size on the fly for those who are using a very high dpi monitor/tv.
- Changed compression algoritm. Now the iso is ~10MB smaller.
- Maybe I have found the way to make everyone read the faq...
V3:
- [BETA] added a second script to come back to stock.
V2:
- added the option to install CWM (thanks Roach!)
- more error check
V1:
First version
=====> DOWNLOAD LIVE-CD V4 - (Mirror)<=====
DOWNLOAD LIVE-CD V3 (previous version)
DOWNLOAD LIVE-CD V2
As always, keep your eyes open and
Have Fun!

Hey, how about an equivalent windows script for those who prefer msft's os. Ok?

awesome -one root to rule them all!

ondoy1943 said:
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
Click to expand...
Click to collapse
In linux there's no need for drivers to work with tf101.
Windows seems to be problematic with driver (for someone seems to be way too difficult install the right ones).
As i stated above, adding this to a live linux cd will be the final one-click-root (put a live cd/usb-memory on your computer, reboot, follow the easy instructions and you're rooted).
Sincerely I don't know how to modify a livecd to add these scripts and programs.
If anyone wants to try, he is welcome.
Anyway I don't plan to do a windows port of this.

Disappointed! No windows support!

Will probably be trying this method from my PCLOS partition, if I can hold off the OTA update which has just begun pestering me.
Got to find out whether the modded adhoc wpa_supplicant works with 3.2 first, thanks for the effort HF

Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.

belrik said:
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
Click to expand...
Click to collapse
I was thinking on it, but perhaps it's better no.
Installing cwm means no more ota, since the update relies on the stock recovery.
This script was meant to leave all as stock as possible.

For all the windows folks:
I have added to the first post a live-cd with all the necessary tools.
Just run it and you'll be fine. (anyway, you are always in time to switch to linux)

Hallo and thanks!!!
what about mac's Users?

Can you explain a bit about what it does? So we can all learn.
Thank you,

Hi !
Will it work under wmware or virtual pc ?

Sorry if this is a dumb questions, but would this work in Terminal in OS X?

RayYung said:
Can you explain a bit about what it does? So we can all learn.
Thank you,
Click to expand...
Click to collapse
So you wanna learn? Good!
First i learned how to root the stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1125714 .
Essentially the steps are:
1 - download a modified boot image into the tablet
2 - install the su and superuser packages.
My scripts do these 2 steps. I wrote a small howto that explains how to modify a boot image (http://forum.xda-developers.com/showthread.php?t=1193737)
Caramel said:
Hi !
Will it work under wmware or virtual pc ?
Click to expand...
Click to collapse
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
I really would like to have an answer to these questions...
The Mac should have a layer of compatibility with linux (can't tell you more), but i really don't know the mac world.
*Maybe* the live cd will work under virtual machine; there should be some options to enable the usb feature. In Virtual Box there's an option to enable the usb controller and an option to filter what device will be accessible to the guest os; don't know vmware and virtual pc.
I don't know if an Intel based Macintosh is able to boot from a x86 live-cd, you could try.
I'm sorry i can't help you much more.

scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
Oops- no- there is no Nvflash for Mac. Sorry.

Created a live usb, booted via windows, and voila i am looking at a linux desktop, which i have not seen for a long time. Started going to its paces to root my tf, but did not push thru to the end, in as much as my tf is already rooted beforehand. But i can sense that barring any unforeseen miscues by the |op|, this almost one-click rooting procedure should produce its desired result. Highly recommended; good job |op|.
Looks like this calls for an "unrooting" routine to complement the rooting process. How about it?

Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?

brando56894 said:
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
Click to expand...
Click to collapse
I have already tried this, but seems it doesn't work.
if i write "adb reboot recovery" or "adb reboot bootloader" my tablet reboot in normal mode.
It's more reliable do it manually.

how can install ClockworkMod recovery
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?

zulu99 said:
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
Click to expand...
Click to collapse
For now if you are running on windows, you can use one of these methods:
http://forum.xda-developers.com/showthread.php?t=1125714
http://forum.xda-developers.com/showthread.php?t=1185104
you are already rooted, so just need the cwm.
Since i had many requests on adding cwm, i am going to update the scripts and live-cd for adding this feature.
I'll keep you updated.

[Guide][WIP] Dopo TD-1010 hacking

Since there is a terrible lack of information on this RockChip tablet, I've decided to compile what is known about this tablet into one thread. I'll modify this as more info becomes available to me.
Double Power TD-1010 10.1" Tablet
Tablet architecture: this tablet is a Rockchip RK3066 based tablet.
Rooting the TD-1010: The method that I have tried and successfully rooted my tablet involves using the drivers from PDAnet and AndroidRoot. A tutorial exists on YouTube for this. Having that out of the way, we can begin on more technical information.
Backing up the ROM: As the tablet is a rockchip device, you can use the RkFlashTool for linux here in order to copy/write to the tablet. I've modified the source of RkFlashTool in order to detect the tablet, and attached it below.
1.compile it using the included instructions, and throw it in your /usr/bin folder.
2.To put the tablet into flash mode, hold the VOL+ button while plugging in the usb cable to the tablet.
3.Wait 2-3 seconds before letting go of the Vol+ button after plugging it in. your screen should be black at this point.
4.You are now in flash mode, and can be detected by the rkflashtool.
5.Download the Linux tools.7z, and run MAKE on the tools dir.
6.Copy the resulting mkkrnlimg executable to your /usr/bin directory.
7.make sure the simpledump has permissions to execute, and run
Code:
./simpledump.sh
8.Make sure your tablet is in flash mode, then hit enter to begin.
Recovery/Unbricking:
Dillmiester at TabletRepublic has made a stock backup of the TD-1010 after it returned from RMA, and can be located Here. Note, remove the external SD card, and you may have to retry the flashing of system.img multiple times if it fails.NOTE 2: THIS UPGRADES YOUR TABLET TO JELLYBEAN, AND GIVES YOU 1.8 GB of APP SPACE.
Flashing: ROMS, such as the stock one linked above, can be flashed using Windows 7 and the RKAndroidTool I have attached to this post. This includes the drivers for using the program as well. The tablet will need to be in Flash mode in order for the program to write to it.
Booting into recovery:Yes, this tablet does have a recovery. to get to it:
hold power and vol+ at the same time
screen should boot to android character with a red ! sign over his body
press vol+ and Back(the normal touchscreen location for it)
If done at the same time, you should be at the recovery menu.

great job thank you. i don't have a Linux machine so i guess all i can do is root?

you can root and flash existing ROMS on windows, but you cannot dump your own tablet on windows.

DOPO td-1010 romdump procedure
ase1590 said:
you can root and flash existing ROMS on windows, but you cannot dump your own tablet on windows.
Click to expand...
Click to collapse
Just an FYI for those interested. I've found a working romdump procedure for this tab, that's independent of any OS. Unfortunately, I can't post the link, but would be more than happy to supply it some other way. I can confirm it works and is safe. It's on vondroid.com for those interested. The rest of the link is /threads/updated-27-08-2012-how-to-dump-current-rom.322/ hope it helps those using windows.
Just for clarification purposes. 'The extracted file is what you need to copy to your SD, not the zip. And when you change the permissions all you need to do is add execute to the user. Oh, and in term emulator after su you need to enter /data/local/romdump and NOT just /data/romdump because it won't work.

ase1590 said:
Since there is a terrible lack of information on this RockChip tablet, I've decided to compile what is known about this tablet into one thread. I'll modify this as more info becomes available to me.
Double Power TD-1010 10.1" Tablet
Tablet architecture: this tablet is a Rockchip RK3066 based tablet.
Rooting the TD-1010: The method that I have tried and successfully rooted my tablet involves using the drivers from PDAnet and AndroidRoot. A tutorial exists on YouTube for this. Having that out of the way, we can begin on more technical information.
Backing up the ROM: As the tablet is a rockchip device, you can use the RkFlashTool for linux here in order to copy/write to the tablet. I've modified the source of RkFlashTool in order to detect the tablet, and attached it below.
1.compile it using the included instructions, and throw it in your /usr/bin folder.
2.To put the tablet into flash mode, hold the VOL+ button while plugging in the usb cable to the tablet.
3.Wait 2-3 seconds before letting go of the Vol+ button after plugging it in. your screen should be black at this point.
4.You are now in flash mode, and can be detected by the rkflashtool.
5.Download the Linux tools.7z, and run MAKE on the tools dir.
6.Copy the resulting mkkrnlimg executable to your /usr/bin directory.
7.make sure the simpledump has permissions to execute, and run
Code:
./simpledump.sh
8.Make sure your tablet is in flash mode, then hit enter to begin.
Recovery/Unbricking:
Dillmiester at TabletRepublic has made a stock backup of the TD-1010 after it returned from RMA, and can be located Here. Note, remove the external SD card, and you may have to retry the flashing of system.img multiple times if it fails.NOTE 2: THIS UPGRADES YOUR TABLET TO JELLYBEAN, AND GIVES YOU 1.8 GB of APP SPACE.
Flashing: ROMS, such as the stock one linked above, can be flashed using Windows 7 and the RKAndroidTool I have attached to this post. This includes the drivers for using the program as well. The tablet will need to be in Flash mode in order for the program to write to it.
Booting into recovery:Yes, this tablet does have a recovery. to get to it:
hold power and vol+ at the same time
screen should boot to android character with a red ! sign over his body
press vol+ and Back(the normal touchscreen location for it)
If done at the same time, you should be at the recovery menu.
Click to expand...
Click to collapse
Thank you sooooo much for the work you have compiled into one location. Is there any way that you could provide a detailed description for Windows PC's for loading the ROM that increases the App storage file size to 2GB and also how to load CWM as the permanent recovery? I just received my tablet back from DOPO and it is loaded with Android 4.1.1 firmware and 1GB of app storage space. The original root process (android root unlocker) does not work anymore. I ended up using (root rk29) to obtain root access (just in case anyone needs the info). Thank you in advance for your support with this tablet, it is greatly appreciated.

How do I install xubuntu?

Do i just make like a folder right on the sd card called linux, or boot, or whatever it was? Would that work with the img and an/or extracted rootfs?
I may be thinking about it too hard and it could very well be super obvious but idek
Also is the latest kernel the lolli dual boot or the cool selector kernel?

I figured it out relatively quickly after reading through 185 pages of linux installs

Relatively quickly? Well, what do I do? Can you explain how have you made it work? PLEASE. I really want this.

danek731 said:
Relatively quickly? Well, what do I do? Can you explain how have you made it work? PLEASE. I really want this.
Click to expand...
Click to collapse
Alright,
You need adb working first of all, you need that to install linux. Somewhere floating around theres asus drivers that will work with it.
Next, you need to have a KitKat 4.4.4 rom. Kexec kernel works right out of the box with a 4.4.4 rom, however you can modify a lollipop kernel to get that working.
Here is the kernel
After you flash all of that, you should have the Kexec menu come up with System Menu and Android as an option. You can use the volume buttons to highlight a choice and press power to boot your selection.
The linux build i used was from Geometry, that can be found in his post here http://forum.xda-developers.com/showpost.php?p=57529347&postcount=15
now once that is done downloading, transfer it to your internal memory, and once that is done transfering you now need ADB
Make sure USB Debugging is enabled and you allow adb to run on the device Something with RSA keys will pop up on the tablet, just press ok (at least i had to do that)
You may need to CD to where ever you installed ADB. I have mine kinda universal so i can just type adb without cd'ing into where it is. Now press enter after each thing you type
type adb devices to make sure your computer can see the tablet.
Next type adb shell then su
that will give you root access in order to extract and move linux to its home.
Now type mkdir /data/media/linux if it is there, itll say its there.
now type tar -xzvf /storage/sdcard0/tf300t-xubuntu-rootfs.tar.gz -C /data/media/linux
That'll take a good 30 minutes to extract and move everything. Once that is done you should be able to reboot and select Xubuntu 14.04 in the Kexec boot menu. Itll reboot into linux and should get you into the login screen after a minute or so of booting.
Now I have everything pretty much working like how I want it to, except for suspend/sleep. Ill carefully move onto maybe full ubuntu or something to see if suspend works or not, in ubuntu or any other distro I might try
Something I need to do is probably install it on the SD card I have, and format it so that the rootfs lives on a ext4 partition and have a swap partition up and running too

Thank you.

Android X-86 Guide for multi-boot with Windows 10 (dont do what i did)

So it has been a hectic few days for me as I had alas managed to wipe my system reserved partition thinking that installing android x86 as multi-boot would actually boot windows for me. Wrong!!! My first poor encounter was the fact that when I had installed windows it had created the system reserved partition as ntfs... I had not realized this when attempting to install android x-86 as multi-boot. I will tell you the result, when booting it would appear to go to grub, however instead it just booted the first menu on the list without hesitation and gave no menu at all. To remedy this I had to use the windows 10 usb i had created for my initial install. I am still not sure how i managed to get it to boot the first time I think it may have just been dumb luck. When windows booted up i went to Disk Management (right click the windows menu and select from the drop down) where I then proceeded to delete the system reserved partition and reformat it fat32. At this point I was satisfied that android would point the out the windows boot, boy was I wrong. After installing Android x86 (_64 8.1 r3) I finally achieved the grub menu boot correctly. I also noted that when installing android x86 the only way it gave me option to add windows to grub was if i had installed without formatting first. (this can be done a few ways including just reinstalling much the same way you would dirty flash a rom on a phone) or you could use a tool to format the partition such as gparted or a linux live cd/usb. I suggest ext4. Oh wait my nightmare hadn't finished yet... Android x86 install had no problems at all (select partition to install(ext4)... do not format... install grub... yes to windows... yes read write... and then reboot) on reboot windows was in the grub menu and I selected it... oops there is no operating system!!! Well that is unsettling... ( I managed to get back into windows using the install media) and not so sure how. At this point i notice that my system reserved partition was now sda 3) So my next objective was to create a boot record for windows which could have been done easily from windows had I considered using bcdedit tool for windows. But since i knew that the partition was sda 3 I figured I could just point the grub menu to the correct drive... again wrong (there was still no boot mbr on that partition *sigh) Well I found that when i went into command line from the windows repair tool it would say I do not have permission to fixboot... wow nice job microsoft... after doing a bit more research I learned that the newer builds give this error when attempting to fix boot. I found a video on youtube which helped me alot but took quite a while to download the older working repair tool(installation media) but his video was fairly well put together. link here (https://www.youtube.com/watch?v=lRCyb7FzWFY). I followed his guide and this time with the repair tool that he shared in the description of his video, I was able to perform the fixboot (bootrec /fixboot) however one of his commands required the copying of bcd to the system reserved partition. The copy failed, however at this time running all the other bootrec commands seemed to go fine. So I exited command and went to the automatic startup repair, which to my surprise worked perfectly... (after a whopping 30 some hours of pulling my hair out of my head over this mess) And windows began to boot. At this point I gave my thanks to the poster of the video and shared my experience with his video in the comments below.) Now When windows booted up I downloaded the bcdedit tool. Personally I used the multi boot tool from this site (https://www.boyans.net/dual-boot-repair-windows-10.html) and selected repair mbr and boot record. This fixed my boot issue windows would boot normal at reset. However now my android was gone but thats okay.
At this point I just reinstalled the android x86 again over the same ext4 partition without formatting and added the windows to grub. This was perfect however when selecting windows did not boot. To fix this I had to edit the grub menu.lst and change the drive from hd(0,0) to hd(0,2) to point to the fat32 partition which had been somehow displaced to sda3. In order to do this I ran android in debug... when debug is running just hit enter and it give you a prompt... from prompt type without quotes "cd /mbr/grub" when the next prompt comes up you should be in the grub directory where the menu.lst is. Now type without quotes "vi menu.lst" this will take you into a text editor (note you can also change your monitors and resolution permanently in grub menu this way) using the arrow keys navigate to the line you want to edit, in my case the last entry which was windows entry when you get to where you need to edit hit the "i" key this will allow you to now enter and edit the text. After making changes hit "esc" to save changes type ":w!" then hit enter. To exit type ":q!" this will take you back to prompt. Now reboot your system and finally the results I had originally hoped for a multi-boot system with windows 10 and android. Now if you are attempting to do this and are looking for a guide to install I will make this just a little longer to make sure you dontt make the same mistakes I made.
1a) before you attempt to install a dual boot with grub... make sure your system reserved partition is fat32 if it is not you need to change it to fat32. as grub will not boot on ntfs partitions.
1b)you will need to have a blank partition, if you have spare room on the drive you can shrink your volume and create a new one. There are plenty of tools out there to format ext4 even from windows. Make sure you format it before installing. (if you are lazy like me you can format ext 4 from the installation, but there is a chance that you would need to reinstall again and choose not format to get the windows entry in grub)
1c)once your partitions looks the way you need and you have a working fat32 system reserved partition you are ready to move on. ( If you have to change a ntfs partition to fat32 I highly suggest you dont install anything until you have repaired the boot menu and tested it first to make sure it works)
2)create your install media... I prefer to use rufus as it is quick and easy, and I prefer the official android x86 as the 8.1 r3 is stable and works great, you can use whatever image you want though, lord knows i test newer versions as they come out. when you have rufus and the android x86 iso of your choice load rufus select your usb drive and select the iso with the browse button. then just hit start allow it to format and when it is done you can boot into your usb
3)To boot into your usb you may actually need to edit your bios and enable virtualization and make sure safeboot is not enabled, also you need a uefi system for x64 distros so if you have an older legacy bios you will need the x86 version instead or the system wont boot
4)When you finally get it to boot you will find the menu to use it as a live cd or install, select the install.
5a) You will now be asked where to install to. Pick the ext 4 partition you created for it.
5b) Now it will ask you to format choose do not format (again if you hadn't formatted the partition ext4 you may do it now, but you may have to reinstall and not format the next time to add windows to the grub menu)
6) You will now be asked to install grub answer yes, if you do not answer yes you wont be able to get back into your android partition again until you do.
7) Now it will tell you that it found a windows partition and asks you if you want to add an entry, select yes... if you do not you will have to make your own grub entry to get back into windows later or completely delete grub from the partition later.
8) Finally it will ask you if you want to make the system read write... select yes, if you select no i can not guarantee you will be able to install anything inside of the system.
10) The end... Installation finishes but do not click launch... instead click reboot. The reason for this is that I have noticed if you launch at the end of installation the grub somehow manages to disappear and you end up having to completely start over.
Enjoy your android x86 / windows multi-boot system.

make sure your system reserved partition is fat32
Click to expand...
Click to collapse
There is no system reserved partition on my laptop since I have a UEFI laptop.
Should I proceed ?