Slidepad 704ce - CWM Recovery and Fastboot mode

dropcap-android-tablet

android-clockworkmod-recovery

If you are having a Slidepad 704ce tablet running a rooted ICS 4.0.4 or a rooted JB 4.1.1, next step is to install ClockWorkMod Recovery.

It will allow you to do complete system backup & restore, to flash an alternative firmware, to format the Nand partitions, ...

Another interesting tweak with this tablet is to access FastBoot, which is not available straight from boot.

This article explains how to access the hidden FastBoot menu and how to install a specific port of CWM compatible with our A13 tablet.

This procedure has been done to be run on a Ubuntu workstation, but it should be easily adapted to any other Linux flavour, and even to a Windows PC.
As a pre-requisite, you need to Install Android tools on your Ubuntu box.

Read more: Slidepad 704ce - CWM Recovery and Fastboot mode

Slidepad 704ce and 704cet - JB 4.1.1 : Root your Tablet

dropcap-android-rooted

slidepad-704ce-tablet

Memup Slidepad 704ce / 704cet are very affordable Android 7' tablets with a Allwinner A13 SoC (Cortex A8 processor), 4 Gb flash memory, 512 Mb RAM, a microSD connector and a fully working micro USB OTG port.

Memup posted on their web site some new Jelly Bean 4.1.1 firmware version for these 2 tablets. This firmware is flashable thru a tool provided in the firmware archive called LiveSuit. For Slidepad 704 ce, the Jelly Bean firmware version runs very well, it is much smoother than previous ICS build.

But main drawback of these firmware is that they are not pre-rooted.

On Slidepad 704ce, I tried to flash a signed version of SuperSU from the stock recovery (3e). It has been accepted, but it didn't flash the /system partition. Any unsigned upate has been refused by the stock recovery. Then I tried with no luck to root the tablet with latest ICS/JB adb restore exploit.

As no other exploits are available at this time for Jelly Bean, what to do ? To stay with an unrooted tablet ? Too sad ... As Santa Claus says : If the door is closed, enter by the window. If the window is closed, enter by the chimney :-)

So I decided to try the hard way : by cooking the original Memup ROM to include ClockWorkMod Recovery natively. This allows to root it by flashing an unsigned su update. And after lots of efforts, it worked !

LiveSuit only runs on Windows OS. The following guide has been run from a Windows XP computer.

So, let's start ...

Read more: Slidepad 704ce and 704cet - JB 4.1.1 : Root your Tablet

Slidepad 704ce - Modify the Root filesystem (root logo, ...)

dropcap-android-cooking

When doing some tweaks on your android device, you may need to change some parameters on the root filesystem. For example you may have to modify /init.rc, /init.sun5i.rc, /initlogo.rle or your root logo /initlogo.rle (the second one displayed in the boot process).

You will then quickly realise that whatever change you will do on these files will be lost after every reboot, even if you do it as root.

This comes from the fact that on android devices the root filesystem is mounted as a initramfs. So it is unpacked and mounted into RAM at every boot. Whatever change you do is done in RAM only.

So to make permanent changes to your root filesystem, you need to modify the files whithin the initrd.img file used during the boot process.

This guide will explain how to extract Root image from Slidepad 704ce

  1. unpack it & extract initrd files
  2. change the boot logo
  3. repack the modified initrd files
  4. flash back the root image on the device

It has been specifically designed for Slidepad 704ce, but it should be applicable to any device powered by A10 or A13 Allwinner SoC.

Read more: Slidepad 704ce - Modify the Root filesystem (root logo,...)

Slidepad 704ce - Modify the Bootloader (boot logo, ...)

dropcap-android-cooking

When doing some tweaks on your android device, you may need to change some parameters on the bootloader, for example the first boot logo (the second one is in the root filesystem).

The bootloader filesystem in a vfat filesystem and it is recorded in /dev/block/nanda.

This article will explain all the steps to make permanent changes to your bootloader :

  1. extract bootloader image from Slidepad 704ce
  2. mount it as a vfat filesystem
  3. change the boot logo (for example)
  4. unmount the vfat filesystem
  5. flash back the updated bootloader on the device

