yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] canedha:
thx again :)

no i have a sbkv1 tab :)

ok then i think i should go with olife instead of frankstools, to be able to use the full extend of olife.

that said, so its just follwing the instructions from the first page of this thread and the linked wiki, or do i have to consider some other things since i have already two partitions (one with ubuntu) right now? or should i for example first use olife to flash back pure android

(with option 4) stock:

- This option will partition the device in a stock way and

install the android system that is in ./images. Use this

option if you no longer want ubuntu on your device.") ?

thx in advance :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
If you want to change your Android ROM, you should be using one of the options under Update Device. If you use one of the options intended for flashing the entire device, all your data will be lost, and you'll need to reflash Ubuntu.
[Eee Pad Transformer Q&A, Help & Troubleshooting] canedha:
thx

so given the fact that i didnt use olife to get ubuntu in the first place and therefore might have different partition sizes, can i just use o life and directly flash android and ubuntu again as it is mentioned in the first post and the wiki?

or do i have to reflashteh entire device with one partition first? or will olife resize both partitions as needed?

i know that the data will be lost, but its a matter of minutes install everything again...

i just read that ics will be out for the tf101 tomorrow, will this be flashable directly as well or do we have to wait (i presume it doesnt take long) for someone to make a nvflashable version?
[Eee Pad Transformer Q&A, Help & Troubleshooting] natostanco:
what does the chromeos kernel need to work? I have tried flashing it but it doesn't even boot.

even flashing plain dual boot does not work for me, it hangs on at the start after a few log lines :B
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Yes, you can just follow the instructions given, as this will format the entire device and flash it in the desire configuration.

ICS will be available as an update to the stock image, I imagine. Presumably it will be necessary to wait until Prime ROM (or another one) incorporates the changes.

The CrOS kernel is experimental and takes a lot of tinkering to get working. I wasn't able to get it working myself, but I have heard that others have. As I understand it, you need the uboot binary (compiled from source) and a boot partition conforming to uboot's requirements. Given that hardware acceleration only works partially under it, I'd suggest leaving it to the devs unless you think you can help them out. (If so, there's a dev thread for this.)

As for regular dual boot not working, is it Android or Ubuntu that's not booting? If Ubuntu, I suggest you try compiling the kernel yourself and flashing it. (see wiki for details)
[Eee Pad Transformer Q&A, Help & Troubleshooting] 0x90:
I have dowloaded and compiled the cros-kernel and uboot from lilstevies github repo. Is that the most recent repo?

Going to try to flash it later, just have to make some backups first. :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
bluetooth config

Firstly, thank you, lilstevie, for an awesome setup here. I can't wait to really have some fun with this. But the onscreen keyboard gives me no joy, so...

I don't have the dock, so I've been trying to get my bluetooth keyboard working with ubuntu. I've used it just fine on Android through the Terminal Emulator with "# hidd --connect".

Note: I'm on IRC in #asus-transformer, everyone points me to lilstevie, haven't caught him yet.

Backgroud: Using OLiFE.sh, flashed dualboot with assumed standard kernel config. Injected bluetooth firmware option 2.

I noticed the boot printout found no driver in lib/firmware. Checked, and there was no bcm4329. Found 3 files in /etc/firmware of the android partition (bcm4329B1_002...0863, 0879, and 0942). Pulled 0942 and copied to "/lib/firmware/bcm4329.hcd".

ran "sudo unblock rfkill 0 && sudo modprobe bcm4329" followed by "/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 3000000 --patchram /lib/bcm4329.hcd /dev/ttyHS0". On argument error, I checked, and there was no ttyHS0 - only HS1 and HS2.

running the same script on either existing ttyHS* successfully loads options but hangs and never sets line discipline.

Question: I assume I have a valid and most-current bcm4329.hcd as it's straight from the working Android ROM. So I'm looking at the brcm_patchram_plus file as the main culprit or a problem with ttyHS1 and HS2 as secondary culprit. I have a webpage that shows a patch script for brcm_patchram_plus, but when I try to compile with arm-none-eabi-gcc (after porting the .h files from the OLiFE ubuntu.img include folders), I get a bunch of undefined call errors. I hear some here have bluetooth functioning. What am I missing?

Sorry for the long post. Hope someone can help.

