doc:appunti:hardware:doogee_x93
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
doc:appunti:hardware:doogee_x93 [2022/03/12 15:05] – [Factory Mode] niccolo | doc:appunti:hardware:doogee_x93 [2022/03/16 09:17] – niccolo | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Rooting the Doogee X93 Android Phone ====== | ====== Rooting the Doogee X93 Android Phone ====== | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | | {{: | ||
+ | | {{: | ||
+ | |||
The Doogee X93 smartphone is a cheap Android phone, priced at about 86 € in March 2022. | The Doogee X93 smartphone is a cheap Android phone, priced at about 86 € in March 2022. | ||
Line 82: | Line 92: | ||
adb push boot.img / | adb push boot.img / | ||
</ | </ | ||
+ | |||
+ | FIXME **WARNING**: | ||
Using the phone file manager, install the Magisk app and run it. | Using the phone file manager, install the Magisk app and run it. | ||
Line 149: | Line 161: | ||
{{.: | {{.: | ||
+ | |||
+ | ===== Android Fingerprint ===== | ||
+ | |||
+ | < | ||
+ | ~$ getprop ro.build.fingerprint | ||
+ | DOOGEE/ | ||
+ | </ | ||
+ | |||
+ | ===== Termux:API problems ===== | ||
+ | |||
+ | On this phone I experienced a **[[..: | ||
+ | |||
+ | It seems that some steps in the right way to solve the problem are explained in this **[[https:// | ||
+ | |||
+ | A partial workaround consists basically in installing the **[[https:// | ||
+ | |||
+ | Download the **MagiskHidePropsConf-v6.1.2.zip** file and install it from the Magisk app (Modules=> | ||
+ | |||
+ | From the Termux command line verify that **ro.hct_autostart_manager** and **ro.freeme_freemanager** properties are set to **1**: | ||
+ | |||
+ | < | ||
+ | ~$ getprop ro.hct_autostart_manager | ||
+ | 1 | ||
+ | ~$ getprop ro.freeme_freemanager | ||
+ | 1 | ||
+ | </ | ||
+ | |||
+ | You can also check the **/ | ||
+ | |||
+ | < | ||
+ | ~$ tsu | ||
+ | .../ | ||
+ | /system # grep freeme_freemanager build.prop | ||
+ | ro.freeme_freemanager=1 | ||
+ | /system # grep hct_autostart_manager build.prop | ||
+ | ro.hct_autostart_manager=1 | ||
+ | </ | ||
+ | |||
+ | Using the **props** command line tool (provided by the // | ||
+ | |||
+ | < | ||
+ | tsu | ||
+ | props ro.freeme_freemanager 0 | ||
+ | props ro.hct_autostart_manager 0 | ||
+ | </ | ||
+ | |||
+ | Here it is the interactive output of **props**: | ||
+ | |||
+ | < | ||
+ | MagiskHide Props Config v6.1.2 | ||
+ | by Didgeridoohan @ XDA Developers | ||
+ | |||
+ | ===================================== | ||
+ | | ||
+ | ===================================== | ||
+ | |||
+ | This will set ro.freeme_freemanager to: | ||
+ | |||
+ | 0 | ||
+ | |||
+ | The currently set value is: | ||
+ | 1 | ||
+ | Please enter the new value. | ||
+ | |||
+ | Pick an option below to change | ||
+ | what boot stage the prop will | ||
+ | be set in, or set/reset a delay: | ||
+ | |||
+ | 1 - Default (current) | ||
+ | 2 - post-fs-data | ||
+ | 3 - late_start service | ||
+ | 4 - Both boot stages | ||
+ | d - Delay | ||
+ | |||
+ | Do you want to continue? | ||
+ | |||
+ | Enter y(es) or n(o) | ||
+ | or an option from above: 2 | ||
+ | </ | ||
+ | |||
+ | Once **rebooted**, | ||
+ | |||
+ | < | ||
+ | ~$ getprop ro.hct_autostart_manager | ||
+ | 0 | ||
+ | ~$ getprop ro.freeme_freemanager | ||
+ | 0 | ||
+ | </ | ||
+ | |||
+ | This workaround is not sufficient, you have also to **disable DuraSpeed** at all (with Termux:API only version 0.50.1 it is not possibile to disable it for the app only). **After a reboot** you have to **enable and then disabled DuraSpeed again**. | ||
+ | |||
+ | ===== Termux: | ||
+ | |||
+ | It is not possibile to add the **Termux: | ||
doc/appunti/hardware/doogee_x93.txt · Last modified: 2022/03/16 09:26 by niccolo