It has been specifically designed for Slidepad 704ce, but it should be applicable to many devices powered by A10 or A13 Allwinner SoC.

Read more: Slidepad 704ce - Modify the Bootloader (boot logo,...)

Slidepad 704ce - JB 4.1.1 : Tweaks for Rooted Tablet

dropcap-android-tweaks

Once you have rooted your Slidepad 704ce following Slidepad 704ce - Jelly Bean 4.1.1 : Root your tablet you have opened the gate to unlimited modifications of your device.

This article will explain some simple tweaks that should enhance your android experience on the Slidepad 704ce.

It will explain how to :

  • update your tablet identification & framework to have a full access to Play Store
  • change your tablet DIP to maximize the screen display
  • tweak Google Search and You Tube incompatibilities

This procedure has been done to be run on a Ubuntu workstation, but it should be easily adapted to any other Linux flavour, and even to a Windows PC.

As a pre-requisite, you need to Install Android tools on your Ubuntu box.

Read more: Slidepad 704ce - JB 4.1.1 : Tweaks for Rooted Tablet

Slidepad 704ce - Cook your own ROM

dropcap-android-cooking

Slidepad 704ce is based on a Allwinner A13 SingleOnChip. The ROM cooking procedure of Allwinner A10 & A13 devices is done thru 3 main steps :

  1. Extraction of original firmware (under Windows)
  2. Modification of filesystem components (under Linux)
  3. Assembly of final firmware (under Windows)

The filesystem components that may be modified are typically :

  • the bootloader
  • the root filesystem
  • the recovery filesystem
  • the /system filesystem

This article will explain the simple steps needed to cook a new ROM for a Slidepad 704ce. This process needs 2 different computer environments :

  • Windows for ROM extraction and repacking
  • Ubuntu for filesystem modifications (but any other Linux flavour should do).

It has been specifically written for Slidepad 704ce ROM cooking, but it should be applicable to many (if not any) Allwinner A10 or A13 SoC devices.

Read more: Slidepad 704ce - Cook your own ROM

Nexus S - Phone painfully slow after ICS or JB OTA update

dropcap-android

If you have bought your Nexus S smartphone outside of any operator pack, you are getting regular Other The Air updates straight from Google.

For example, when I bought mine 9 months back, it was running Gingerbread 2.3.6. Then I got OTA updates for :

Ice Cream Sandwich 4.0.4 : After that update, my phone was showing some strange behaviour mostly on the desktop screen.
Sometimes some parts of the screen where not refreshed, some fonts where becoming bold, ...

Jelly Bean 4.1.1 : After that update, my phone became extremely slow.
For example, I was sometimes left 5 seconds on a white screen while entering the SMS application.
Same type of behaviour entering Gmail, ...

These problems come most of the time from the phone's system caches that might have been corrupted by the OTA update.

The clue is to purge these cache. After this operation, you will rediscover your Nexus S in full speed. Jelly Bean will be blazing fast.

This operations needs your phone to be rooted. If your phone is already rooted you won't loose any data, it's totally transparent.
But if your phone is not rooted, you'll need to root it first and it will wipe all your data.

Read more: Nexus S - Phone painfully slow after ICS or JB OTA update

Nexus S - Get rid of Recovery boot failure

dropcap-android

This tutorial supposes that you have already rooted your Nexus S phone.

As rooting process involves flashing a new recovery, you will realize that after you've rebooted your system at least once under ICS, your favorite recovery is not accessible anymore thru fastboot menu.

nexus-s-recovery-red-triangle

Instead of your favorite recovery, you will get a nice picture of Android on the back with an exclamation mark in a red triangle.

At this stage, your phone is stuck, you can only reboot it by removing the battery or wait for a very long time till it reboots by itself !

In fact, at every boot, your android system replaces your TWRP recovery with that ... dead end.

This article explains how to get rid of that real bad behaviour and to be able to enter your favorite TWRP recovery anytime you need it, without reflashing it.