Wade
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Yes, lilstevie's git has the latest copies of everything.

2 things:

a) 0942 isn't necessarily the file used. You can tell by enabling BT under Android and using lsof. (It points to a file in a different place, but it's a copy of one of them - you can tell which using diff or md5sum.)

b) AFAIK, no-one has BT working yet. I suspect you're closer to doing so than most of us, so if you figure it out, please report back.
[Eee Pad Transformer Q&A, Help & Troubleshooting] stibbons:
Clearing MSC flag on boot

lilsteve mentioned a while ago writing a script that would automatically clear the MSC flag at Ubuntu startup. But there's been nothing since, so maybe it's fallen off his radar. So I went ahead and wrote a quick upstart config file to do it myself.

Usual disclaimer. This works for me, but I'm not responsible if anything goes wrong for you.

To use, just extract the clear-msc.conf from the attached zip, and place it in

/etc/init

It runs very early in the init process, and wipes the MSC partition. Useful for Transformers that boot Android by default; you can tell Android to boot in to recovery mode to boot Ubuntu, and then just reboot to get back to Android.
[Eee Pad Transformer Q&A, Help & Troubleshooting] natostanco:
I was trying to flash with ubuntu as default that's why it didn't work, tough it booted with ubuntu as default once and then it stopped working after a crash :s
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
It's very odd that it would work once then stop. Check your hashes and try reflashing it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
Follow-up

Right you are, rdnetto.

ad3658a13dd094cf8a6627588e5b13d3 /misc/bluetooth/bcm4329.hcd <!-- file used by android system -->

ad3658a13dd094cf8a6627588e5b13d3 /etc/firmware/BCM4329B1_002.002.023.0797.0879.hcd <!-- matching firmware -->

Thanks for the tip. [EDIT] Successfully pairing, but little/no functionality. Digging deeper; more details later. [/EDIT]
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
Bluetooth support update

For interested parties, bluetooth is now working. You need to make sure that there is NO valid bcm4329.hcd in /lib/firmware at boot. Instead, put a copy there as bcm4329.bak. After booting, run:

cp /lib/firmware/bcm4329.bak /lib/firmware/bcm4329.hcd && rfkill unblock 0 && modprobe bcm4329

followed by:

/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 921600 --bd_addr XX:XX:XX:XX:XX:XX --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2

It should say that it set line discipline. If you do this from adb shell, the window will become dedicated to keeping bluetooth up - do NOT close it. Open a new terminal to continue adb commands.

NOTE: Make sure to replace XX:XX:XX:XX:XX:XX with your device's bluetooth mac address.

The whole reason this wasn't working was because if brcm_patchram_plus doesn't receive an address here, it looks for the default in "ro.bt.bdaddr_path" which is a property of Android systems ONLY. Not your Ubuntu. Without your mac address, it will hang and tie up ttyHS2, making it unusable until you reboot. Unfortunately, this script is called without an address on boot, so unless you rename or remove the bcm4329.hcd file before rebooting, it will execute on startup and make ttyHS2 useless once again.

If you've used the above commands, issue "rm /lib/firmware/bcm4329.hcd" before shutting down. The .bak copy will remain for successive attempts. If you know how to edit the init script, more power to you. I'm still new to linux.

To find your bluetooth mac address, simply open "/data/misc/bluetooth/mac.txt" from your Android partition. The same folder has your valid bcm4329.hcd file.

More updates coming.

Wade
[Eee Pad Transformer Q&A, Help & Troubleshooting] darks1der:
Hye guys,

FrankC123 adviced me to look here for some information.

I am looking to install Backtrack 5 instead of ubuntu, so im able to do pen testing on the go without having to caary around my laptop.

I have the ARM img file of Backtrack, and i was hoping i can switch it with the Ubuntu file to get an install working.

Does anybody know if this will work?

I'm looking to get the project of the ground once i can get some information.

Any help is welcome.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Yes, but you'll need to manually install the kernel modules. You may also need a custom kernel since some of the network related stuff is disabled by default. Instructions for building them are on the wiki.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Thanks for that. The init script is /etc/init.d/bsp-tf101. Line 17 is the important one. It doesn't include the rfkill command, so that'll need to be added as well. (It also has a much lower baud rate specified, though I'm not sure why.)

