May 15

TF201 CM9 External GPS Support Testing [Updated 17/05/2012]

In an effort to support the newly released external GPS expansion in CM9, we are happy to present our GPS Wrapper!

Once this has been tested, it will be merged into CM9!

On our small-scale tests this seems to work fine, however we would like to get the widest range of test data possible!

This is not guaranteed to work as it is Work-in-progress,  however there are instructions below on how to restore!

How to use:

  • Install the update.zip below from CWM recovery
  • To switch between internal and external GPS, you need to attach or detach the GPS Dongle, then turn GPS on/off in settings. The GPS wrapper will make sure to take care of the rest.

Updated 17/05/2012 – New wrapper that should allow the change of device without GPS settings toggle

update.zip Install (CM9 Only)

  • Install this update.zip

Manual Install Instructions (CM9 Only)

  • extract zip file bellow
  • navigate to the /system/ directory within that folder
  • adb root
  • adb remount
  • adb push lib/hw/gps.tegra.so /system/lib/hw/
  • adb push lib/hw/gpsdongle.tegra.so /system/lib/hw/
  • adb push lib/hw/gpsinternal.tegra.so /system/lib/hw/
  • adb push etc/u-blox.conf /system/etc/
  • adb push etc/gps.conf /system/etc/
  • adb shell reboot

To switch between GPS devices

  • Just switch GPS off/on in settings while the dock is either connected or disconnected

Manual Uninstall Instructions (CM9 Only)

  • adb root
  • adb remount
  • adb shell cp system/lib/hw/gpsinternal.tegra.so system/lib/hw/gps.tegra.so
  • adb push lib/etc/gps.conf.old /system/etc/gps.conf
  • adb shell reboot

Links

Permanent link to this article: http://androidroot.mobi/2012/05/15/tf201-cm9-external-gps-support-testing/

Apr 01

SBKDump v1.0 (April fools!)

Update: This was obviously an april fools. This tool won’t dump your SBK. 

 

After much persistence androidroot.mobi has FINALLY BROKEN the security around the Tegra AES Engine and we are able to dump your SBK.

We know it’s a Sunday and this isn’t a good time for a release but we’re so excited to be able to share this everyone that this post will not be a teaser – WE ARE RELEASING OUR SBK DUMPING TOOL- RIGHT NOW!

Note that this requires a rooted device! It needs to access low-level hardware that just isn’t possible as a regular user!

To get the tool download it here: sbkdump v1.0

The tool is a command line utility so you’ll need to run the following commands:-

adb push sbkdump.bin /data/local/
adb shell
$ cd /data/local/
$ su
# chmod 755 sbkdump.bin
# ./sbkdump.bin

Please note that this tool is rather rough and ready and we hope to provide a nicer tool in the future but for now we just want to get it out there!

Permanent link to this article: http://androidroot.mobi/2012/04/01/sbkdump-v1-0/

Feb 24

Aaaaaand, we’re back. CM9 for ASUS Transformer (TF101) back on track

Right on the heels of CM9 for TF Prime, we have CM9 for original TF coming soon!

Don’t quite have a video or a screenshot yet, but rest assured that our work on CM9 for TF prime has resumed now that ICS is out for it :)

Stuff that now works compared to our previous (unreleased) versions:

  1. No more green overlays!
  2. Full hardware acceleration, including video playback
  3. Sound
  4. Camera

We are working on getting this and the TF201 tree merged into official CM, but until then our device & vendor trees are available on the AndroidRoot github: https://github.com/AndroidRoot/

Images will be out as soon as possible!

 

Permanent link to this article: http://androidroot.mobi/2012/02/24/aaaaaand-were-back-cm9-for-asus-transformer-tf101-back-on-track/

Feb 23

Ubuntu on the Transformer Prime

As some of you saw earlier I (lilstevie) posted a screenshot of Ubuntu on the Prime on twitter.

This is something that is still a few hours/days away from release, depending how much time I have to spend on packaging it up. The picture I tweeted was a teaser that I shot in the excitement of things at least basically working. It is my TF101 image with the kernel modules injected from the Prime honeycomb kernel. I had this part prepared about 2 weeks ago when my prime arrived.

For the last week I have been porting over the applicable patches from the TF101 kernel and making sure the tree builds. Being the third device that I have done this to now, I know all the basic patches required to bring up Ubuntu on these android devices. I’ve applied them, as well as the wonderful BCM4329 driver patch done by vhda. I also enabled the display class config option, in the hope that it would support linux4tegra drivers.

Today with the bootloader unlock release gave me the chance to test out everything I have had waiting. Some of it went better than I could hope, other parts need a lot of work.

Let’s look at what does work first:

  • Wifi – Same patch as for the TF101.
  • Keyboard (if you have a dock).
  • USB Host (if you have a dock).

partially working:

  • Graphics Acceleration – Only 2D at this point.
  • Touchscreen – It works but every few touches are off target by 1/2 the screen.

