Related
Dear XDA,
I have had a Tudou 91 D1 for over a year, and i tried every rooting method. (one click root, srs root, etc) I tried looking for roms but there is little on google about this phone, and nothing on xda. It is a good phone, very happy with it, but no roms. Is there any rom that could be tweaked to work on my phone? I checked about rom porting and creating a new rom via kitchen but all those require a rom for my phone, and a rom i want to change. The problem is i got nothing for my phone.
ALPS Tudou91 D1
quadrant standard review
4.2.1 Jellybean
ID: JOP40D
OS Version:3.4.5
dalvik: 1.6.0
Model:Tudou91 D1
Product/board: ratech89_we_rlk_jb2
ARMv7 Processor rev 2 (v7l)
1.2ghz
4 cores
architecture 7
bogoMIPS:2439.94
MT6589
revision 2
serial: bunch of zeros
total memory:995912 kb
540x960
5'3 in
240 dpi
51.02 fps or refresh rate
PowerVR SGX 544MP
OpenGL ES 2.0
bootloader: unknown (although when i boot into recovery "volume up + power" it shows no command, hold volume down + power, and i get into "Android system recovery <3e>") and its yellow, if that helps lol
http://www.cheapunlockphone.com/?p=1688 <--the phone
if it helps, i extracted launcher apk and it had something like s3 launcher.
Thank you very much!
First off, try to see if the manufacturer provides existing firmware on their website. It would be ideal if you can get that. If there is one, then that would be your backup.
Now the next step towards rooting is to either use z4root or try to inject the root into the stock firmware and then flash it yourself. You may also use this guide to enhance it further.
Now supposing you do not find a Stock firmware by the manufacturer, there is a way to backup the current stock firmware on the phone. At least for most of the phones. Here's a nice Guide on how to do so. I am aware its for a different phone. But it will give you ideas and pointers.
FYI on SRS page they say your phone is supported. So Try These steps
1. Use USBDEVIEW to uninstall any usb devices that look like they may be your phone.
2. Download the Universal Drivers from here http://hexamob.com/drivers-smartphone-tablet/tutorial-universal-adb-driver-koush/
3. Once you have your phone installed with the proper drivers and can access ADB via cmd (if you need adb tool search the forms) download the srsroot and run it.
Like i said in the first line Your Phone is Supported by SRS root. Once you have root back up your phone. Back up your WHOLE phone not just system and data. Everything. Once you have a good backup. start playing. If you just want to use some simple mods install xposed. If you want a custom AOSP rom u will prob have to build it your self.
Have fun!
I will try! i think i messed up somewhere with adb, when i tried srs root. does srs root need adb drivers? if so, then that was my problem.
messed up
Perseus71 said:
First off, try to see if the manufacturer provides existing firmware on their website. It would be ideal if you can get that. If there is one, then that would be your backup.
Now the next step towards rooting is to either use z4root or try to inject the root into the stock firmware and then flash it yourself. You may also use this guide to enhance it further.
Now supposing you do not find a Stock firmware by the manufacturer, there is a way to backup the current stock firmware on the phone. At least for most of the phones. Here's a nice Guide on how to do so. I am aware its for a different phone. But it will give you ideas and pointers.
Click to expand...
Click to collapse
I just tried this method, followed your steps, and srs root results:
10:11:58 AM [+] Testing exploit: root4b (please wait..)
10:12:05 AM [+] Device Reboot #1 (Wait till it's started)
10:13:27 AM [+] Device Reboot #2 (Wait till it's started)
10:14:41 AM [+] Remounting /system Filesystem as R/W..
10:14:41 AM [+] Installing SU Binary...
10:14:41 AM [+] Installing SuperUser APK...
10:14:42 AM [+] Remounting /system Filesystem as R/O..
10:14:48 AM [+] Rooting Complete !
I cant find the superuser app, and i checked with root checker pro if i had root, and it says that the device is not rooted.
root checker pro:
superuser application- is not installed!
SuperSU application- is not installed.
analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
I found the file in system/bin/su but i dont know how to execute it.
also to top things up, when i tried srs root option for gesture lock, it said this
10:33:43 AM - Starting ADB Server..
10:33:48 AM - Manufacturer: alps
10:33:48 AM - Model: Tudou91 D1
10:33:48 AM - Android Version: 4.2.1
10:33:48 AM - Build ID: Tudou91_D1_V1.0
10:33:48 AM - Board ID: ratech89_we_rlk_jb2
10:33:48 AM - Chipset Platform:
Device is not rooted, To use this function you need to root it first...
its messed up
Have you tried the steps I had mentioned ?
Hello,
After looking at your thread we have decided to close it. XDA assist is here to help users learn their way around XDA. It is not here to fix issues for users. Please have a look at the goals of the forum:
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Click to expand...
Click to collapse
As there is no dedicated forum available for your device, the best we can offer is to create a thread in: Upgrading, Modifying and Unlocking section in the general forum. Other users on XDA may be able to help you there. If you can provide as much detail on your device as possible and the steps you have taken so far it will help.
We do hope you can get your issue resolved.
Many thanks,
Ghost
Forum Moderator - XDA Assist forum.
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samitan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
I am looking for the same!
T5 Rom Needed
Hi, i'm looking for the same rom, i miss my phone's imei,
I was able to install the t5 lite Rom, but the NVRAM partition seems to be incompatible.
Thanks
Doogee t5s Stock rom
Please doogee t5s Stock rom link
Not a new ROM, but a step forward. (TWRP & SuperSU)
ethan_hines said:
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samaritan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
Click to expand...
Click to collapse
(Edited: Removed all external links due to my newcomer status)
To be brief:
I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.
I have managed to install a TWRP with SuperSU powers.
These instructions might help you clean up your current system.
Bonus: the recovery menu (TWRP) is multilingual.
Caveat emptor:
My stock ROM came with a nasty couple of Trojans(a) and other potential malware(b) embedded. The Trojans subscribed me to "premium" phone services, costing me some money. I went through the whole hassle in order to get rid of them.
If you have a DOOGEE T5S, your phone is probably infected too. Owners of other DOOGEE phones should beware. (c,d,e)
DISCLAIMER: The following instructions could seriously harm or brick your phone. I make no guarantees of any type, shape or form as to the end results. These operations WILL VOID YOUR WARRANTY.
What I did:
Last warning: during these operations I had to do a factory reset of my phone. I strongly recommend you BACKUP ALL YOUR DATA before you continue.
1] Install TWRP & root the phone (f)
* Download the required files:
- The TWRP image file here:
[Search the NEEROM dot COM website]
- The SuperSU patch file here:
[Search the NEEROM dot COM website]
* Unrar the TWRP image. Leave the SuperSU patch zipped.
* Enter fastboot mode.
Using ADB in terminal:
Code:
adb reboot bootloader
* Flash the TWRP image in the recovery partition.
Code:
fastboot flash recovery /path/to/twrp/image/recovery.img
(in my case fastboot requires root privileges, so sudo it.
* Reboot and enter in recovery mode.
In fasboot send the reboot system, but press Volume UP during reboot.
* Enter into TWRP and Install the patch "SuperSU 2.78-SR1"
Once in TWRP, ADB is again functional.
Load SuperSU patch to your sdcard:
Code:
adb push /path/to/your/patch/SuperSU_Pro_v2.78-SR1.zip /sdcard/
In the TWRP menu, go to "Install". Browse to the "sdcard" directory. Select the SuperSU patch and Install.
* Reboot to the system.
Beware: system will not start if you haven't installed the SuperSU patch. It will loop at startup, and won't progress beyond the startup logo.
2] Initial setup.
From factory reset, the phone will go through the first installation procedures. Follow the setup until your system logs on, and you can connect again to your phone via ADB.
3] Get rid of the malware.
* Disable the apps:
Without need of supercow powers:
- Enter an adb shell:
Code:
adb start-server
Code:
adb shell
Disable the apps:
In a normal ADB shell:
Code:
pm disable your.package.name.here
If you don't know the name of the packages, you can always get the full list with:
In your normal terminal (not adb):
Code:
adb shell 'pm list packages -f'
In an ADB shell:
Code:
pm list packages -f
* Remove the apps:
First try a normal removal. If they are system apps this will fail, but try anyways.
Code:
pm uninstall your.package.name.here
* Escalation to remove apps:
Now that the first try has failed, get supercow powers:
In the ADB shell:
Code:
su
(You should get a message on your phone telling you that ADB is requiring root privileges. Say OK)
Now your ADB console should read something like "[email protected]"
And we try again:
Code:
pm uninstall your.package.name.here
But we have a super hardcore app that fails to be removed with the normal supercow powers. So we step it up. (g)
Code:
pm uninstall -k --user 0 your.package.name.here
... SUCCESS!
But wait, the app is still there. Yes, you only removed it for root. So... lets do some overkilling:
Meanwhile:
Let's check the ID of the system user:
Code:
id system
In my phone "system" is 1000
So, here we go:
Code:
pm uninstall -k --user 1000 your.package.name.here
Your mileage may vary. Sometimes the first command does the trick, sometimes the app is still there.
Is it gone? Not always.
Can it creep out from the netherworld? Maybe. So, let's beat the dead horse.
* Silence the dead (h)
Just in case the app is still lurking, let's make it harder for it to creep up on us.
Code:
pm hide your.package.name.here
Great. Silent in its coffin.
But is the app still there? Sadly, yes. I looked around and the apps were still there, in a privilege data folder.
* Root it out (i)
This is an extreme measure. You can really harm yourself doing this, so... you have been warned.
At this stage, you should be using supercow powers. If you are not, brief recap:
Code:
adb shell
su
Now, the systems partition is read only, so you cannot remove the content there. So, to remove the files there, you have to remount it in read-write mode. Here we go:
Code:
mount -o rw,remount /system
Now, find the app directories you want to remove. In my case, the apps were in "/system/priv-app". So:
Code:
rm -rf /system/priv-app/YourAppFolder/
And, eventually, erase the associated data:
Code:
rm -rf /data/data/your.package.name.here
A read-write /system/ partition is not a good idea, so we reset as read-only:
Code:
mount -o ro,remount /system
[You might need this]
I don't remember if this is required. Maybe to be able to write to the recovery partition via fastboot...
Code:
adb shell setprop ro.secure 0
This voids the GUARANTEE. You have been warned (AGAIN).
----
(a) Found Trojan.Hiddad & Adware.Retsanvie. Probable carrier app: com.gangyun.beautysnap (aka com.android.snap).
(b) Antivirus programs tag the OTA program as potentially dangerous: com.fota.wirelessupdate
(c) [Some articles on DOOGEE and LEAGOO shipped with Trojans]
(d) [Some articles on DOOGEE and LEAGOO shipped with Trojans]
(e) [Some articles on DOOGEE and LEAGOO shipped with Trojans]
(f) [NEEDROM dot COM website]
(g) [ROMPROVIDER dot COM website]
(h) [Reddit Post]
(i) [ANDROID dot STACKEXCHANGE dot COM Post]
rrm. said:
(Edited: Removed all external links due to my newcomer status)
To be brief:
I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.
I have managed to install a TWRP with SuperSU powers.
These instructions might help you clean up your current system.
Bonus: the recovery menu (TWRP) is multilingual.
I am amazed you were able to do as much as you did with just ADB! Usually this type of phone (ChinaPhone) requires flashing the bootrom with a utility called SP Flash Tool and , VCOM Drivers as well as the aforementioned Scatter file! BTW There is a rom for the T5S LITE but not T5S (Despite many many requests, falling on deaf ears)
Click to expand...
Click to collapse
ethan_hines said:
rrm. said:
(Edited: Removed all external links due to my newcomer status)
To be brief:
I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.
I have managed to install a TWRP with SuperSU powers.
These instructions might help you clean up your current system.
Bonus: the recovery menu (TWRP) is multilingual.
I am amazed you were able to do as much as you did with just ADB! Usually this type of phone (ChinaPhone) requires flashing the bootrom with a utility called SP Flash Tool and , VCOM Drivers as well as the aforementioned Scatter file! BTW There is a rom for the T5S LITE but not T5S (Despite many many requests, falling on deaf ears)
Click to expand...
Click to collapse
Yes, I did notice the lack of help regarding the release of the stock ROM. Given that (in my case) it was a compromised ROM (Trojans & Co.), I would imagine why they would not release the original one. It surprises me they are not releasing a cleaned up version, though.
The TWRP for the T6 works fine on the T5S. I was tempted to try one of the custom roms for T6 pro available at needrom DOT com. The thing is I need a working phone, so I cannot hard or soft brick my T5S. Not having a fallback ROM, that kind of nails it down for now.
I'm deploying LineageOS on a series of other devices. If all goes well, I might give LineageOS for T6 pro a try on my T5S. My concern is not the chipset of the SOB, it's the periphericals. Chiefly the capacity to recognize the SIM cards. It would defeat the purpose to have a running Android Nougat on my phone and not be able to make calls.
Click to expand...
Click to collapse
Replacement stock ROM: use the T5 lite stock ROM
ethan_hines said:
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samitan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
Click to expand...
Click to collapse
UPDATE:
Previously described to have successfully flashed TWRP 3.0.3 from needrom, with root powers, allowing for housekeeping of the original ROM.
I now inform you to have successfully flashed the T5 Lite stock rom (the UPDATE) into the T5S.
The ROM is apparently fully functional: RadioFM, front camera, back camera, WiFi, SIMs. I have not found any non-functioning feature.
I have tried to flash in a custom ROM, but until now I have been unsuccessful. While flashing the ROM with TWRP I get a 255 error. I'm thinking I need TWRP 3.1 or 3.2 to flash the custom ROMs I have. Sadly, there doesn't seem to be a TWRP 3.2 for the DOOGEE T5 lite/T5S.
I'll keep you all posted.
Need SuperSU
Is anyone here who can send me the "SuperSU_Pro_v2.78-SR1.zip"
PLEASEEEE don't send me the needrom link. Thanks!
ethan_hines said:
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samitan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
Click to expand...
Click to collapse
Finally the T5S firm is available at doogee.cc comunity!
I had to use it to revive my T5S after trying to flash TWRP recovery: I tried TWRP from T5, T6 and T6 Pro but in all cases phone got stuck in a boot loop. :crying:
I don't know if the official firmware contains bloatware... I'll keep any eye on it...
Doogee T5S rooten
After some time consuming experiments, I finally got my T5S rooted.
The main point after installing TWRP, througth fastboot or SP-Flash tool is:
1st: Booting immediatly into the recovery mode (prevents the operating system to switch to the original recovery app)
2nd: installing Super-SU before booting in the system (I my case it prevents the boot-loop. I think a must!)
When you finally restarted successfully the operating system, deactivate the APP "Aktualisierung mit Funknetz" (in englisch I think something like "OTA WiFi upgrade") , which seems to be reason for the malware. I my case, since I did it, no pop ad's appeared! (since 3weeks)
Remark:
As the T5S has the some CPU as T5light you can flash this firmware as well. I did it with the SP-tool but with same problem of poping up of unwished AD's, i.e. you have to root to put the above mention APP in deactivat mode (I did it with the app: 3C System Tuner Pro).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Software root method for MediaTek MT67xx, MT816x, and MT817x!
So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I created, MTK-SU, was originally aimed at helping Amazon Fire HD owners to easily root and unlock their tablets. (Without it, most models need a hardware mod to achieve root & unlock. This tool made rooting accessible to many times the number of owners. It also made possible to root the Fire TV gen 2.) But funny story: this method actually works on virtually all of MediaTek's 64-bit chips. Many devices of various vendors have already been confirmed.
So in case it's not clear, what mtk-su does is give you a root shell to do with as you please. It's like running 'su', but without the need to have su installed. That may be a holy grail for locked devices. On some devices, it may be possible to install a root manager for permanent root using mtk-su as a springboard.
The original thread is here: Rapid Temporary Root for HD 8 & HD 10. It's a great resource for info. But please avoid posting there about non-Amazon devices. This new thread is a catchall topic for other devices and vendors.
DISCLAIMERAnything you do that is described in this thread is at your own risk. No one else is responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software. There is a nonzero chance of any of these events happening as a result of using the tools or methods here.
REQUIREMENTSMastery of the Thanks button under XDA posts
A phone or tablet based on Mediatek MT67xx, MT816x, MT817x or MT6580 chipsets
Either:
A PC with ADB installed to interact with your device, or
A terminal emulator app
Familiarity with ADB (if using PC) and basic Linux shell commands
You agree to post the model name of any unconfirmed device which ran mtk-su successfully
INSTRUCTIONS FOR ADB
Make sure you meet all the requirements listed above, especially the first and last ones.
Download the current mtk-su zip file to your PC and unzip it. Inside will be 2 directories: 'arm' & 'arm64' with an 'mtk-su' binary in each. Pick one for your device. Differences between the flavors:
arm64: 64-bit kernel and userspace
arm: 32-bit userspace on a 64-bit or 32-bit kernel (will also work in 64-bit userspace)
Connect your device to ADB and push mtk-su to your /data/local/tmp folder
adb push path/to/mtk-su /data/local/tmp/
Open an adb shell
adb shell
Change to your tmp directory
cd /data/local/tmp
Add executable permissions to the binary
chmod 755 mtk-su
At this point keep your device screen on and don't let it go to sleep. Run the command
./mtk-su
It should only take a second or two. If the program gets stuck for more than a few seconds and your device is awake, press Ctrl+C to close it.
The -v option turns on verbose printing, which is necessary for me to debug any problems.
The output of ./mtk-su -v is similar to this:
Spoiler
Code:
$ ./mtk-su -v
param1: 0x3000, param2: 0x18040, type: 2
Building symbol table
kallsyms_addresses pa 0x40bdd500
kallsyms_num_syms 70337, addr_count 70337
kallsyms_names pa 0x40c66d00, size 862960
kallsyms_markers pa 0x40d39800
kallsyms_token_table pa 0x40d3a100
kallsyms_token_index pa 0x40d3a500
Patching credentials
Parsing current_is_single_threaded
ffffffc000354868+50: ADRP x0, 0xffffffc000fa2000
ffffffc000354868+54: ADD xd, x0, 2592
init_task VA: 0xffffffc000fa2a20
Potential list_head tasks at offset 0x340
comm swapper/0 at offset 0x5c0
Found own task_struct at node 1
cred VA: 0xffffffc0358ac0c0
Parsing avc_denied
ffffffc0002f13bc+24: ADRP x0, 0xffffffc001113000
ffffffc0002f13bc+28: LDR [x0, 404]
selinux_enforcing VA: 0xffffffc001113194
Setting selinux_enforcing
Switched selinux to permissive
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
#
Some other options:
mtk-su -c <command>: Runs <command> as root. Default command is /system/bin/sh.mtk-su -s: Prints the kernel symbol tablemtk-su -Z <context>: Runs shell in a new selinux context. Example: ./mtk-su -Z u:r:logd:s0If you see any errors other than about unsupported or incompatible platform or don't get a root shell, report it here. When reporting a problem with a device, please post a link to the firmware and/or the kernel sources.
Please post the model of any device that works with mtk-su that's not already confirmed.
Important: in rare cases, it may be necessary to run the tool multiple times before you hit UID 0 and get selinux permissive. If you don't achieve root on a particular run, the "UID: N cap: xxxxx...." line will reflect that. If it doesn't say "UID: 0 cap: 3fffffffff selinux: permissive", type exit to close the subshell and try mtk-su again.
WARNING If you have a device with Android 6 or higher, it likely has dm-verity enabled. On such a device one does not simply remount the system partition as read/write. The remount command will probably fail. But if you succeed in forcing it somehow it will trigger dm-verity, which will result in a very bad day. Your device will become inoperable until you restore the stock system partition.
DOWNLOADCurrent Version
Release 23
Spoiler: Changelog
Release 23 - August 24, 2020
Add support for some early Linux 3.10 tablet firmware
Add support for kernels with some debug features enabled
Release 22 - May 8, 2020
Expand kernel support
Enable seccomp handling for Android 8
Release 21 - March 14, 2020
Add support for more devices
Fix seccomp on 3.18 arm kernels
Release 20 - Dec 28, 2019
Add support for MT6580
Add support for some MT8183 versions
Fix handling of some 32-bit 4.x kernels with stack protection
Move to NDK build
Release 19 - October 20, 2019
Add -Z option for setting custom selinux context
Fix seccomp on armv7
Fix seccomp handling on late-revision 3.18 kernels
Improve error printing for critical failures
Strip supplementary groups in root shell
Do not spawn root shell on critical failures
Release 18 - July 29, 2019
Add support for kernel address space layout randomization (KASLR)
Change status output format
Release 17 - July 13, 2019
Fix missing capabilities under adb shell in Android 9.x
Disable seccomp in app mode of Android 9.x
Add support for MT6771 on Android 8.x
Reliability improvements
Release 16 - June 9, 2019
Add support for 32 & 64-bit kernels compiled with CONFIG_KALLSYMS_BASE_RELATIVE
Add support for MT676x on Android 7.x
Speedups
Release 15 - May 29, 2019
Run shell/command in global mount namespace -- mounting from apps is now visible to the whole system
Release 14 - May 22, 2019
Remove restriction for adb shell initial run on Android 8.0+
Add support for 32-bit kernels compiled under Android 8.0+
Add initial support for MT6771 on Android 9+
Minor bug fixes
Release 13 - May 16, 2019
Improve stack protection detection -- add support for some armv7-kernel 3.x phones
Release 12 - April 26, 2019
Unify the arm and armv7-kernel binaries into one
Support Linux 4.9.x
Improve speed and possibly reliability
Fix arm64 support for phones on kernel 3.10.65
Fix stack protection workaround for armv7 kernels
Update readme file
Release 11 - April 10, 2019
Fix up and enable rooting for 32-bit kernels -- first such device confirmed (thanks @anthonykb)
Improve criteria for detecting strong stack protection
Release 10 - April 7, 2019
Fix support for the latest Oreo devices
Add compatibility for kernels with stack protection (Nokia phones)
Improve reliability
Initial support for 32-bit (armv7) kernels -- needs testing
Release 9 - April 1, 2019
Confirmed support for at least some Oreo devices
Fix bugs with R8
Release 8 - March 30, 2019 (REMOVED)
Lay the groundwork for Oreo devices
Improve performance
Improve reliability
Release 7 - March 17, 2019
Add/fix support for many Linux ver. ≤ 3.18.22 devices
Fix arm binary on Fire HD 10
Release 6 - March 13, 2019
Add support for some devices with kernel 4.4.x (MT8167 confirmed by @cybersaga)
Minor bug fixes
Release 5 - March 7, 2019
Support kernels with CONFIG_KALLSYMS_ALL disabled
Improve reliability
Release 4 - March 4, 2019
Improve compatibility with phones
Support Fire TV 2 new FW
Minor bug fixes
Improve reliability
Release 3 - March 1, 2019
Add support for HD 10 7th gen
Add support for 3.10 kernel layout
Add possible support for MT67xx phones
Improve reliability
Release 2 - Feb. 27, 2019
Add support for HD 8 8th gen and 32-bit only user stacks
FAQI got the error, "This firmware cannot be supported". What's up with that?
This means that your device's firmware is not prone to the mechanism used by mtk-su. It may be a new device or it may have started from a firmware update. It will not be feasible to add root support for the current or future firmware versions. Check the last supported firmware version in post 4. If the last working FW is not listed and your device used to work with mtk-su, please report the last working version and/or your current version. In those cases, it may be possible to get mtk-su support by downgrading the firmware.
I got the error, "Firmware support not implemented". What gives?
That means that mtk-su does not recognize the type of firmware on your device. While It's technically possible to add basic detection, most of the time this error happens on devices that have already blocked mtk-su access. So implementing it would only kick the can down the road and probably lead to a, "This firmware cannot be supported" message (see above). If your device has Android 10+ or a security patch level at 03-2020 or higher, or if your firmware is newer than the last compatible version in post 4, there is no need to report this error.
Will this work on my phone?
Yes, it will work on your phone, unless it doesn't. But to be serious, there is no point in asking this question. If you have the device in hand, it is much quicker to just try out the above procedure than to wait for a response. You are usually the best person to answer that question. If your device is listed among the confirmed models or, to a lesser extent, your chipset is supported, that's a good indication that mtk-su will succeed, but that is not guaranteed. You should report your success or failure in this thread, along with the requested materials if it fails.
Why don't you reply to my post?
I read every post in this thread, and respond to practically every post that warrants a response. Sometimes I will only click a Thanks as an acknowledgement. The reasons I may not answer your question are:
It has already been answered in the FAQ or multiple times in the thread.
Your post is unrelated to this project. It may be specific to your device, which would make it off topic for this thread.
Your question is extremely vague and you appear to be intentionally leaving out basic information (e.g. fishing).
After getting a root shell I'm still getting 'permission denied' errors. WTH?
It may be that selinux is still being enforced. Having root with selinux enabled somehow ends up being more restrictive than a normal shell user. First, check that mtk-su succeeded in setting selinux to permissive by running getenforce. If it says Enforcing, then exit your shell and run mtk-su again.
Will this work on an MT65xx or MT8127?
There is no support for most 32-bit chips. But there may be a couple where it's possible.
Does this thing unlock the bootloader?
No, it does nothing to unlock the bootloader.
I ran mtk-su successfully, but my apps still don't have root permissions.
Mtk-su does not give apps root permissions. It is not a permanent root solution in and of itself. It opens a command shell that has root and administrative capabilities within the context of that shell. It's up to you what you want to do with it. But also, there is a way to load Magisk using this tool without the need to unlock your bootloader. Just follow this guide.
How does this tool work?
It overwrites the process credentials & capabilities in the kernel in order to gain privileges. It also turns off selinux enforcement by overwriting the kernel's selinux_enforcing variable. As for how it accesses that memory, the tool involves making use of the vulnerability known as CVE-2020-0069.
Can I include mtk-su in my app or meta-tool?
Generally speaking, you may not distribute any mtk-su zip or binaries with your software. That includes doing any automatic download of those files into your app. You can still use it with your tools. But you should ask your users to visit this thread and download the current release zip themselves. No apps have been permitted to bundle or auto-download mtk-su.
CREDITS
Thank you to everyone who has tested and provided feedback to help me add support for the large variety of MTK-based devices out there. There are simply too many people to list.
MediaTek, Inc., who leave holes and backdoors in their OS to make software like this possible :good:
Thank you to everyone who has donated. You're the best!
INSTRUCTIONS FOR TERMINAL APPYou can optionally run mtk-su on a terminal emulator such as Terminal Emulator for Android (recommended) or Termux. The basic idea is to copy the executable to the terminal app's internal directory and run it from there. These are the instructions for Termux, but a similar procedure applies to all terminal shell apps.
Make sure you meet all the requirements from the first post, especially the first and last ones.
Download the current mtk_su zip to your device and unzip it. Take note of where you extracted it. Pick the variant that fits your device. (See above.)
Open Termux and copy the mtk-su binary to its home directory, which in this case is the shell's initial working directory.
General idea: cp path/to/mtk-su ./
For example,
cp /sdcard/mtk-su_r14/arm64/mtk-su ./
For this to work, you have to enable the Storage permission for your term app. Do not try to circumvent the cp command with clever copying methods involving file managers or external tools. Mtk-su will not get the right permissions that way.
Make file executable
chmod 700 mtk-su
Run the program
./mtk-su
If mtk-su fails, post the output of ./mtk-su -v here along with a link to firmware and/or kernel sources, if possible.
Note that for most terminal shell apps, the internal app directory is stored in the variable $HOME. So in general you would do
cd
cp path/to/mtk-su ./
chmod 700 mtk-su
./mtk-su
PROJECTS USING THIS TEMP ROOT
Partition Backup Helper for Termux by @mrmazak
Creates a script that automatically backs up your device's partitions, which may come in handy for repairs or experimenting.
Full bootless root with Magisk (for 20.x to 21.4) by @diplomatic
Loads Magisk without modifying the firmware.
Full bootless root with Magisk for 22.x+ by @HemanthJabalpuri
Loads the latest Magisk version without modifying the firmware.
Status
NOTE: Any firmware update released after March, 2020 is bound to block this temp root. Think twice before updating your device if you would like to keep using mtk-su.
Confirmed Devices
Acer Iconia One 10 B3-A30/B3-A40/B3-A50 series
Acer Iconia One 8 B1-860 series
Acer Iconia Talk S
Alba tablet series
Alcatel 1 5033 series
Alcatel 1C
Alcatel 3L (2018) 5034 series
Alcatel 3T 8
Alcatel A5 LED 5085 series
Alcatel A30 5049 series
Alcatel Idol 5
Alcatel/TCL A1 A501DL
Alcatel/TCL LX A502DL
Alcatel Tetra 5041C
Alcatel U5 / Orange Rise 52
Alldocube iPlay10 Pro
Alldocube iPlay8
Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only
Amazon Fire HD 8 2016 -- up to Fire OS 5.3.6.4 build 626533320
Amazon Fire HD 8 2017 -- up to Fire OS 5.6.4.0 build 636558520 only
Amazon Fire HD 8 2018 -- up to Fire OS 6.3.0.1 only
Amazon Fire HD 10 2017 -- up to Fire OS 5.6.4.0 build 636558520 only
Amazon Fire HD 10 2019 -- up to Fire OS 7.3.1.0 only
Amazon Fire TV 2 -- up to Fire OS 5.2.6.9 only
ANRY S20
ASUS ZenFone 3 Max ZC520TL
ASUS ZenFone Max Plus X018D
ASUS ZenPad 3s 10 Z500M
ASUS ZenPad Z3xxM(F) MT8163-based series
Barnes & Noble NOOK Tablet 7" BNTV450 & BNTV460
Barnes & Noble NOOK Tablet 10.1" BNTV650
Blackview A8 Max
Blackview BV9600 Pro (Helio P60)
BLU Life Max
BLU Life One X
BLU R1 series
BLU R2 LTE
BLU S1
BLU Tank Xtreme Pro
BLU Vivo 8L
BLU Vivo XI
BLU Vivo XL4
Bluboo S8
BQ Aquaris M4.5
BQ Aquaris M8
CAT S41
Coolpad Cool Play 8 Lite
Coolpad Legacy S(R)
Cubot Power
Doogee X70
Dragon Touch K10
Echo Feeling
Evercoss Genpro X Pro S50
Gionee F103 Pro
Gionee M7
Gionee S9
HiSense Infinity H12 Lite
HTC Desire 12
HomTom HT20
Huawei GR3 series
Huawei Y5II
Huawei Y6II MT6735 series
ION Gravity
Lava Iris 88S
Lenovo A5
Lenovo C2 series
Lenovo Tab E7
Lenovo Tab E8
Lenovo Tab2 A10-70F
Lenovo Tab3 10
Lenovo Vibe K5 Note
LG K8+ (2018) X210ULMA (MTK)
LG K10--K430 series
LG K10 (2017)
LG K50
LG Q7 (MTK)
LG Stylo 4 (MTK) -- up to Q710AL11k
LG Tribute Dynasty
LG X power 2/M320 series (MTK)
LG Xpression Plus 2/Harmony 3/K40 LMX420 series
Lumigon T3
Meizu M5c
Meizu M6
Meizu Pro 7 Plus
Motorola Moto C series
Motorola Moto E3 series (MTK)
Motorola Moto E4 series (MTK)
Nokia 1
Nokia 1 Plus
Nokia 3
Nokia 3.1
Nokia 3.1 Plus
Nokia 5.1
Nokia 5.1 Plus/X5
Odys PACE 10 (MT8163)
Onn 7" Android tablet
Onn 8" & 10" tablet series (MT8163) -- up to 10/2019 FW only
Oppo A59 series
Oppo A5s -- up to A.30 only
Oppo A7x -- up to Android 8.x
Oppo F5 series/A73 -- up to A.39
Oppo F7 series -- Android 8.x only
Oppo F9 series -- Android 8.x only
Oppo R9xm series
Oukitel K6
Oukitel K9
Oukitel K12
Oukitel U18
Philips E518
Protruly D7
RCA Voyager III - RCT6973W43MDN
Realme 1
Realme 3
Snopow M10 series
Sony Xperia C4
Sony Xperia C5 series
Sony Xperia L1
Sony Xperia L3
Sony Xperia M5 series
Sony Xperia XA series
Sony Xperia XA1 series
Southern Telecom Smartab ST1009X (MT8167)
Teclast M30
TECNO Spark 3 series
Umidigi F1 series
Umidigi Power
Verizon Ellipsis 10 HD QTAXIA1
Vernee Mix 2
Wiko Ride
Wiko Sunny
Wiko View3
Xiaomi Redmi 6/6A series
ZTE Blade 10 Prime
ZTE Blade A530
ZTE Blade A7 Prime
ZTE Blade D6/V6
ZTE Blade V8 Lite
ZTE Quest 5 Z3351S
ZTE Voyage 4S/Blade A611/Blade A610
Support Problematic*
Most/all Vivo phones
Most/all Huawei/Honor models with Android 8+
Most Oppo phones in app mode
Oppo F11 -- up to CPH1911EX_11_A.22 only
Most/all Samsung MTK-based phones
Supported Chipsets
Including, but not limited to: MT6735, MT6737, MT6738, MT6739, MT6750, MT6752, MT6753, MT6755, MT6757, MT6758, MT6761, MT6762, MT6763, MT6765, MT6771, MT6779, MT6795, MT6797, MT6799, MT8163, MT8167, MT8173, MT8176, MT8183, MT6580, MT6595
* These devices typically use kernel modifications to deter root access via exploits. But this temp root method can still attain root on most of these models in theory. However, I will not be adding support for such non-standard kernels in the main release versions. A tailored version of mtk-su can be made to handle a protected kernel in a specific firmware. This is not something I'm usually motivated to do. But it's possible to make such a version if you can somehow encourage me.
Re-re-reserved
Great work mate!! I would liked to of kept secret till I got myself a new Sony L3 and backup the ta thought.
:laugh:
:highfive:
LOL... thanks!
Don't worry man, no one reads this forum
Great work. Having used both a hardware root method and this method on a pair of devices I have, mtk-su was waaaaaaay easier to work with. Big thanks!
looks great ...i want to try it on a Vodafone carrier branded mtk67__ device in Spain / Europe to see what happens ...
ultimately i would want to use su to pull a copy of stock recovery to sd card / that and boot partition.img
what about after pulling stock recovery & porting twrp i flash twrp with flashfire or similar and after booting directly to recovery flash dm-verity disable .zip ...
reason being that bootloader is locked and this device is on marshmallow ...
*so my question is ...
will mounting rw on marshmallow trip dm-verity immediately and bootloop instantly or only on reboot ...if it's on reboot it would serve my purpose ..
* next question is if im running as su in shell how will I "give" escalated privileges to third party apk like flashfire for example or is it possible to disable dm-verity from root shell using commands ?
or installing mixplorer with root privileges for examle ..
KevMetal said:
looks great ...i want to try it on a Vodafone carrier branded mtk67__ device in Spain / Europe to see what happens ...
ultimately i would want to use su to pull a copy of stock recovery to sd card / that and boot partition.img
what about after pulling stock recovery & porting twrp i flash twrp with flashfire or similar and after booting directly to recovery flash dm-verity disable .zip ...
reason being that bootloader is locked and this device is on marshmallow ...
*so my question is ...
will mounting rw on marshmallow trip dm-verity immediately and bootloop instantly or only on reboot ...if it's on reboot it would serve my purpose ..
* next question is if im running as su in shell how will I "give" escalated privileges to third party apk like flashfire for example or is it possible to disable dm-verity from root shell using commands ?
or installing mixplorer with root privileges for examle ..
Click to expand...
Click to collapse
@diplomatic made a good outline of the the steps to "jump" into full root. At least until rebooted.
I will add the link to the post, but keep the discussion that follows , here in this thread
*Copied from post https://forum.xda-developers.com/showpost.php?p=79348378&postcount=569
diplomatic said:
For advanced users or devs: here's a general overview for a method to get root with Magisk without having to modify your boot image.
Get a Magisk zip file and extract the magiskinit binary. Push magiskinit to your device.
Extract the magisk binary from magiskinit with ./magiskinit -x magisk
Make a symbolic link to (or a copy of) magiskinit and call it magiskpolicy.
Make a symbolic link to (or a copy of) magisk and call it su.
Make a small ext4 image of about 2 to 4MB (using something like make_ext4fs -J -l 2MB). In it, place Magisk's magisk and su binaries. The su binary could be either a link to magisk or a copy of it. (Idea borrowed from @k4y0z's unlock method.)
Get a root shell with mtk-su
Patch the running sepolicy with a magisk context using ./magiskpolicy --live --magisk 'allow magisk * * *' .
Start a temporary Magisk daemon with ./magisk --daemon
Start a temporary Magisk root shell with ./su. This may involve prompts from Magisk Manager.
Check to make sure the new root shell has the context u:r:magisk:s0. Don't proceed if it's not that context.
From the magisk context shell, mount the ext4 image to /system/xbin with
losetup /dev/block/loop0 magisk.img
mount /dev/block/loop0 /system/xbinYou may be able to combine those 2 commands into one, but I wasn't able to on my device.
Kill the temporary magisk daemon with killall magiskd. The point of this is to launch a new daemon from within the magisk se-context. Otherwise there will be problems with selinux.
Start a new daemon with magisk --daemon. Notice that there's no ./ at the start. This is to test the loopback img.
Exit the temporary ./su shell. You may get an error message, but that's fine. At this point you should be back to the mtk-su shell.
Exit the mtk-su shell.
Check if su works. You should get a prompt from Magisk Manager.
At this point, if you get a normal root shell, you can do setenforce 1.
Now all apps that want su access will have it with proper prompting.
Have some app execute steps 6 through 17 at every startup.
Steps 1-5 are done once. Step 6 onward are done at every boot session. A script would probably help. I'm sure this is missing some details, but I just wanted to convey the general idea.
EDIT: If you get this system up and running, you of course want to avoid updating Magisk binaries through MM. That's pretty important because doing so will probably stop your device from booting.
Click to expand...
Click to collapse
KevMetal said:
looks great ...i want to try it on a Vodafone carrier branded mtk67__ device in Spain / Europe to see what happens ...
ultimately i would want to use su to pull a copy of stock recovery to sd card / that and boot partition.img
what about after pulling stock recovery & porting twrp i flash twrp with flashfire or similar and after booting directly to recovery flash dm-verity disable .zip ...
reason being that bootloader is locked and this device is on marshmallow ...
*so my question is ...
will mounting rw on marshmallow trip dm-verity immediately and bootloop instantly or only on reboot ...if it's on reboot it would serve my purpose ..
* next question is if im running as su in shell how will I "give" escalated privileges to third party apk like flashfire for example or is it possible to disable dm-verity from root shell using commands ?
or installing mixplorer with root privileges for examle ..
Click to expand...
Click to collapse
Cool... let us know the results of running mtk-su on that phone, as well as the full model name so I can list it.
So you're on the right track about installing permanent root. I was pretty vague about it in the OP because it's a complex topic and it's pretty risky territory. Before trying to mod your boot image with systemless root and/or verity disabled, you have to check how restrictive your BL is. It's very possible that it can accept self-signed or unsigned images without needing to unlock. You can check this in a minesweeper fashion by flashing your stock recovery with the OEM signature removed and see if it boots. If not, Android will restore the stock recovery automatically, no harm done.
If you want to flash partitions from a root shell, you can use the dd command. FlashFire is a glorified dd flasher. For example, to flash a recovery image you would do
dd if=recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery
The exact path of the dev node varies by device. You should do more research about it if you're interested. To dump partitions, essentially do the reverse of if= and of=.
If you want, you can post your stock recovery image and I can modify it so you can test how restrictive your BL is. There's no need to jump ahead to TWRP yet.
diplomatic said:
If you want, you can post your stock recovery image and I can modify it so you can test how restrictive your BL is. There's no need to jump ahead to TWRP yet.
Click to expand...
Click to collapse
Most MTK's allow the boot probably due to difficulties during OTA patches indeed a lot of the OEM OTA's I have seen actually flash the recovery.img to the boot partition first then reboot do the update flash the recovery to recovery partition then reboot to recovery do the final check then reflash the boot.img back to the boot partition.
I think this is so if the OTA fails at any point they are always in recovery mode. If any of that makes sense :laugh:
Some mtk fstab's I have seen even have a flag that states verify "recoveryonly" so you can flash a TWRP recovery.img to the boot and it will boot up but it will not if flashed to the recovery of course OEM's may have other ideas and implementations so caution and a way back are definitely needed.
It's definitely a game of Russian roulette with a one in six chance of you finding the loaded chamber.
Been too secure can backfire on OEM's and cost them as with the Amazon Fire Phone I brick 3 or 4 of those suckers trying to unlock it and even they could do nothing with them so they would just give me a new one and I am convinced they actually locked themselves out on that devices and that's why it never got a version update or bootloader unlock which is a shame because it was a good phone. :silly:
bigrammy said:
Most MTK's allow the boot probably due to difficulties during OTA patches
Click to expand...
Click to collapse
OK, but I don't see how any of this would prevent cryptographic signature checking and enforcement at any OTA installation stage. Do you have any reason to believe that most devices that are not unlockable have support for unsigned images?
diplomatic said:
OK, but I don't see how any of this would prevent cryptographic signature checking and enforcement at any OTA installation stage. Do you have any reason to believe that most devices that are not unlockable have support for unsigned images?
Click to expand...
Click to collapse
Depends on oem I guess eg: Lenovo TAB2 never unlock the bootloader, Infocus Never unlocked the bootloader, All China brands various I never unlocked the bootloaders yet all rooted with custom recovery's installed although most of these were Android 6.0 so AVB used by Magisk SuperSU etc works for them.
Nokia3 I did unlock the bootloader but I beginning to think maybe I didn't need to and maybe I can test that theory soon when I get one back I loaned out.
Big brands like Sony Defo need to be unlocked but lessor brands I am not so sure about.
OK, good to know, @bigrammy
diplomatic said:
OK, good to know, @bigrammy
Click to expand...
Click to collapse
I might try flash the boot of my Sony XA1 (bootloader locked) with a TWRP recovery over the weekend and see what happens. It just means me having to boot windows to recover it if it fails and I have not done that in 18 months or more :laugh:
EDIT: Unsigned TWRP Failed to boot so now I will try with a AVB signed image and see what happens.
EDIT 2: AVB signed TWRP Failed verification check too. :laugh:
PS: Never unlocked the Lumigon T3 (my daily driver) either and that was marketed a secure device it took me about 30 min's to to make a scatter file then pull the boot with SPFlashTool ported over TWRP from my Infocus pre patched the boot with Magisk flashed them back done. Again it seems AVB sig was enough for this device too but again Android 6.0. :laugh:
OK.... it would be interesting what happens with the Sony...
It's pretty much the same deal with the Asus Zenpad series. The Z3xxM series, based on MT8163, can be flashed without unlocking the BL. On the old Android 6 FW, you needed to have an AVB signature for it go through. On Android 7, you don't even need that. However, for the high-end MT8176-based Zenpad Z500M, they locked it down so that you'd need to unlock before installing a custom boot/recovery--OEM sig support only.
bigrammy said:
EDIT: Unsigned TWRP Failed to boot so now I will try with a AVB signed image and see what happens.
EDIT 2: AVB signed TWRP Failed verification check too. :laugh:
Click to expand...
Click to collapse
LOL... I guess I'll have to stick to unlocking my Sonys before installing root.
I have a question
I have been looking ways to root redmi 6a. Xiaomi have been imposing 15d grace period one any request to unlock boot loader. Very annoyed
My question is if I manage to root it and install TWRP. can I still modify the boot loader without unlocking it?
Tia
Sent from my Redmi 6A using Tapatalk
Hi, @ahhl
If you can install and boot TWRP without unlocking the bootloader, you can almost definitely install permanent root to a boot image. The question is whether the locked BL on that phone will boot an image that is unsigned or wipe out instead. This is what bigrammy and I were just talking about above. I'd love to know if mtk-su works on that phone, btw....
i will try. but i am just novice?. i read thru the conversation between you and bigrammy, only to 30% goes thru my head?
if i manage run mtk-su, then flash twrp, if the flashing did not work, it will just reboot back using stock boot.? i do not have to worry something i need to do just like bigrammy did for 30min, just to get the phone running? as the reboot just wipe twrp? is this true?
Curious if anyone has any experience good or bad about rooting these two tablets, if you have I'd love the method!
I haven't seen any methods, conversations, twrp for the iPlay 50 or the Blackview Tab15.
I understand these are not mainstream tablets and won't receive mainstream attention however I can always hope. A tablet like this suits my wanted specs and budget.
thanks
If the Linux kernel of both tablets mentioned is version 5.10 or higher then you can root via KernelSU: KernelSU is working in Linux kernel mode, it has more control over userspace applications. Only App that is granted root permission can access `su`, other apps cannot perceive su. KernelSU supports.
See also here:
KernelSU reborn: Developer ports kernel-assisted root access to GKI compatible devices
A Magisk successor at last?
www.xda-developers.com
Very interesting. I'll research and post an update.
In downloading a terminal emulator and using the command uname -a I've got the following.
ALLDOCUBE iPlay 505.4.161Blackview Tab154.19.191
ah well
I've looked and found a reference to an earlier tablet model an iPlay 40 where they say " you can use magsik app to modify the factory boot.img ,and flash patched boot.img ".
I'll take a look at this.
didn't have much luck. it seems these tablets are locked in not a conventional way. best to leave as is unfortunately.
Up
mountainsnow said:
these tablets are locked in not a conventional way
Click to expand...
Click to collapse
Did you try this method for unlock?
Meberry M7 - Unisoc Tiger T310 - Root, TWRP, +Info, etc.
Little review and tablet issues: This is a 2020 Tablet, that was launched with Android 11, and the last security patch was December 2021. Hardware It packs an UNISOC Tiger T310, basically 1 ARM A75 and 3 A55 4 GB RAM and 64 GB ROM Build...
forum.xda-developers.com
-------------------
Drivers for windows
SP_Drivers_EXE_v2.0.zip
drive.google.com
-----------------------------
Unlocking Unisoc Bootloader on linux1) fastboot oem get_identifier_token
2) ./signidentifier_unlockbootloader.sh 303132333435363038394142434????6 rsa4096_vbmeta.pem signature.bin
where 303132333435363038394142434????6 is identifier_token , rsa4096_vbmeta.pem is a private key of Unisoc
3) fastboot flashing unlock_bootloader signature.bin
I ended up just returning the tablet and grabbing something else. I no longer have this model to test unforunately.
Hi Everyone, I hope somebody can help me I've a Toshido Android tablet with mainly these specifications below:
- OS: Android 10;
- RAM 4GB;
- STORAGE: 64GB.
I own this tablet from several time, and now I'd like to root it, but it does not seem to be a widespread model. Could somebody help?...
Thanks in advance for any help, please sorry for my english and my poor experience too, let me know if I forgot something
Look inside here ( note: the method suggested is generic )
[ GUIDE ] [ ANDROID 10 ROOT ] [ HOW TO ] Patching Boot.img with Magisk
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step : (not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device) What do you need : > Pixel 3 phone with Android...
forum.xda-developers.com
xXx yYy said:
Look inside here ( note: the method suggested is generic )
[ GUIDE ] [ ANDROID 10 ROOT ] [ HOW TO ] Patching Boot.img with Magisk
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step : (not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device) What do you need : > Pixel 3 phone with Android...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you, I downloaded and installed Magisk on the tablet and yet downloaded the link of the described "Android 10 factory image" (it's valid for my Toshido tablet too, right?.. ), then I extracted all into my pc, and copied a file named "boot.img" into my tablet as described on the thread (as I understood..)...for now I wished ask you if till now I did right.. (I didn't install the "Boot.img" file yet, because I still have to install ADB and FASTBOOT tools because I tried but my Linux OS is giving me some problems w repository 'n I'm trying to solve hoping soon...)
I'd like if someone can follow me in these steps... I hope to not annoy you I'd be very gratefull if you can do, 'cause I still have very little experience...
The latest ADB / Fastboot drivers you can obtain here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Sorry, I looked for the 32-bit version I supposed it was available on any architecture, but it doesn't seem to exist for me... I have a laptop with Linux OS on 32-bit Hardware, then I can not do anything? Thank you anyway