Database Info

PSFreedom for Magic

Quoted from Breach
PSFreedom on G1. Simple step by step.
Before you proceed. This is tested and working on CM 6.0 Final, as it has been compiled for that kernel from that source. It may work on other versions, but is not supported.
Get PSFreedom_G1_bdvd_k4roshi_signed.zip (available at http://psfreedom.com/wiki)
Place PSFreedom_G1_bdvd_k4roshi_signed.zip on your SD card.
Shut off the G1 and Start the G1 into Recovery mode (holding Home & Power)
Flash PSFreedom_G1_bdvd_k4roshi_signed.zip using "Flash zip from SDCard"
Reboot once completed.
Once the phone has booted, open a terminal emulator..
Type..
su
cd /system/lib/modules
insmod psfreedom.ko
Connect your G1 to the PS3 via USB.
Turn off the power switch in the back of your PS3 and turn it back on.
Start your PS3 using the power button quickly followed by pressing the eject button.
Note: You will not see anything displayed on your phone. To verify that it worked, go to the games menu and check for "Install Package Files".
Download a Backup Manager of choice.
Put the manager.pkg (the Backup Manager install file) on any USB mass storage device and plug it into your USB port on the PS3.
Install the Backup Manager on the PS3 and you're good to go.
If your PS3 turns on, but you get no video, you may need to update to 3.41 (Known versions that draw blank screen 2.76 & 3.15, probably all versions older then 3.41 which PSFreedom was tested on)
I hope you find this useful.

Waiting for a 32B/G1 CM6 Kernel one too

It's working and being uploaded to the wiki right now...

0Vw3 said:
It's working and being uploaded to the wiki right now...
Click to expand...
Click to collapse
Which wiki?
Sounds great though

http://psfreedom.com/wiki

DashKiller said:
http://psfreedom.com/wiki
Click to expand...
Click to collapse
Thanks
I guess http://bit.ly/9YyrJ4 will be up soon, huh?

New link is up on the wiki. Downloading now

Can someone post some instructions?

Can someone tell me how to compile it? The link on the wiki now works, I just don't know how to compile it...

Install the zip file from the wiki through recovery
Once the phone has booted, open a terminal emulator and then type su.
Go to your memory card (usually /sdcard) and run insmod psfreedom.ko
Connect your Nexus One to the PS3 and power the PS3 off completely, following the guide for PSJB - power on, push power and then quickly push eject. You will not see anything displayed on your phone.
To verify that it worked, go to the games menu and check for "Install Package Files".

The file you are trying to access is temporarily unavailable

hanzohittori said:
run insmod psfreedom.ko
Click to expand...
Click to collapse
Do we get this file after we have flashed the .zip? And have you tried this yourself on a G1(32b)?

Just installed kernel. insmod psfreedom.ko returns "insmod: init_module 'psfreedom.ko' failed (Exec format error)

cd to /system/lib/modules and run it
Works flawlessly - thx

0Vw3 said:
It's working and being uploaded to the wiki right now...
Click to expand...
Click to collapse
the link for the 32a is broken, can any1 fix it?

So how can I end the module now to use ADB again?

The wiki link for the file has gone. Can some one reupload please

broken wifi
psfreedom kernel updat seems to broke my wifi - can anyone confirm it?

been taken down

So I need to do a nandroid restore in order to disable the module?
My wifi is broken aswell.

[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.

Noob Tutorial: Ubuntu on Transformer

I've been looking around for some good tutorials, but in my opinion, almost everything was pretty difficult to understand for me.
But finally I found out how things are working (except of wifi, can You help me?
http://forum.xda-developers.com/showthread.php?t=1295718)
So I want to share my knowledge with You all and try to make it easy to understand.
1. The ony way in the moment to install Ubuntu on Your Transformer is over a Ubuntu or other Linux PC. (I easily installed Ubuntu virtually in VMware Workstation)
2. Get the required files on Your Linux machine:
http://forum.xda-developers.com/showthread.php?t=1191141
On this link, in the second post is written flash kit for linux:
klick on "here" to download the flash kit.
3. Extract the flash kit into a folder (e.g. Desktop)
4. Now download the Ubuntu root files. They are located here:
http://rootzwiki.com/showthread.php?1072-ubuntu-on-the-transformer
You have to scroll a bit down then You see
"ubuntu-rootfs:
is available here md5sum(95eda389e64461533c51fd1e4e237a30)"
Again, click on "here" to download the rootfiles. (It'll take a while, since the file is 950mb)
4. Once this is done, extract the rootfiles into linux-flash-kit/images. (This folder is the one You have extracted in 3.
5. When You want to Dual-Boot Your device with Andoid AND Ubuntu, read on, otherwise go to point 6.
You have to download a nvflashable rom like for example "PRIME!"
http://forum.xda-developers.com/showthread.php?t=1251044
There You download the NVflash version and extract the image files in it, to linux-flash-kit/images, like You have done it with the ubuntu image file.
6. Now You have to choose.
If You want only linux: remember flash-purelinux.sh
If You want linux and Android Dual-Booting with Android as default OS:
flash-linux-android.sh
If You want linux and Android Dual-Booting with Linux as default OS:
flash-linux.sh
If You want to restore back to android: flash-android.sh
If You want to get to factory state: restore-default.sh
Now You have to install the APX drivers. How to do this, You can read in other threads. Basically download the NVflash file from this thread, in it, You'll find the drivers: http://forum.xda-developers.com/showthread.php?t=1123429
So connect Your tablet to Your PC, turn it off, and turn it on while holding down the Power Button and the Volume+ button.
What You'll see is nothing. Now Your device is in APX mode.
In Your Linux Computer, open up the console and go to the linux-flash-kit directory (In my case it is on the Desktop)
so I do:
cd Desktop\linux-flash-kit
So now You are in Your linux-flash-kit directory. From here You have to type:
sudo sh flash-linux-android.sh
OR You type this in what You have remembered in Point 6.
e.g.
sudo sh flash-purelinux.sh
or
sudo sh flash-linux.sh
This will take a while because the files are transfered to Your device.
7.
When it's done, Your device will start.
Turn it off, and start into Your Ubuntu.
When Ubuntu is Your main system, You start it up normally by pressing the power button.
When Android is Your main system and You are Dual-Booting it, hold down the power button and the Volume down key until the device says that Your have to press the Volume-up key. Do this and You will see a Linux code with two penguins on the top running down Your screen. That's just good like it is.
Finally You should see the Ubuntu Setup with the language selection.
Now You can go on, and now You can set up Your Ubuntu PC!
FYI:
When You have not got a keyboard-dock, Connect Your tablet with Your pc and enter the adb shell
When You don't know how to enter it:
open up Your console, get into the directory of the android-sdk and into the platform-tools.
Then You type:
adb shell
Now You should be in the ADB shell
Now You can type:
DISPLAY=:0 onboard
Then a virtual keyboard should appear on Your tablet and You're ready to go!

Just to create a vocal point, This requires root doesn't it?

Also, is the wifi and stuff working? What's not working?

Mr.Ox said:
1. The ony way in the moment to install Ubuntu on Your Transformer is over a Ubuntu or other Linux PC. (I easily installed Ubuntu virtually in VMware Workstation)
Click to expand...
Click to collapse
Nice guide. There is one correction: it took me a while to find this but there is a windows-flash kit that I've used to install ubuntu on the transformer from Windows 7.

roflcopterofl said:
Just to create a vocal point, This requires root doesn't it?
Click to expand...
Click to collapse
I don't think so, because everything is flashed via nvflash. This way, You can flash a rom without having it rooted, too.
But I'm not quite sure..
moseskim said:
Nice guide. There is one correction: it took me a while to find this but there is a windows-flash kit that I've used to install ubuntu on the transformer from Windows 7.
Click to expand...
Click to collapse
Oh, that's a nice one, I haven't seen this yet! Thank You!
asdfuogh said:
Also, is the wifi and stuff working? What's not working?
Click to expand...
Click to collapse
What's working and not You can read in the Q&A Thread, there is written everything, I just tried to explain it a littlebit easier.
The thread is here:
http://forum.xda-developers.com/showthread.php?t=1191141
There You can see what's working, what not, and how to connect to a WiFi network (For me it doesn't work...)

Thank for this, I am itching to try this... Is there any "easy" way to get back to stock honeycomb after i try this ?
(sorry for this stupid question, I do no know much about these things)

In my opinion it's very easy.
On the one hand, run the command
Flash-android.sh
Or
Restore-default.sh
Or your use nvflash to wipe the device and get a normal rom on it.
Sent from my HTC Desire using xda premium

Thanks, I will try this later today then

tombolek said:
Thanks, I will try this later today then
Click to expand...
Click to collapse
Yeah, when You get Your wifi working, please tell me how because mine does not work
Sent from my HTC Desire using xda premium

Hello yesterday i've try to put linux and android on transformer, all work's great but after 5 minut nvidia apx was disconnected because battery load 0%; i work on vmware machine; after I've charged my dock e tablet and run again the script but that's is the result
sudo sh '/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh'
/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh: 2: /ubuntu/abootimg-i386: not found
/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh: 3: /nvflash: not found
rm: impossibile rimuovere "linux.img": File o directory non esistente
why?
I've already tryed to restore with nvflash all partition and download all in new virtual hdd but not work.

Kali Linux on Android Note 3 Guide

This may have been posted some where in the past but I have been searching for some time and found nothing but others looking for this information. So I though I would document what I did to get everything up and running on my note 3 and share it here.
Requirements
Rooted Note 3
Recommended
Bluetooth keyboard and mouse
From a PC
1. Download kali from the LOA website kalilinux.FULL.ext4.20131031 (5.8 GB Uncompressed) (2.0GB Download)
2. Once the download is complete extract the contents of the folder so you have a folder named “kali” then an .img and .md5 file in it then copy that to the Note 3 device storage root. I strongly recommend using USB 3.0.
On the Note 3
1. First Download Linux on Android It might be called Complete Linux Installer now
2. Then Download androidVNC and Terminal Emulator
3. Download the modified bootscript.sh from attchments and extract
4. Copy to /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
5. Start Linux on Android
6. Swipe from the left of the screen to the right and open the menu
7. Select “Launch”
8. Using the drop down box select “Kali”
9. Press the “Settings” button on the top right
10. Select “Edit”
11. On the line that says “Image” click the “…” button
12. Select the img file you copied to the storage in the kali folder
13. Click the “Save Changes” button
14. Then you are ready to click the “Start Linux” button
15. There will be a question if you want to check the img with the MD5 I would go ahead and type “y” and do this step to verify your download was not messed up.
16. Then it will ask you to create a new password. Type it in. And again. Make it 6 char alpha numeric.
17. If all is good it will ask if you would like to start vnc and ssh servers. Select yes to both.
18. Next it will ask you if you would like to save as default settings. I would select yes.
19. After things finish loading and you have a prompt. We will have to configure ssh
20. Type “ssh-keygen –R localhost”
21. Then you will be able to connect to the linux shell via ssh
22. Type "ssh localhost"
23. It will ask you if you want to add localhost to the list of allowed hosts
24. Type "yes" then press enter
25. Type in your password
26. Once connected to the emulator you will need to setup the VNC password
27. Type "vncpasswd" then press enter
28. Type your password in. And again. I would use the same 6 char password from before
29. Then you are ready to connect to the desktop
30. Open androidVNC from them the main menu leaving the terminal running in the background
31. Create a new connection from the dropbox
32. Name it kalilinux
33. Fill in the password you created
34. Use localhost for the address and the default port
35. Select 24-bit color (4 bpp) for the color format
36. Click connect...

Great guide. My device isn't rooted (yet) but this makes me really start considering a root in near future. THIS^ is a the best reason why we need knox free devices.
Damn you Sammy with your Knox mumbo jumbo! I should start looking for an older FW/rootable SGN3....

This will not trigger the Knox bit it is running in an emulator on top of android. there are a couple of ways to root without tripping the Knox bit. And this does not need a custom rom or kernel.

Does it really work for you? I wasted almost a full day trying to get linux to run on my note 3 yesterday, I even began suspecting kitkat prohibits running linux...
On a side note, is there some smaller distro? 5+ gigs is an awful lot, I only need GCC and a few static libraries on my image...

good guide! Thanks!

Does it support packet injection out the box, or are you awaiting the modded driver as well?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

melaniel said:
Does it support packet injection out the box, or are you awaiting the modded driver as well?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not by default i could not start monitor mode on the adapter but you can use an external wifi adapter as long as you provide external power via usb splitter
this guide should work with other distors just download one to your likeing from the linux on android site

bruce303lee said:
not by default i could not start monitor mode on the adapter but you can use an external wifi adapter as long as you provide external power via usb splitter
this guide should work with other distors just download one to your likeing from the linux on android site
Click to expand...
Click to collapse
ill wait out the driver then. bcmon is working on the nexus 5, same driver so should theoretically work on note 3

melaniel said:
ill wait out the driver then. bcmon is working on the nexus 5, same driver so should theoretically work on note 3
Click to expand...
Click to collapse
+1
I don't think there will be a driver, but let's hope and pray... Maybe a developer take some time to port the driver for the bcm 4339 chipset to get monitor mode working .
For informations about development status for the driver you can follow my link
http://forum.xda-developers.com/showthread.php?t=2602710
Greetings Tyler

TylerDurben said:
+1
I don't think there will be a driver, but let's hope and pray... Maybe a developer take some time to port the driver for the bcm 4339 chipset to get monitor mode working .
For informations about development status for the driver you can follow my link
http://forum.xda-developers.com/showthread.php?t=2602710
Greetings Tyler
Click to expand...
Click to collapse
Well its the same driver as the Nexus 5, so here's hoping!

melaniel said:
Well its the same driver as the Nexus 5, so here's hoping!
Click to expand...
Click to collapse
This project is much more interesting!!
http://w11.zetaboards.com/Pwnie_Express/forum/3714106/
I am using it with my nexus 7 (2012) witch is bcmon supported
Sent from my SM-N9005 using XDA Premium 4 mobile app

Error: Unable to create loop device!
Hello,
I installed the 4.4.2 version on Note 3 (N9005) ... when I boot Kali I receive the error below:
Code:
[email protected]:/ $
[email protected]:/ $ cd /storage/extSdCard/Linux/KaliFull
[email protected]:/storage/extSdCard/Linux/KaliFull $ su
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Linux/KaliFull/kalilinux.FULL.ext4.v2.img
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Linux/KaliFull/kalilinux.FULL.ext4.v2.img
Full/kalilinux.FULL.ext4.v2.img <
Checking loop device... MISSING
Creating loop device... /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[130]: /data/data/com.zpwebsites.linuxonandroid/files/busybox: can't execute: Permission denied
FAILED
Error: Unable to create loop device!
1|[email protected]:/storage/extSdCard/Linux/KaliFull #
does anyone know how to fix it?
Thanks,

Error: Unable to create loop device!
yea, me too, galaxy note3
Error: Unable to create loop device!
help,

Loop device error
My device also has that loop error.
I think that this has something to do with the kernel...
Here is my kernel version:
http://i.imgur.com/C6yF4DB.png
Can anyone confirm that this is the kernel issue?
P.S. here are the instructions for setting up Kali on Galaxy S4 with Linux Deploy app (I'll try install it using these methods...):
http://forum.xda-developers.com/showthread.php?t=2400638
EDIT:
I had no luck installing it with Linux Deploy. It just fails... It says it cannot find the directory that actually exist... xD
P.S. i think this is a kernel issue according to this (and other posts I found):
http://forum.xda-developers.com/showpost.php?p=50746675&postcount=5
You can find custom kernels and ROMs here:
http://forum.xda-developers.com/showthread.php?t=2439633
I heard that the LEAN kernel has "loop devices" setting enabled.
Also, you can modify your current kernel. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1818871
Is there a easier method for enabling loop devices?

access
how can I access all kali files and folders when I usee explorer root is my sd card root and I can't see a single kali file

I tried your method and still received the same errors.
I have a rooted note 3 (I think I used the chainfire method) the device is still pretty new to me.
First it won't create the loop255
I've manged to get around that by making the loop255 device myself in terminal with the play store version of bbox (for some reason there seems to be an issue with the installer calling it's own busybox)
But then it (that is the loop device) won't mount, I'm over my head with that stuff so I haven't been able to work around this.
Some guidance would be much appreciated.
On a side note I got linux running on my old LG Motion with linux deploy and it works like a dream but for some reason there are no programs on it! I've found this odd but there are (or at least I cant find them) none of the preloaded hacking programs that are the entire point of the kali project. It's possible I just didn't find them yet but it's so hard to work with a desktop OS on a 320x480 screen, that's why I'm trying to get it on my note! I'm in love with this new 1080x1900 res!
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 11:15 PM ---------- Previous post was at 10:57 PM ----------
Okay I've seen in a few places that it has to do with the stock kernel of the note 3 can anyone either confirm or deny this and if so what do I do?
Sent from my SM-N900T using XDA Free mobile app

Root Folder
I was just wondering how you were able to copy files and folders from your pc to your root folder. Do you use a program or cmd line?

Circumventing the loop device mounting problem on the Note 3
Vinniecap974 said:
I tried your method and still received the same errors.
I have a rooted note 3 (I think I used the chainfire method) the device is still pretty new to me.
First it won't create the loop255
I've manged to get around that by making the loop255 device myself in terminal with the play store version of bbox (for some reason there seems to be an issue with the installer calling it's own busybox)
But then it (that is the loop device) won't mount, I'm over my head with that stuff so I haven't been able to work around this.
Some guidance would be much appreciated.
On a side note I got linux running on my old LG Motion with linux deploy and it works like a dream but for some reason there are no programs on it! I've found this odd but there are (or at least I cant find them) none of the preloaded hacking programs that are the entire point of the kali project. It's possible I just didn't find them yet but it's so hard to work with a desktop OS on a 320x480 screen, that's why I'm trying to get it on my note! I'm in love with this new 1080x1900 res!
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 11:15 PM ---------- Previous post was at 10:57 PM ----------
Okay I've seen in a few places that it has to do with the stock kernel of the note 3 can anyone either confirm or deny this and if so what do I do?
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
I ran up against the same problem and the only way I could get around it was to flash with a "permissive" ROM.
Device: Galaxy Note 3 N9005 running stock Android 4.4.2 (KitKat).
Main steps I followed were:
(1) Rooted the phone using the excellent Towelroot method;
(2) Downloaded and deployed the various files mentioned in the Kali install guide in this thread (Kali image, bootscript, busybox, etc.);
(3) Flashed a bootloader. I used Mobile Odin (from Play Store) to install the latest CWM bootloader;
(4) Downloaded and flashed the Omega V21 ROM using the CWM bootloader. I opted for "no wipe" and it seems to have worked OK.
(5) Used the Complete Linux Installer app (Play Store) to load and run the Kali image;
(6) Fixed some permissions problems with the rooted version of the FX file explorer app (Play Store);
(7) Accessed Linux using the RealVNC app (Play Store) rather than the recommended android-vnc-viewer.
Found the former worked better for me;
Of course, the ROM flash voided my warranty, but that's not an issue for me.
Hope this helps,
Ronan

As I understand it , you need to flash a permissive kernel to make this work properly.
Im on 4.4.2 with knox 0x0 and really dont want to set it to 0x1.
I managed to get linux to install but its limited in what you can do with it.
Xposed didnt set mine to permissive , neither did the playstore app .
If anyone knows of a way to set a stock kernel to permissive on a rooted device plz pm me.

I set up a Debian chroot on my CM11 Note 3 and have been using it for a long time with great success. Here's a tip, don't bother with the loopback-mounted images, it's pointless on a phone with a datamedia partition layout (where /data and /sdcard are the same partition, which the Note 3 is). Instead, just dump the root filesystem directly into the /data directory in a folder, i.e. /data/debian (or /data/arch, /data/ubuntu, /data/kali, etc). This way you don't have to have loopback device support in your kernel, you can install as much crap as you want and not have to resize your image/partition, and you can delete crap you don't want to free up space for Android apps or user storage because all of them share the same space.
Another tip, instead of VNC server which is not accelerated and pretty crap overall, use XServer XSDL. This implements an X-server at the Android app level so it can take advantage of some acceleration (not 3D but possibly 2D) and is drawing with native Android surfaces rather than rendering into a VNC buffer and such. To use it, simply run a command such as:
Code:
# env 127.0.0.1:0 mate-session
from a chroot terminal. This particular one will open a MATE desktop session in XServer XSDL (make sure you either open the app right before or right after running the command, leave it too long and it times out). There's also a libandroid_shmem.so or something library you can use to speed up the chroot->xserver memory performance. Best thing is you can configure the touchscreen to act as a trackpad like on a laptop, then use the left and right (up and down, but landscape) volume keys as left and right click.
On CM11 you can even write a script and add it to /data/local/userinit.sh to automatically start the chroot (bind mount all the devices and set up networking) and even start services if you want. I have mine automatically fire up a samba server and an SSH server on boot so I can access files remotely as well as remote in and use my Note 3 as an ARM build box for compiling stuff.
Finally, I'm looking into booting Debian natively. I've already got it working on my Note 1 and my HP TouchPad. Booting natively means you get full access to run an X server with full graphics hardware access, and with the Freedreno driver you can get actual GL and GLES acceleration. The Adreno 330 should be able to handle this pretty well. The first step towards this goal is getting dual-booting kernels to work as the native Debian kernel will need some stuff that Android doesn't want and vice-versa. I'm working towards porting Kexecboot and the kexec-hardboot patches which will allow booting of multiple kernels without reflashing. Then you can boot Debian (or other Linux) natively or you can boot Android and use services from that Linux install in chroot and easily switch back and forth by rebooting. I already have this working on the Note 1 (HP TouchPad has kexecboot but it isn't really necessary as the main bootloader supports multiple kernels already).