not working or tested:

  • Bluetooth.
  • Trackpad.
  • Sound.
  • Sensors (ALS, Gyroscope, Accelerometer, GPS, magnetometer).
  • Shutdown, Reboot, Suspend.

What this all means.

The bootloader unlock has given us a wonderful opportunity to explore the Tegra3 hardware, and with a bit of work we should have a relatively stable and fast Ubuntu running on the TF201. After a little bit more fiddling around with the kernel I will be releasing a pack similar to OLiFE that uses the fastboot mode to flash images required.

Permanent link to this article: http://androidroot.mobi/2012/02/23/ubuntu-on-the-transformer-prime/

Feb 22

Cyanogenmod 9 for Asus Transformer Prime!

Now you have CWM, we thought we would give you a reason to install CWM!

As you can see, most, if not all, hardware already works!

We are expecting a beta within a few days, so keep an eye on this space! :)

Permanent link to this article: http://androidroot.mobi/2012/02/22/cyanogenmod-9-for-asus-transformer-prime/

Feb 22

Introducing CWM for ASUS Transformer Prime

Update: Fixed download links.

Update2: YES, this tool does require that you have an unlocked Prime!

Update3: Fastboot tutorial updated to use the *BLOB*. This should work fine. Blame Asus/Nvidia for not making fastboot work like it should.

ASUS finally released the unlock! :)

This means, it’s time to get CWM on there. Enjoy! We have been preparing CWM for a little while, but for obvious reasons we haven’t been able to test until now :) Stay tuned for more awesome things for Transformer Prime! :)

CWM

Download Link: CWM Blob |  Just the CWM image | Update.zip(TBD)

Instructions:

  1. Root your TFP
  2. Download the blob file (tfp_CWM5_androidroot.blob)
  3. adb push tfp_CWM5_androidroot.blob /data/local/blobfile
  4. adb shell & su
  5. dd if=/data/local/blobfile of=/dev/block/mmcblk0p4
  6. Reboot!
  7. That’s it :) We plan to release an update.zip suitable for flashing from the stock unlocked recovery to make this even easier!

Instructions for non-rooted Primes (or those who’d rather use fastboot):

  1. Get fastboot from here, and extract it.
  2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
  3. Power off your prime.
  4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
  5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
  6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
  7. Profit!

Permanent link to this article: http://androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/

Jan 31

Introducing Ratchet – The ‘Unknown Serial’ Fix

We are proud to announce Ratchet, a quick fix for Asus Transformer Primes that are experiencing the “unknown serial” issue (reference thread). This tool will recreate the p5 configuration partition, by writing the UUID, and asking the user for the serial number to write out. The latter is found on the packaging box of the Transformer Prime, or on the stickers on either the tablet or the keyboard dock.

By registering this serial number in the configuration of the device, the tablet is from then on able to check for OTA updates from Asus.

About the “configuration partition” (mmcblk0p5)

This is a partition on Asus devices that should contain per-device data, such as the serial number, UUID, sensor calibration and Wireless / Bluetooth MAC addresses. Units that suffer from the “unknown serial” issue are simply missing this data (presumably an error in manufacturing / quality control). As stated above, this tool will recreate this partition to a state that will have correct UUID and serial number.
The other information on the partition (sensor calibration / MAC addresses) is not vital to normal system operation. To clarify, the MAC addresses just default to the vendor burned-in MAC addresses (Azurewave/Broadcom), so this is not an issue.

Howto

This tool requires your device to be rooted, and you need to have ADB access to your device.
You can, however, also get a temporary root shell by means of the recently discovered exploit ‘mempodroid’, which is also explained in detail on this thread.

The archive for Ratchet contains a binary for mempodroid, just in case.

If your device is not rooted beforehand.

* Unzip the archive.
* Make sure the USB drivers for the Transformer Prime are installed, as well as ADB (Android SDK).
* adb push mempodroid /data/local/
* adb push ratchet /data/local/
* adb shell (You’ll now see a shell@android:/ $ prompt)
* chmod 755 /data/local/mempodroid /data/local/ratchet
* /data/local/mempodroid 0xd9ec 0xaf47 /data/local/ratchet
This is where the magic happens. Make sure you enter your serial number correctly, all in caps!
* Reboot your device.
* Done!

If your device is already rooted (su/Superuser installed).

