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!

---

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
• 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?

OMAP4-AOSP Roms aren't pre-rooted, you need to use SuperSu or the OpenSource SuperUser to get rooted.

---

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:

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

---