For anyone else who's trying this out, /data (under Android) is mmcblk0p7, so you can just mount it to avoid switching between OSs.

I was able to successfully pair my N900 with it and transfer files in both directions. I'm using bluedevil under KDE, which might explain that.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
@braernoch, I've done some work on getting the internal speakers to work, but I wasn't able to get much further due to my lack of familiarity with the kernel. I posted the results in the dev thread, if you're interested.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
if you manage to fix it you would be a god :) the AC100 has exactly the same problem. They have a fairly good kernel team comprised of people who work for canonical and they haven't managed to crack it yet.
[Eee Pad Transformer Q&A, Help & Troubleshooting] CobraBytez:
So there's absolutely no way to get Ubuntu running on an sbkv2 device? Even something non-persistent like off a USB?
[Eee Pad Transformer Q&A, Help & Troubleshooting] yalkowni:
You might wanna try chroot. But expect to be LAGGY
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
that would be possible, but would come with the added risk of no recovery to save your ass if something should happen to go wrong.
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
I've never dissected a kernel before, but it must be possible:

https:/wiki.ubuntu. com/ARM/TEGRA/AC100#Sound_from_speakers

This no-dev-posts/no-outside-links is getting annoying. /rant
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Given I've never actually delved into the kernel source, this does not bode well...

The AC100 also uses the WM8903 AFAICT, so anything they have on it should be directly applicable.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
not directly, maybe indirectly though
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
Audio ideas

I take it back. I've been knee-deep in a ramdisk and two kernels all night. Makes sense bit-by-bit. I'm taking a different approach - what does the Android system have that Ubuntu doesn't? There's an interesting folder on the Android partition you should poke around in that's not even part of the kernel image:

/sys/devices/platform/soc-audio/

@rdnetto, specifically the file, "code-reg" - it allows you to set the registers of the WM8903 bitwise. Though by occam's razor, it shouldn't be necessary. Also in that folder is a subfolder called, "PCMC0D0P." I'd attach the files, but I can't yet.

Oh, and you mentioned wondering what detects headphone plug-in? Device "h2w" is a switch-state device used for headsets. So if you know when the device is loaded, it's that script. According to dmesg:

[ 7.211770] device: 'controlC0': device_add
[ 7.212108] HEADSET: Headset detection init
[ 7.212122] device: 'h2w': device_add
[ 7.212275] HEADSET: Headset detection mode
[ 7.212283] HEADSET: Config Jack-in detection gpio
[ 7.212492] HEADSET: Config Headset Button detection gpio
[ 7.212503] HEADSET: Config LineOut detection gpio
[ 7.212548] ALSA device list:
[ 7.212555] #0: tegra (WM8903)

Happy hunting. I need sleep.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Well, that helps a bit. We can read the value of h2w from /sys/devices/virtual/switch/h2w/state. In theory codec_reg should be writeable (once you change the permissions with chmod), but I'm getting 'bash: echo: write error: Input/output error'. Not sure whether this is from bash trying to write to the file or the function attempting to write to the actual registry - it happened no matter which register I tried to access.

For reference, the syntax is such that "echo 6 59 > codec_reg" should set register 0x06 to a value of 0x59.

There's also another interface in /sys/kernel/debug/wm8903, but I don't know if it's writeable or not. There doesn't seem to be a write access function in the source like for the sysfs one, but it might be non-obvious.
[Eee Pad Transformer Q&A, Help & Troubleshooting] dvhh:
modfied /etc/init.d/bsp-tf101

For people who don't know, bluez is successfully working with a bluetooth headset.

Thanks for the pointers.

#! /bin/sh

do_stop(){
#look if Board Support Package is already running
PS=$(ps -A | grep " brcm_patchram_plus\>")
if [ -n "$PS" ]; then
echo "* Stoping Bluetooth Support Package..."
killall brcm_patchram_plus
fi
}

do_start(){
#if already started then stop first
do_stop
#now start all board support binaries
echo "* Starting Bluetooth Support Deamon..."
# see : http://xdaforums.com/showpost.php?p=21305188&postcount=1441
# see : http://xdaforums.com/showpost.php?p=21328461&postcount=1445
rfkill unblock 0
modprobe bcm4329
#/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 3000000 --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2&
/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 921600 --bd_addr f4:6d:04:58:85:d9 --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2&
# making sure the nvtegra dev nodes have the correct permissions
echo "* Setting correct permissions on nvtegra device nodes..."
chmod 0666 /dev/nv* /dev/tegra_*
}