* Unzip the archive.
* Make sure the USB drivers for the Transformer Prime are installed, as well as ADB (Android SDK).
* adb push ratchet /data/local/
* adb shell (You’ll now see a shell@android:/ $ prompt)
* su (You should now see a shell@android:/ # prompt)
* chmod 755 /data/local/ratchet
* /data/local/ratchet
This is where the magic happens. Make sure you enter your serial number correctly, all in caps!
* Reboot your device.
* Done!

Afterwards, verify if ‘About tablet’ in Settings shows your Serial Number.
You can, alternatively, check by ‘getprop ro.serialno’ in an adb shell.

Downloads

* Download Ratchet

Ratchet is released under the GNU GPL v2 license. Source code is available on AndroidRoot.mobi GitHub.

Credits

  • IEF
  • kmdm
  • RaYmAn
  • Bumble-Bee
  • lilstevie

If you’d like to donate to our cause, you can do so here:

Permanent link to this article: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/

Jan 15

An analysis of ASUS Transformer Prime security

So, now ASUS Transformer Prime has been out for a while and we decided it’s time to give a quick rundown of the security features in the Prime.

The Security

First, a quick list of security features:

  1. Secure Boot Key (SBK)
  2. Encrypted Bootloader (Same as ASUS Transformer)
  3. Hidden boot & recovery partitions (Same as ASUS Transformer)
  4. Cryptographically signed boot & recovery partitions (New)
  5. Cryptographically signed staging blobs (New)

Read the rest of this entry »

Permanent link to this article: http://androidroot.mobi/2012/01/15/an-analysis-of-prime-security/

Dec 13

Thoughts On Android Tablet Security

I’ve been around the Android scene for the last few years, and in the area of phones there has been a lot of change happening in regards to the viewpoint of manufacturers towards unlocking.
With manufacturers allowing the end-users to unlock their devices (at the expense of their software warranty), this allows the user to root and install any software they desire. This can include custom roms and uninstall preinstalled apps. Unfortunately, this has not been the case with Android tablets, where the majority of these are being shipped with ever increasing security, to lock the end user out of full control of their devices.
These include the Asus Transformer (3G) / Slider and Acer Iconica A500. I was hoping this was just a Google enforced rule for 3.2. But this doesn’t seem to be the case.

From information gathered from an Asus Transformer Prime ROM we see yet another security measure being enforced, namely “blob” packages being signature checked. This means that the old method of flashing boot/recovery partitions like on the TF101(G)/SL101 will no longer work on the TF201 because of added security.

I personally have an issue with manufacturers outright locking down a device that I own, preventing changes that I want to make to it, not just for custom ROMs, but for security and the ability to install other operating systems (like Ubuntu), that these tablets will be able to run. Below, I’ve listed some of the reasons why manufacturers should be unlocking these devices for their owners in a controlled way.

  • Security: the recent Razorclaw exploit that allowed the rooting of the TF101(G) / SL101 posed an issue, it highlighted a huge flaw in which any application could gain full control of a device, without the OS giving it any permissions. This could not be removed without first rooting a device. If this hole was found by an unsavory character first (as opposed to us), they might have used it to covertly exploit any affected device and the end-user would not have been able to secure their device on their own.
  • Other OS: the Tegra2 platform can run Ubuntu very well (let alone what Tegra3 can do) in a portable form-factor. As such, an end-user could benefit greatly from running Ubuntu on these devices, providing them with a choice over the vendor-supplied OS.
  • Controlled unlocking (primarily intended for manufacturers): When unofficial methods to gain full control of these devices are used, there is no control whatsoever by the manufacturer. This means that manufacturers have no idea if a device has been unlocked (causing warranty issues). If a controlled method was introduced, manufacturers could keep track of which devices were unlocked and void the warranty. This is obviously a trade-off for the end-user in exchange for more freedom, but it is a fair one at that.

This has probably been a long winded way of saying that Android tablets are moving in the opposite direction of phones, which makes less sense than ever, because tablets are usually under less restrictions/agreements with carriers, as opposed to phones.
This statement is intended to reach out to both the people that can make a change in the industry, but also to create awareness among the community to get a movement going that stands up for their rights.

P.S we have thoughts on how to make a controlled unlocking service for tegra2/3 devices…

 

Permanent link to this article: http://androidroot.mobi/2011/12/13/thoughts-on-android-tablet-security/

Nov 14

Introducing: Razorclaw v1.0.1 (Updated Dec 25: Don’t get latest OTA!)

After a long period of radio silence, we are proud to announce Razorclaw!

ASUS latest updates to all of the tablets removes the ability to root your device with razor claw! If you want root, stay with the versions listed below!

Razorclaw is a one-click root for ASUS Transformer. It takes advantage of ASUS new App Backup feature to provide a nice, smooth and simple rooting experience.

It has currently been tested on the following devices and ROM versions:

  • ASUS Transformer TF101 (8.6.5.19)
  • ASUS Transformer 3G TF101G (8.6.6.19)
  • ASUS Slider SL101 (8.6.5.18)

Links can be found at the end of this post.

Razorclaw

Razorclaw

This root has been a team effort from:

  • IEF
  • kmdm
  • RaYmAn
  • Bumble-Bee
  • lilstevie

If you’d like to donate to our cause, you can do so here:

Downloads

  • Market link Pulled from market.
  • APK
  • Binary (TBD)
  • Source


Permanent link to this article: http://androidroot.mobi/2011/11/14/introducing-razorclaw-v1/

Older posts «

Bad Behavior has blocked 12894 access attempts in the last 7 days.