This procedure has been tested on a Nexus S running Ice Cream Sandwich 4.0.4 and Jelly Bean 4.1.

The OTA update from ICS to JB rewrite the faulty file !
So, after a Jelly Bean OTA update, you need to re-root your Nexus S and to apply this procedure once again.

Read more: Nexus S - Get rid of Recovery boot failure

Nexus 7 - Root your tablet with Ubuntu Linux

dropcap-android-rooted

If you want to root your Google Nexus 7, a lot of stuff is available on the net from different sites and forums.

nexus7-front-panel

But most of the guides you get are using some tools running under Windows.

Obviously, you can do the same from an Ubuntu workstation, but all the steps are not trivial.

So, this article will explain all the steps needed to :
 * have your Nexus 7 tablet properly recognised by udev
 * OEM unlock it
 * install TWRP touch recovery
 * root it
 * protect your recovery image from removal

 

The complete procedure has been tested with a Google Nexus 7 running ICS 4.0.3, Jelly Bean 4.1.1, 4.2 and 4.2.1 from a Ubuntu Precise LTS 12.04 computer.

As a pre-requisite, you need to Install latest Android tools on your Ubuntu box.

Read more: Nexus 7 - Root your tablet with Ubuntu Linux

Nexus S - Root your phone with Ubuntu Linux

dropcap-android-rooted

If you want to root your Google Nexus S, a lot of stuff is available on the net from different sites and forums.

nexus-s-front

But most of the stuff you get on the net is oriented toward using Windows tools.

Obviously you can handle all the needed steps from an Ubuntu workstation.

But all different steps are not trivial to setup and follow.

This article will explain all the steps needed to :
 * have your phone properly recognised by udev
 * OEM unlock it
 * install TWRP touch recovery
 * root it

The complete procedure has been tested on a Google Nexus S with Ice Cream Sandwich 4.0.4 and Jelly Bean 4.1.1 from a Ubuntu Precise 12.04 computer.

As a pre-requisite, you need to Install Android Tools on your Ubuntu box.

Read more: Nexus S - Root your phone with Ubuntu Linux

HTC Wildfire - Flash your phone from HTC Sense to CyanogenMod AOSP

dropcap-android-cyanogenmod-7

This guide explains how to convert your HTC Wildfire mobile phone running Android with HTC Sense to a brand new Gingerbread Android Open Source Project smartphone.

HTC Wildfire

But, you may ask : Why to do so ?

Some of the answers may be :

 * to get rid of the Sense user interface
 * to upgrade the phone to the latest Android 2.3.4 branch (Gingerbread)
 * to get a very fast & responsive phone
 * to feel like a real geek :-)
 * to have fun ...

 

All the following steps will be done with a Ubuntu workstation.You won't need any proprietary operating system at any stage.

I will use an Android ROM called CyanogenMod 7.1 from the Cyanogen project.

This ROM is straight from the AOSP project and has been tested to be very stable and very responsive on the HTC Wildfire.

Read more: HTC Wildfire - Flash your phone from HTC Sense to CyanogenMod AOSP

Android - Setup Subsonic client to stream over 3G network

Android

Subsonic is a really efficient music streaming server. You can get a good overview of the possibilities from the main site http://www.subsonic.org/.

This server can stream your complete music library to any internet connected device, handling on-the-fly compression. A subsonic client is available on the Android market for all android devices.

The main specificity of streaming music to a mobile phone, is that it uses a 3G or even a Edge access, where the available bandwith is quite restricted. You then need to use a very efficient codec and a high compression ratio to remain compatible with the network capacity.

After doing few tests, I realised that Ogg Vorbis is very good at low bitrate. Using this open source codec, it is possible to keep a good music quality with a bitrate as low as 80 or 96 kbits.

This tutorial explains how to configure your Subsonic personnal server to stream your music to your android device thru your 3G data plan, using a 96kbits Ogg stream.

Read more: Android - Setup Subsonic client to stream over 3G network

Page 2 of 2