Relative Content

Tag Archive for low-level

Reverse engineering: what is it really good for? [closed]

It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago. I have some innocent/beginner questions: What is reverse […]

Books/sources on inner workings of JavaScript [duplicate]

This question already has answers here: What is the path to JavaScript mastery? [closed] (9 answers) Closed 11 years ago. When I started studying C++ a couple of years ago, a lot of the books and texts I read did a very thorough job of explaining, how the code written would translate into concrete operations […]

Is this theoritically possible to create a full android device simulator

I want to adjust firmware components, or to have opportunity to test something on an android device. A problem is that usually modern devices prohibit to recover a brick for free.
Theoritically it is possible to program a full device simulator, primary to handle first low level stages (like bootloaders, and possibly boot, recovery, fastboot), not necessary to even program a workable screen and therefore OS, but preferable. A one way i know how to get hardware info is look into /proc using root.
In /proc/iomem there is common device memory map,
In /proc/devtree there is list of hardware components, versions and their base address to interact with,
/proc/devices has list of some unknown devices and /proc/cpuinfo has a list of all cpus with their version. Some additional useful info how that individual device work i think may be found in product documentation.
To find base address of images may be copied a scetter file from firmware and, some additional possibly not needed addresses may be resolved by unpacking boot and recovery.