#Spreadtrum tool v.1.0 released install#
#Spreadtrum tool v.1.0 released update#
#Spreadtrum tool v.1.0 released manual#
#Spreadtrum tool v.1.0 released software#
#Spreadtrum tool v.1.0 released Bluetooth#

The TTL fixer is limited to Qualcomms only (didn't work on MTK anyway) for the time being The version 0.0.4 was released on July 4, thanks to the contribution of Fabio Malagas (on Discord):

#Spreadtrum tool v.1.0 released update#

The version 0.0.3 was released on July 3, and was just an important update to implement root access for all devices with Busybox, not just Nokias. On Nokias can be changed Wi-Fi MAC address. IMEI editor also works for MediaTek KaiOS handsets (autodetecting whether it's Qualcomm Nokia or MTK) The version 0.0.2 was released on July 2, 2020, with the following implementations:

#Spreadtrum tool v.1.0 released Bluetooth#

Edit Bluetooth MAC address (Nokia devices only) Edit Wi-Fi MAC address (Nokia and MediaTek devices only, temporary for MediaTeks) Enable developer menu and privileged access (via cache injection method )Ĭall. Run overclocking script (Qualcomm devices only) Toggle diagnostics port (Qualcomm devices only)

#Spreadtrum tool v.1.0 released manual#

Override user agent (dangerous: affects KaiStore accessibility, can't be reset until the factory reset or manual device preferences editing in WebIDE)Ġ. Override TTL when tethering until reboot (Qualcomm devices only)Įdit IMEI1 (Nokia and MediaTek devices only)Įdit IMEI2 (Nokia and MediaTek devices in DSDS configuration only)

#Spreadtrum tool v.1.0 released install#

Install application package ( OmniSD/GerdaPkg compatible, works when developer menu is enabled, tested on Nokias only) Return operation success.ĪDB root (needs Busybox for the operation, you may use OmniBB to install it if missing)Ĭall recording on/auto/off (works on KaiOS 2.5.2 and higher, tested on Nokia 2720 Flip and Nokia 800 Tough) With the help of selected master extension startUniversalCommand method, run the command to move the file (found with the find command within the /storage/self/primary/ tree, because its location might be either /storage/self/primary/tmpbin.bin or /storage/self/primary/0/tmpbin.bin) to the target location. On success, go to the next step, otherwise return operation error. Retreive the storage handle with navigator.getDeviceStorage('sdcard') and try writing the resulting blob to 0/tmpbin.bin file (relative to the B2G storage root, not physical location). If succeeded, go to the next step, if not, return operation error. Shape the XHR with 'application/octet-stream' content type and 'blob' response type to fetch the necessary resource file. Hence, the logic of the loader method is as follows: The only issue is that in some cases (for instance, on 8110 v16 without SD card) the actual storage is mounted onto /storage/self/primary/0but, due to some bug, the root of B2G 'sdcard' storage handle still refers to /storage/self/primary/ itself, so attempts to write to the root result in DOM error. The most interesting part in this app is the ' Resource loader ', that uses the fact that main storage can always be referred to as /storage/self/primary/ in the actual FS tree. Remove leftover folder from primary storage if it's empty. Run the unzip command against the local application package to extract adbd binary to /sbin Īdjust the new /sbin/adbd permissions and start the adbd service again Move the unzip binary from /data/local/tmp/unzip to /sbin/unzip and adjust its permissions (since /sbin structure is volatile until next reboot) With the help of selected master extension startUniversalCommand method, a concatenated command is run to: Resource loader (see below) method is called to fetch 'unzip' binary from the app resources into /data/local/tmp/unzip

#Spreadtrum tool v.1.0 released software#

In fact, it is very likely that some features or even the whole application may not work, for reasons ranging from software features to hardware.įirst fitting master extension is selected depending on the platform (choice is done among engmodeExtension, jrdExtension and kaiosExtension) Read their characteristics carefully, so that you can choose the right application for your KaiOS device. On this page I will try to explain the functioning of the individual apps, focusing more attention on the Wallace project, which contains a real library for the implementation of root privileges and beyond.Īll the applications in our resources will be listed in chronological order, starting from the least powerful (Telnetd) to the most complete (Wallace Toolbox).

These apps can easily be installed using WebIDE or OmniSD.

In KaiOS it's much simpler, as there are applications written in Javascript, HTML and CSS that take advantage of extensions already existing in the system, so as not to interrupt updates. To perform root access on a Linux Embedded device such as Android, we are often forced to use patches in the partitions, in order to add ' busybox ' to /system/bin or to change the permissions directly in the /boot partition.