FAQ - Frequently Asked Questions

How to flash a Rom properly?

  • backup all important files (e.g. contacts) and store them on your MicroSD-Card or on your PC/Laptop
  • copy the rom and gapps you like to install to your MicroSD-Card (make sure Gapps match the Android version of the Rom!)
  • boot into your custom recovery
  • make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop (some of the following are named slight different depending on the recovery you use)
    • wipe cache
    • wipe dalvic cache
    • wipe/format system
    • wipe/format data
    • reboot your recovery once!
    • flash rom
    • flash gapps
    • reboot and give your device some time to do it’s first boot!

What Rom do i use on my Galaxy Tab2?

  • You can use a device specific rom for your device (discontinued), the Rom name need to match your model.
  • You can use a unifed Rom for your device.
    • GT-P3110, GT-P3113, GT-P5110 and GT-P5113 user: flash “espressowifi” Roms
    • GT-P3100 and GT-P5100 user: flash “espresso3g” Roms
Note: Your device get detected automatically on unified builds and loads proper driver and config at boot! You shouldn't notice any difference compared to the device specific builds (only changed romname).

How to re-calibrate the compass on my Tab 2?

  • The compass sensor is calculated from the accelerometer and magnetic field sensors. If the values reported by the compass sensor are not right, you can re-calibrate the magnetic field sensor with the following steps:

    adb shell stop geomagneticd
    adb shell rm /data/sensors/yas.cfg
    adb shell rm /data/sensors/yas-backup.cfg
    adb shell start geomagneticd
  • Now start an application using the compass sensor. Move the device in every direction, with a rotation around each axis: the device should now be re-calibrated.

Rom installation failed on "error 7" in recovery, what can i do?

Best will be to post a recovery.log. There’s an option inside your recovery to create one.

You can get the log to your PC using adb:

  adb pull /path/to/log/log.name

If this is not possible for your: tell the whole message you get! There are different “error 7” messages out!

  • it could be you used a recovery for a different device (p3100, p3110, p5100 and p5110 had a own recovery in the past!)
  • it could be you flashed a file/rom not made for your device
  • it could be your recovery is to old (official CWM is to old, a lot of user still use it)

How to enable root access?

For security reasons i’ve removed root from all my ROMs. If you need root access:

How do i get proper logs?

Well, there are some apps out (e.g. Syslog App) which can help getting usefull logs, but i prefer using adb to get those logs:

  • Logcat:

    adb shell logcat > logcat.txt

    (abort/stop logging pressing ctrl + c on your keyboard)

  • Radio Logcat:

    adb logcat -b radio -v time -d > logcat_radio.log
  • Dmesg:

    adb shell dmesg > dmesg.txt
  • last_kmsg: (make sure root is enabled!)

    adb shell su -c "cat /proc/last_kmsg" > last_kmsg.txt
  • audit.log: (make sure root is enabled!)

    adb root
    adb pull /data/misc/audit/audit.log

What's the difference between the "old" and the "new" kernel source you are using?

First of all: the biggest part of our new kernel was done by Ziyan @ XDA-Developers. The kernel is the heart of our roms. Some words about “new” kernel:

  • based on official omap4 kernel source (p-android-omap-3.0-dev branch)
  • merged Stable 3.0.101 kernel source linux-stable/linux-3.0.y
  • full commit history
  • BCMDHD updated to 1.88.45 from 3.4 Kernel source (Note: The Samsung BCMDHD used to read the factory MAC address from /efs. Accessing the filesystem in-kernel is a very bad practice, but what can we expect from Samsung? We now calculate the MAC address based on the SoC Die ID: this is unique for all devices, and ensures that the same device will always have the same MAC address, not a randomly generated one.)
  • last_kmsg support
  • big debloat before adding Tab2 specific driver, boardfiles, etc. on top of the “new” kernel
  • use dynamic tiler allocations (more free ram available)
  • auto detect tab2 variant on boot (read out lcd_panel_id command line parameter from our bootloader to detect the board type)
  • added a property (/sys/board_properties/type) to show the board type, used by userspace drivers to configure stuff accordingly

    Note: Some rom changes depend on this property (e.g load proper sensor driver, audio config etc.) - old custom kernel don't use the porperty and will cause issues on those roms!
  • One kernel source for all Android Versions (4.4 and newer, only different defconfig for 4.4 Roms)

We now use the new kernel on all of our roms (Android 5.1 and newer, but we also switched to it on some of the official 4.4 Roms like CM 11.0). Kernel Source can be found here , History from cleanup and update here.

How to change the bootlogo of my Galaxy Tab2?

There’s a great tutorial by Ketut Kumajaya which i have slight updated and added

The tutorial can be found here

I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.

16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.

From the EMMC data sheet:

5.1.7 End of Life Management:

The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.

But, reliability of the operation can not be guaranteed after end of life.

On a faulty EMMC firmware it happens a lot faster.

What are the symptoms?

  • Uninstalled apps and deleted files are back after a reboot
  • Formating the storage doesn’t work (after reboot the old rom and apps are back)
  • You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)
  • … there might be some more, but only to mention some …

In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.