case $1 in
start | restart)
do_start
;;
stop)
do_stop
;;
esac
[Eee Pad Transformer Q&A, Help & Troubleshooting] riberet25:
Help Required Please..........

I installed the dual boot with Ubuntu and Andriod. Everything went well. Everything works fine - Ubuntu and Android.

I had a quick question - I want to install the Revolver ROM and get rid of the dual boot and keep only the Androis OS.

Can someone please guide me. I am little better than a novice but still have a lot of doubts. I used the original post instructions for dualboot using OLiFE.

Can someone please guide me or redirect me to the right post please?

Thanks
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
What would you like to do?

1. Backup device
2. Flash device <-- this option
3. Update device
4. Inject firmware
5. Onscreen Keyboard

Q. Quit

Please choose from 1, 2, 3, 4, or Q:

Then

How would you like to flash the device?

1. Dualboot
2. uboot (linux only)
3. asus boot (linux only)
4. stock <- This option

0. Return to Main Menu

Please choose from 1, 2, 3, 4, or 0:
[Eee Pad Transformer Q&A, Help & Troubleshooting] riberet25:
Improving the performance of Ubuntu

Thank you Steve for all your wonderful work. You have really simplified things for most of us and your work is commendable.

I was wondering if there are any things that could be done to improve the performance of ubuntu using the default kernel. The lag is really bothersome. Apart from changing the desktop environment to a lighter one is there anything else you recommend.

Thanks
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
I'm running into an odd error when compiling the kernel. The weird part is that it only happens on one PC - on the other everything works fine. I'm using gcc 4:4.6.1-2ubuntu5 and dtc 1.3. Any ideas?

drivers/net/smc91x.c: In function ‘smc_tx’:
drivers/net/smc91x.c:710:51: warning: variable ‘pkt_len’ set but not used [-Wunused-but-set-variable]
drivers/net/smc91x.c: In function ‘smc_phy_configure’:
drivers/net/smc91x.c:1045:6: warning: variable ‘status’ set but not used [-Wunused-but-set-variable]
LD drivers/net/arm/built-in.o
CC drivers/net/usb/cdc_ether.o
CC drivers/net/usb/cdc_ncm.o
CC drivers/net/usb/cdc_subset.o
drivers/net/usb/cdc_subset.c:221:2: warning: #warning You need to configure some hardware for this driver [-Wcpp]
CC drivers/net/usb/usbnet.o
LD drivers/net/usb/built-in.o
LD drivers/net/wireless/built-in.o
LD drivers/net/wireless/bcm4329/built-in.o
CC [M] drivers/net/wireless/bcm4329/dhd_linux.o
drivers/net/wireless/bcm4329/dhd_linux.c: In function ‘dhd_rx_frame’:
drivers/net/wireless/bcm4329/dhd_linux.c:1249:24: error: variable ‘save_pktbuf’ set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
Compile errors

Three changes I had to make to get kernel to compile:

1) Edit kernel/cpuset.c and change "!= task)" to "!= tsk)"

2) Edit drivers/net/wireless/bcm4329/Makefile and delete the flag -Werror. *The latest revisions to gcc force it to treat the warning as an error in dhd_linux.c.

3) Edit arch/arm/mach-tegra/board-ventana-misc.c and remove the entire if-statement that uses the instantiated-but-uninitialized variable g_NvBootArgsGPSPreemption. Remove the variable declaration, too. It's declared as an int, used as a boolean, and never given a value to begin with.

Your make should now succeed.
[Eee Pad Transformer Q&A, Help & Troubleshooting] v0id_walker:
noob asks:

hi there,

i would like to buy this device and use it as a tablet and linux netbook (i am using archlinux netbook right now)

I noticed that there are at least 2 ways how to run a full-fletched OS on this device (asus tf101)

First was to run the ubuntu in chrooted environment and second was to install as native OS. (as far as i know there are supposed to be more ways to do this too)

So my questions are:

