Quote:
Originally Posted by nystagmus
|
Yup, that happens on most android e-ink devices (and crappy phones/tablets). Normally they route the traffic from one process to another using android binder IPC and the service that sends the traffic is buried in one of the core apks, like SystemUi.
I don't have that specific device but I got a friend's Likebook during a few days for testing and cleaning it up. It shows the same behaviour. In principle they seem like affiliate links that try to trick these sites, by hiding a window so the user cannot see it but the site thinks it can and flags "yet another impression for this referral". I doubt it has the wanted effects.
But, from user pov, they seem not too harmful, as they're not sharing user sensitive data and the traffic received is a lot more that the traffic sent.
Quote:
Originally Posted by nystagmus
|
fastboot is not a bootloader, is a protocol. And devices can implement it or not (for instance samsung devices do not implement a fastboot compliant bootloader).
Your link goes to OEM / vendor information to implement a device based on AOSP following google best practices. Not final user info.
Anyways, unlocking the bootloader just makes the system to skip partition signatures, so it can boot with a modified boot.img.
In my experience most crapphones don't implement any kind of boot verification and will happily boot with a modified boot.img (with an added service to run Chainfire's su daemon). Even more, most of these craps use AOSP test keys to sign updates, so it is possible to sign you own updates and flash them from stock recovery.
The difficult part of the process is getting a dump of the original phone flash. Without this (which most vendors don't provide) messing with low-level stuff is a quick way to get a brick, and since the "community" for these devices is kind of 0, the way to recover from a brick is 0 too.