1. Which one is better/has more stuff(like bluetooth/wifi or network/touchscreen) working. Can it run stuff like eclipse/lazarus/gcc?

2. Is it possible to have a dual-boot (Android/Ubuntu)?

3. The device needs to be rooted, i guess?

4. Is there a problem with rooting/unrooting?

Thanks to anyone willing to answer those questions, i guess someone already asked them but i could not find it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] braernoch:
listen to rdnetto and lilstevie.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
1) chroot may have issues with hardware stuff where Android already has exclusive locks on things. Where this is not the case, things which do not currently work on Ubuntu may work under it.

I would like to stress that the reason no-one uses chroot if they can help it is because it is painfully slow, and borders on unusable. Not to mention that 756 MB can still be a little restrictive for Ubuntu (you can fill it up with Firefox and a few dozen tabs), which means Android's overhead can be rather problematic.

2) Yes, dual boot is supported by OLiFE.

3) Strictly speaking, no. Rooting involves modifying (or replacing) the Android ROM so you have root access under it. You could theoretically flash the device with Ubuntu and stock Android, and it would work just fine. However, this has the same effects on your warranty as rooting does, since you effectively have a different kind of root access under Ubuntu.

This is because root access and the ability to flash the device are two different things.

4) Depends on the model. The original Transformers can be flashed (incl. SBKv2 devices, I believe). Primes have more sophisticated DRM (see androidroot.mobi for details) and cannot currently be flashed, AFAIK.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
nonononononononononononononono(takes a breath)nonononononononononono.

You don't just unlock the bootloader, APX is below the bootloader, it requires knowing the secure boot key, which is known for devices with a serial below B7O, there is no "do this and it will unlock nvflash access" you either have it, or you don't.
[Eee Pad Transformer Q&A, Help & Troubleshooting] canedha:
haha, i like ur style!

btw. thx for this awesome stuff ur doing here

the first time i put ubuntu on my tf i used franks tools.

i want to reinstall everything again with OLife for being able to use CWM even with ubuntu installed (the option where ubuntu boot is removed, cwn installed, used and removed and ubuntu installed back again).

after frank tools i had root right on, will this be like this with OLife as well or will i have to use razorclaw/nachoroot whatsoever?

what will happen to my data, programs in ubuntu etc when using cwm as mentioned above? will only the bootloader be overwritten for the time being or the whole partition? (i thinks its the first option but i dont want to risk it ^^)

thx again :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] yalkowni:
You don't need to reinstall everything just to use olife just go straight to flashing cwm through Olife
[Eee Pad Transformer Q&A, Help & Troubleshooting] canedha:
thx and what about root?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
CWM does not touch your programs or data - it only writes to the LNX partition which the bootloader reads from. However, if you use OLiFE to flash a new configuration (as opposed to flashing a single partition), then you will lose all data saved on the device.

If you use OLiFE with any non-stock ROM (e.g. Prime), then you do not need to root it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
creating custom debian image

Hi, i am creating a custom debian image, in order to use your OLIFE script to install it.

I have a couple of doubts.

I have some issues with debootstrap in debian wheezy/unstable/experimental. Nothing i couldn't fix, I also have a sheeva plug (arm architecture) with debian installed.

Anyway, i am writting too much. Let's cut the cheese:

First question:

all /dev/* devices already created in your ubuntu.img... are they especially created for the transformer? does not the kernel create them the first time you boot? did you use mknod to make them?

Second question:

I've seen the fstab in your ubuntu.img. How did you create it? I mean... how do you know de UUID of the disk even before "format/repartition" it? ¿could i use the same one?

Third question:

You haven't create any user in your installation, is it really necesary to be root to use ubuntu? I think that's a security issue,

Last question:

My transformer is very new (christmas present), and its b70, but sbkdetect sais it's sbk1 so i guess there is no much risk (i now there is allways a risk) because a could use nvflash to restore it. couldn't i?

Thanks and sorry for so many questions, but i didn't find enough information en both threats or in the wiki.

cheers
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
1) /dev is kernel maintained not files in the system.

2) I know the UUID because I got it with blkid.

3) Your user is created on the first boot with oem-config.

4) there is no chance of bricking if you do have an sbkv2 device because quite simply you need nvflash to install, not having nvflash access means no chance of bricking.