Hello,
I recently acquired the HomTom HT10 and I am really liking it so far. Trying to get more out of this device I started looking for viable methods to root it. So far, none of them has worked.
Specifications:
Software:
- Android Version: 6.0
- API Level: 23
- Android Security Patch Level: 2016-08-05
- Kernel Architecture: armv8l
- Kernel Version (in device info): "[email protected] 2016/06/03"
- Kernel Version (in CPU-Z): 3.18.22 (1473842401)
- Build Number: HOMTOM-HT10-Android 6.0-V01-20160914
- Custom Build Version: alps-mp-m0.mp9-V1.33_aeon6797.6c.m_P11
- Firmware download at the bottom of this page: http://homtom.cc/
- Bootloader is unlocked
- I can access the device using ADB and Fastboot
- The only bootmenu is accessible by holding down the Volume Up button while booting the phone. In this menu there are 3 options:
1. Recovery Mode: This shows a blank screen with a picture of a droid with an open chest and a red triangle floating over it, as well as the text "No Command" written above it.
2. Fastboot Mode: This shows a blank screen with the typical "Fastboot mode" text.
3. Normal Boot: Does what you would expect.
Hardware:
- mt6797
- MediaTek Helio X20
- Mali-T880
- Resolution: 1080 x 1920
- Ram: 3 GB
- Memory: 32 GB
Rooting methods I tried (for each method, the mobile and PC version was tried, if one was available):
- Framaroot: 2 Exploits choosable, both of them return Error #6 immediately
- Kingoroot: Error around 85%, can't read Chinese error message
- Kingroot: Root Failed
- iRoot (formerly vRoot): Root Failed
- Towelroot: after pressing the "make it ra1n"-button, the application gets stuck
- Root Genius: phone reboots twice, the PC tool gets to ~56 % and says "Root Failed"
- The Ultimate Guide to Rooting any Android Device Manually: Method 1 works, until I have to reboot into the recovery mode, Ubuntu just won't mount it. Method 2 relies on "psneuter", which gives the error "mmap() failed. Invalid argument". I presume it just doesn't work for my android version, maybe someone knows of an alternative?
http://forum.xda-developers.com/showthread.php?t=2684210
Does anyone have an idea how I could get root on this thing? Can someone maybe point me in the right direction how I would go about decompiling the manufacturer firmware and building a rooted image, or at least build a custom recovery? AFAIK there isn't even a custom recovery available yet.
On another note, I also found MOD Edit:- Links Removed. Could this be useful?
If I forgot to mention anything, let me know!
Thank you for reading this,
Greetings, Nukeer
Edit:
I have managed to root my device, though I had to deal with quite a few real-life issues, so I totally forgot about this thread. I apologize for this late reply, but I guess better now than never. Note: the following two paragraphs are also copied from a reply I wrote in another thread about this phone. If anyone can answer my questions, I'd really appreciate it.
I have the Homtom HT10 running the firmware Android-6.0-V01-20161202 and I was able to root the device using Kingo Root. It's been a while, but I think there were some additional steps to go through before this root worked. My question is if anyone here has had success in rooting one of the newer firmwares, since I'm not sure if this root would survive the firmware update and I wouldn't want to lose root access.
Also, does anyone know how to replace the Kingo Superuser app with Chainfire's version?
[Source for my reply: https://forum.xda-developers.com/an...omtom-ht10-t3564957/post72876549#post72876549 ]
Me too.
I also can not be.
ttp://hirachon.blogspot.jp/2016/10/root.html
also looking for a tutorial to root because i'm not satisfied with the current OS :
- losing connectivity: cannot receive calls (need to reboot or turn off/on SIM cards in settings)
- no 5Ghz Wi-Fi networks compatibility
- losing user preferences (language or default apps)
- froze and reboot if you set a password to lock your device (pattern or PIN)
- battery saving mode is too aggressive and not easy to manage
...
Hi guys!
Same specs here:
Software:
- Android Version: 6.0
- API Level: 23
- Android Security Patch Level: 2016-08-05
- Kernel Architecture: armv8l
- Kernel Version (in device info): "[email protected] 2016/06/03"
- Kernel Version (in CPU-Z): 3.18.22 (1473842401)
- Build Number: HOMTOM-HT10-Android 6.0-V01-20160914
- Custom Build Version: alps-mp-m0.mp9-V1.33_aeon6797.6c.m_P11
- Firmware download at the bottom of this page: http://homtom.cc/
- Bootloader is unlocked
- I can access the device using ADB and Fastboot
- The only bootmenu is accessible by holding down the Volume Up button while booting the phone. In this menu there are 3 options:
1. Recovery Mode: This shows a blank screen with a picture of a droid with an open chest and a red triangle floating over it, as well as the text "No Command" written above it.
2. Fastboot Mode: This shows a blank screen with the typical "Fastboot mode" text.
3. Normal Boot: Does what you would expect.
Hardware:
- mt6797
- MediaTek Helio X20
- Mali-T880
- Resolution: 1080 x 1920
- Ram: 3 GB
- Memory: 32 GB
Solution FIND ! ! !
KingRoot apk finally works !!! :victory:
I tried this version: V4.9.7
by this file: NewKingrootV4.9.7_C152_B341_xda_release_2016_11_14_20161115194410_105243.apk
IMPORTANT NOTE:
1) I find some bloatware that doesnt wipe out neither with a factory reset
2) the root is factoryreset resistant.
3) Some issue with Wathsapp only when sending stored images.
Best regards!
If you are happy with this please tnx me! :highfive:
If you have trouble, please share!
did not work
Westboy82 said:
NewKingrootV4.9.7_C152_B341_xda_release_2016_11_14_20161115194410_105243.apk
Click to expand...
Click to collapse
This NewKingroot apk did not work for me, no root available, same for version 5 from kingroot page.
I hope someone can figure this out soon.
ht20 / ht10 / root homtom
hello Nukeer,
have you found a way yet? i bought the ht20 a few weeks back, and would also like to root it, and if it works, plan to probably use replicant... already contacted them.. waiting.
any ideas? something we could share, work together?
there is a new firmware available:
https://forum.xda-developers.com/android/general/homtom-ht10-firmware-homtom-ht10-t3564957
This video describes the installation of TWRP and after the installation of SUPERSU within the TWRP Recovery in HomTom HT10
The same recovery and scatter file to flash it with SP_Flash_Tool i found it at the needrom.
Does anyone tried this method;
I don't have the phone yet so i cannot try if work.
Because i cannot post outside links search at the youtube for the video "HOMTOM HT10 TWRP и ROOT" from "vova snake" channel.
See the edit in my original post. I've done it, I managed to root my device.
Root did well
Hi guys, i could root using kingroot, it was an easy task. Greetings.
root HT10 with twrp and su
damaskos said:
This video describes the installation of TWRP and after the installation of SUPERSU within the TWRP Recovery in HomTom HT10
The same recovery and scatter file to flash it with SP_Flash_Tool i found it at the needrom.
Does anyone tried this method;
I don't have the phone yet so i cannot try if work.
Because i cannot post outside links search at the youtube for the video "HOMTOM HT10 TWRP и ROOT" from "vova snake" channel.
Click to expand...
Click to collapse
It's in Russian ?
here is one in english on youtube youtu.be/btdllA1vlqI
How to Root the HTC 10 and Install TWRP Recovery by RootJunky
Related
Hi all,
Let me first thank you for the wonderful website that you've created here, it already really helped me out.
Now, I want to root my fake Galaxy S4. I know the pain of people who ask questions without trying to look around for a solution themself. Yet, after a few full days, starting without any knowledge of smartphones, working my way trough all the terminology and trying to root my device... the only thing I know left to do is asking for your help. I sincerely hope this is 1) the right place 2) I'm allowed to ask this here and 3) there is not already a simliar topic... If I still failed then feel free to redirect me, move me, etc.
I bought the following device:
Hardware : MT6575 (SAMSUNG is aFake!)
Model : GT-I9500
Build number : JDQ39.I9500ZHUAMDE
Build date UTC : 20130606-103654
Android v : 4.2.2
Baseband v: MAUI.11AMD.W11.50.SP.V37, 2013/05/06 11:21
Kernel v : 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 Thu Jun 6 18:33:27 CST 2013
This is what I did:
Drivers:
- I've downloaded and succesfully installed pda drivers.
- I've manually installed MT6575_USB_VCOM_drivers by connecting my phone while holding the volume button. These drivers appear, but disappear again in the Device Manager.
Tried Roots:
- This one of course. But the 'Restore button' does not pop up.
- SRSRoot - does not work
- New graphical method for MTK6589,MTK6577,MTK6575 - does not work
- Manual way directed via MTK Droid Root en Tools:
I failed here at step 7. Mtk drooid Root does not make the CWM automaticly.
Furthermore:
- Tried removing all user data in Recovery Mode, but when I press the power button to select the option it simply does not react.
- I can not enter 'download mode' as far as I know.
- I know there are more methods in Gizbeat 101, but I can't acces them right now... as I'm not a full member there and somehow got instabanned.
- I have the idea they could help me at the Russian fora.. I found this thread with help of google translate... but I don't speak Russian and can't figure out what to do.
Can anyone help me out? This phone has hardly any internal storage. I can't remove most of the applications and a lot of appliacations first install on it's internal memory. If I can't root it, then I can't really use any new applications, since there is no room.
One more question: Am I right if I say I could flash the phone without rooting it? Only that there are at the moment no mtk6575 roms to flash on it?
You're my last resort, else I'll just accept the phone is unrootable and probably buy a new one.... Any help would be much appreciated!
i did factory reset - and network signal is gone for the same above fone
do u have any solution
i tried all possible solutions
some say it is 2.3 not 4.2.2
do u have rom (cumsum)
when i tried to restore data - it said cumsum match error
kingvasudev said:
i did factory reset - and network signal is gone for the same above fone
do u have any solution
i tried all possible solutions
some say it is 2.3 not 4.2.2
do u have rom (cumsum)
when i tried to restore data - it said cumsum match error
Click to expand...
Click to collapse
Hey man,
I think it's not possible to make a full back-up without rooting the phone is it? Else I'll be glad to help you out.
I can make a scatterfile with the mtkdroidrootprogram.. but the 'backup' button in mtkdroidroot is grey.
If you tell me how to make a backup I'll gladly help.
So I probably shouldn't just try and flash my phone? Good chance I brick it...
Best regards,
R.
ps. I'm dutch but happened to be in Hyderebad not so long ago
I got root on a s4-clone with the same specs as the first poster.
I used Cydia Impactor.
I can not attach links, so just google it.
megabirger said:
I got root on a s4-clone with the same specs as the first poster.
I used Cydia Impactor.
I can not attach links, so just google it.
Click to expand...
Click to collapse
Thanks for your reply! But...
Cydia Impactor does not recognize my phone. (errormsg: "/data/local/tmp/impactor-5" or "no such device")
Which drivers did u use?
S3 Mini Clone Korea
any of you know how i can root may s3 mini clone korea mtk 6575? any info would be appreciated! thanks a bunch!
chubywoobee said:
any of you know how i can root may s3 mini clone korea mtk 6575? any info would be appreciated! thanks a bunch!
Click to expand...
Click to collapse
i also have the same unit and i tried every rooting method but no success. What i did is i just install superuser app and it works. hope this help. cheers.
HydraNL said:
Hi all,
Let me first thank you for the wonderful website that you've created here, it already really helped me out.
Now, I want to root my fake Galaxy S4. I know the pain of people who ask questions without trying to look around for a solution themself. Yet, after a few full days, starting without any knowledge of smartphones, working my way trough all the terminology and trying to root my device... the only thing I know left to do is asking for your help. I sincerely hope this is 1) the right place 2) I'm allowed to ask this here and 3) there is not already a simliar topic... If I still failed then feel free to redirect me, move me, etc.
I bought the following device:
Hardware : MT6575 (SAMSUNG is aFake!)
Model : GT-I9500
Build number : JDQ39.I9500ZHUAMDE
Build date UTC : 20130606-103654
Android v : 4.2.2
Baseband v: MAUI.11AMD.W11.50.SP.V37, 2013/05/06 11:21
Kernel v : 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 Thu Jun 6 18:33:27 CST 2013
This is what I did:
Drivers:
- I've downloaded and succesfully installed pda drivers.
- I've manually installed MT6575_USB_VCOM_drivers by connecting my phone while holding the volume button. These drivers appear, but disappear again in the Device Manager.
Tried Roots:
- This one of course. But the 'Restore button' does not pop up.
- SRSRoot - does not work
- New graphical method for MTK6589,MTK6577,MTK6575 - does not work
- Manual way directed via MTK Droid Root en Tools:
I failed here at step 7. Mtk drooid Root does not make the CWM automaticly.
Furthermore:
- Tried removing all user data in Recovery Mode, but when I press the power button to select the option it simply does not react.
- I can not enter 'download mode' as far as I know.
- I know there are more methods in Gizbeat 101, but I can't acces them right now... as I'm not a full member there and somehow got instabanned.
- I have the idea they could help me at the Russian fora.. I found this thread with help of google translate... but I don't speak Russian and can't figure out what to do.
Can anyone help me out? This phone has hardly any internal storage. I can't remove most of the applications and a lot of appliacations first install on it's internal memory. If I can't root it, then I can't really use any new applications, since there is no room.
One more question: Am I right if I say I could flash the phone without rooting it? Only that there are at the moment no mtk6575 roms to flash on it?
You're my last resort, else I'll just accept the phone is unrootable and probably buy a new one.... Any help would be much appreciated!
Click to expand...
Click to collapse
please send me your backup, i will make cwm 6.0.3.0 recovery for you.
make your backup with mtk droid tools 2.3.8 . connect phone with usb, click on root . it will root temporary . click on the bakup . creat backup and upload on the 4share or any other place and send me link.
i will make cwm recovery for you if you like TWRP recovery i will make also for you
try
try kingoapp i rooted my phone with the same chipset of yours.. just give it a try..
reminders:
+allow usb debugging
+ur pc needs internet connection
+remove sd card
+do factory reset
just google about kingoapp since i cannot post a link here because i am new member...
Porklo said:
try kingoapp i rooted my phone with the same chipset of yours.. just give it a try..
reminders:
+allow usb debugging
+ur pc needs internet connection
+remove sd card
+do factory reset
just google about kingoapp since i cannot post a link here because i am new member...
Click to expand...
Click to collapse
Thanks for the tip.
Won't the factory reset brick my phone? Since it won't install the hacked ROM?
I tried it without the factory reset but it says "This is not a real Samsung." Will that really change if I factory reset :S?
Try Farmaroot Application buddy. It will work.
forever king said:
Try Farmaroot Application buddy. It will work.
Click to expand...
Click to collapse
Your device seems not vulnerable to exploit included in Framaroot
HydraNL said:
Your device seems not vulnerable to exploit included in Framaroot
Click to expand...
Click to collapse
Oh, then did you tried " TPSparkyRoot" method? and sorry, i thought you're using mt6577.
Try the software eroot. Everything is in Chinese but I just clicked and clicked and finally got my phone (clone s4 mini Korean) rooted.
I now have my phone bricked when I tried to install some fonts. I got into the 3e recovery but cannot execute the command.
ahmadw said:
Try the software eroot. Everything is in Chinese but I just clicked and clicked and finally got my phone (clone s4 mini Korean) rooted.
I now have my phone bricked when I tried to install some fonts. I got into the 3e recovery but cannot execute the command.
Click to expand...
Click to collapse
Just fyi, if you still wanna know:
In 3e, you can execute the commands by hitting the lower left touch key, think it's the menu button took me like forever to figure that out
Anyways, I probably got the same mobile, it is a mtk6575. But I am not sure which custom rom I could install safely. Which one worx for sure?!
Eroot
ahmadw said:
Try the software eroot. Everything is in Chinese but I just clicked and clicked and finally got my phone (clone s4 mini Korean) rooted.
I now have my phone bricked when I tried to install some fonts. I got into the 3e recovery but cannot execute the command.
Click to expand...
Click to collapse
Man! After several hours and efforts on trying root my chinese s4 clone, I saw your post about eroot!
It just worked like a charm!
Thank you!
Hi guys,
I have a S4 mini clone with the follow config:
--About the phone info
Device Name: GT-I9190
Model number: GT-I9190
Android version: 4.2.2
Baseband version: I9190XXUAMF5
Kernel Version: 3.4.0-849021 [email protected]#1 Thu Jun 13 16:52:08 KST 2013
Build Version: JDQ39.I9190XXUAMF5
SELinux state: Permissive
--Antutu tester info
Phone model: GT-I9190
Phone brands: Samsung
CPU model: ARMv7 processor rev 10(v7l)
CPU frequency: 13.53
CPU manufacturers: SAMSUNG SERRANO
Internal RAM: 1349(MB)
Internal ROM: 107(MB)
Android OS version: 4.2.2
Version: JDQ39.I9190XXUAMF5
Kernel Version: 3.4.0-849021 [email protected]))#1 SMP PREEMPT Thu Jun 13 16:52:08 KST 2013
Screen Resolution: 540x960
--Factory mode info (hold volume up + power button when phone turned off)
BB Chip: MT6575
MS Board: GT-I9190
Modem Ver: MAUI.11AMD.W11.50.SP.V37 2013/08/20 12:45
Build time: 2013 09 27 14:25:07 CST
UBoot ver.: 2010.06
Kernel ver: 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Fri Sep 27 14:21:49 CST 2013
Android ver: 2.3.6
SW ver: MDK_V2.1_K18_en_tp6306_v2.3
Custom Build Verno. : 1380262921
It's a clone from China/Korea/Japan (I don't know) and I would like to root and update the android version but I've tried a lot of different tutorials but no success in anyone.
I tried to put my phone on Download mode (Hold volume down + home button + power button) but it only show a screen with the android robot and a triangle with white borders and an exclamation inside. It is the recovery mode (Android recovery mode <e> with some options appears if I press home button)
Could somebody help me on this?
I tried:
* Odin -- Does not recognize my phone because it is not in download mode
* Mtk droid tools:
--->>> Connect to device <<<---
--- Nand Page/Spare = 2048/64
--- Start ZergRush ...
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- Through CWM it is possible to get root on this phone!
* PdaNet -- Don't do nothing, loose of time testing it!!
* SP Flash Tools -- When I choose the scatter file (generated by MTK Droid tools) the list of downloads does not fill the 'Location' and it does not let me download anything.
Nothing works. I really would like to root because I want to update android and uninstall a bunch of chinese/korean apps that shows semi naked women in the middle of screen from nothing. Depending on the situation it can cause an embarrassment for me.
Please help me!!!!!!
s4 I9500 replica
can some one help me get the rom for a mt6575 I9500 dual core 1Ghz, 512rami managed to flash a few roms, but i think those are not for my device, cause most of them are S3, or note, but it matches cause of the NAND flash file on them, can some one help me with this?, device dont turn on or charge, but ican make it work on pc to flash by holding down volume- key and then pluging cable to pc, when first red bar pass i but the battery and flash is complete(this is using SPFlash Tools.
Haven't been able to find anything on this model as of yet, looking for info for rooting and any possible roms/hacks. also asking for thumper1436 who's original thread is http://forum.xda-developers.com/general/xda-assist/please-help-stock-nextbook-10l-quad-t3254936 --there (sorry, not familiar with proper tagging features for the bulletin boards just yet).
thanks for any info in advance!
found some hope from https://www.youtube.com/watch?v=baIhaJ0Zz5U . not the exact model but a starting point maybe? we'll see.
::edit:: i'm an idiot. after mulling about and using the commands in the video comments, I kind of figured it out. booted into bootloader, flashed the boot and recovery img's via fastboot, and so far so good. rebooted into recovery and twrp is up (yay). now to work on rooting (hopefully as easy as installing the zip files through twrp). worst thing that can happen is I brick it. wish me luck.
oh yeah, android 5.0 kernel version 3.10.20-x86_64byt build v 1.0.7
okay, so attempted backup via twrp but it failed. figured wth, flashed recovery zip and super su zip from link in youtube video ( https://www.youtube.com/watch?v=baIhaJ0Zz5U ). after rebooting, went to play store and installed a root checker, and viola. so root achieved.
keep in mind that using twrp wouldn't work without keyboard attached (which is annoying). controls are normal, though throughout the process the screen goes portrait mode instead of landscape, so figuring out "mouse" controls is wonky but doable. after root, using the touchscreen is all but gone (very very buggy, not sure how to fix as of yet). if i could find a recovery image from mfg it'd be great (already emailed them about it, but very very doubtful it'll show up).
tl;dr
root is possible, but makes system buggy.
DO THIS AT YOUR OWN RISK! YOU ARE RESPONSIBLE IF YOU BRICK YOUR TABLET! WARRANTY IS VOID, ETC.
-----please do a clean install/wipe/factory reset first. it's always a good idea and can save you the headache from bugs that can occur from not doing this. please. google is your friend if you're a bit lost on how to do anything referenced in this "guide" ----
I take no claim of ownership of the files used in this process. respect goes out to the owners/originators.
1) install working adb drivers (through android sdk or however). I went with installing from here . don't forget the java crap (link is on this page too, just read the instructions).
2) download twrp and recovery files from here
3) i downloaded the nocturnal adb stuff as well from here . Was easier to keep files organized imo.
4a) extract files from both and put files from step 2 into the same directory as files from step 3 ( will look like image from looky looky when done right). don't forget to copy the recovery.zip and SuperSU246.zip to the root of an external sd card, going to need these in the future.
4b) i forgot about the developer options thing. if you're working with the tablet already booted up like normal, you have to enable developer options and turn on usb debugging (there's all the info on that in the youtube video referenced from the post above, or by google-ing it).
5) hold down shift and right click in window, select "open command window here". if tablet is loaded up like normal, you'll type in "adb devices" to make sure the drivers installed okay (it'll show a device if all is done right). if tablet is already in the bootloader, type in "fastboot devices" and it'll show a device if all is done right. google is your friend on how to get into the bootloader, or you can always load up the tablet, verify the adb drivers are working, and go to step 6.
6) type in "adb reboot bootloader". when it loads up, type "fastboot flash boot boot.img" and hit enter. When that completes, type in "fastboot flash recovery twrp_recovery.img" and hit enter. all should show okay (mine had a data error from the backup, didn't seem to effect much, though i'll be going back and redoing this with a clearing of data/factory reset first that will hopefully kill the buggyness of the touchscreen.
7) use the volume down button to change the option to "recovery mode" and select with power button. once there the fun begins.
8) as stated before, using the mouse pad seems the only way to go. up is up, down is down. the screen however is turned on it's side this way.
go to the "install" button and click on it. navigate to the root of the external sd card (click the storage button at the top, change to external_sd) and click ok. should have to just scroll down and select the recovery.zip file. click "add more zips" button and select the SuperSU246.zip file. click and drag the "swipe to confirm flash" button and release. wait for confirmation of success.
9) go back to main menu (I used the navigation buttons on the physical keyboard) and reboot into the system.
that's all there is. as stated, it is buggy as hell and the touchscreen is all buggered up. but using the keyboard/touchpad seems to work. not sure of too many other bugs yet as this is fresh off the press and I haven't done anything else with the tablet since doing this (besides installing the root check program from the play store and running it to verify it worked.
hope this helps someone =)
::edit:: damn this is a little confusing to read, sorry about that. first time attempting a guide like this.
device info from skipsoft android toolkit.
DEVICE INFORMATION
==================
Product Manufacturer: Yifang
Product Model: NXA101LTE116
Model ID:
Device Type: NXA101LTE116
Device Characteristics: nosdcard,tablet
Product Serial Number: YFGV0715030938
Build Description: nxm1017bapl_64-user 5.0 LRX21V 20150708.171530 release-keys
Build Date: Wed Jul 8 17:17:24 CST 2015
Hardware: nxm1017bapl
Board Platform: baytrail
Build Version Release: 5.0
Build ID: LRX21V
Bootloader: unknown
Build PDA:
CSC Sales Code:
Region Code: US
Ro.secure Level: 1
Ro.adb.secure Level: 1
Selinux.enforce Level:
Selinux Level:
Alarm Alert: Alarm_Classic.ogg
Notification Sound: pixiedust.ogg
Ringtone: Ring_Synth_04.ogg
------------------------------------------------------------------------------------
Boot Image Status is: SECURE [based on ro.secure value]
Note: This is only an indictation if the boot image files have been modified
------------------------------------------------------------------------------------
::edit:: info was prior to rooting device.
Do you happen to have a stock image or a backup available?
daleguthery said:
Do you happen to have a stock image or a backup available?
Click to expand...
Click to collapse
unfortunately no. i tried emailing the mfg to no avail (they claim they don't have the image files to restore them). haven't tried doing a factory restore yet, though i doubt that'd help. right now i just use it as a "laptop" with using the track pad instead of the touch screen. still a work in progress, just been busy with life happenings. will update if i can find out more (or if i manage to get my hands on another untouched unit that i can try and dump or something).
I have also tried contacting the mfg, and they told me the same thing. I read somewhere that this tablet was actually made by eFun. The stock rom for the model without LTE will work on this tablet, however there are somethings that don't work correctly, the first being enabling LTE and recognizing a SIM card. The others are camera orientation, and screen rotation is always upside-down.
daleguthery said:
I have also tried contacting the mfg, and they told me the same thing. I read somewhere that this tablet was actually made by eFun. The stock rom for the model without LTE will work on this tablet, however there are somethings that don't work correctly, the first being enabling LTE and recognizing a SIM card. The others are camera orientation, and screen rotation is always upside-down.
Click to expand...
Click to collapse
I have the same tablet. I will be attempting to root.
Hi everyone,
A couple of days I posted in XDA Assist and was asked to seek help here. Therefore, I'm posting my original post here, along with some updates at the end.
Original Post:
#####################
I've got a reasonably unknown Tablet PC.. Here are the specs and miscellaneous information;
Name: Ainol Numy 3G P97
Internal Memory: 16GB
RAM: 1GB
GPU: Mali-400 MP
SoC: MediaTek MT8382 ARM Cortex A7 @ 1.3Ghz (Quad Core)
OS: Android Jellybean 4.2.2 (I'm pretty sure it's a Custom ROM)
Kernel Version: 3.4.5
Build Number: Numy_3G_P97_V1_2014090215
Custom Build Version: 1.19_20140822
Root Access: No (I never tried to root the device, never had a reason to do so)
I've been searching around for ways to upgrade the OS from Jellybean to Lollipop or higher. I've searched extensively within XDA Developers' various forums, but there doesn't seem to be any post in relation with my device.
I took to the internet and found some websites offering Flash Tools, Firmware (nothing above KitKat, or so it seems) and Android Studio. I've tried (in vain) to go through some tutorials on YouTube, but haven't come across anyone who's done anything with this particular device.
However, I have a rough idea rattling around in my head of what needs to be done, but I just need guidance from the Developers here to tell me how to get about doing it.
I have the following software downloaded;
1. MediaTek USB Drivers and Flash tools
2. SP Flash Tool v5.1620
3. Official Android Jellybean 4.2.2 System Image for the device
4. Android Lollipop 5.0 System Image (the site I downloaded it from says the Firmware is for a different tablet pc, but with the same specs as my device)
5. Android Studio (latest version, direct download from Google) - I read in some sites that Android Studio would help a lot to install a Custom ROM into any Android device, hence the download.
I'd greatly appreciate anyone helping me out in this endeavor. I'd like to install Lollipop (at least) on my Tablet PC, in order to gain some functionality as well as improved performance (hopefully!), as the current Jellybean OS is terribly laggy. I've seen other Tablet PC's with lesser specs running Lollipop smoothly, so I'm hopeful that there might be a silver lining to an otherwise very dark and sinister looking thunderstorm.
#####################
End Post
Updates:
While waiting, I've tried a few things. I downloaded the following;
1. Android SDK Tools with Platform Tools
2. Android Lollipop system images x 2 (.img file format) (similar specs to my Tablet PC)
3. Android Lollipop system image x 1 (.zip file format) (similar specs to my Tablet PC)
4. Android KitKat system image x 1 (supposedly the original and official KitKat OS for my Tablet PC)
5. Kingo Root app (Windows version)
Here's what I tried:
I tried using ADB to sideload a Lollipop system image (.zip file format) through a custom recovery already installed on my Tablet PC. Each time I tried, the installation would just stop with "Installation aborted". No matter what I did, I couldn't get it to work.
Next, I tried to "update" the current OS (Jellybean 4.2.2) to KitKat using the "official update" I found on the net, for my Tablet PC. I used SP Flash Tools to try and load the file, but that didn't pan out, as there was something corrupted in the Scatter file. Each time I tried to load the Scatter file, I'd get the error message that it was corrupted. Didn't know what else to do.
Following that, I read some articles where rooting the device in question was suggested, so I searched around for a bit, found the Kingo Root app, used it and rooted my device. Then, I tried using ADB again, this time using a more traditional method of custom ROM installation. But once I got to the Fastboot commands, I couldn't get any further. My device did boot up in Fastboot mode, but I got lost after that.
As of yet, my device is still running Jellybean 4.2.2. I've refurbished it by doing a master reset, but I'd really like to get Lollipop in, if it's possible. Any help would be much appreciated.
Thanks!
Serious help needed please!
I really need help, people, on this issue! Isn't there some kind soul who will respond??
About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...
I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.
THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build
Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!
Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones
Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.
Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:
Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.
Hey.
I have a question, if there is anyone who knows how to help me with getting root access for my phone (Tesla 6.2 lite).
Before I continue: this is my first post on this forum, so I don't even know if the topic is in the correct "department", so please mods feel free to move it to another section if it is not correct. Thank you.
Ok back to my problem:
I have this phone (mentioned above), which I need root access to. I have tried with one-click root programes (KingoRoot, KingRoot, OneClick, ...) and had no luck. Then I went on to try MTKdroidTools, SP_Flash_Tools, and yet no luck. All I was able to do is to unlock bootloader using Fastboot in CMD.
I have also tried booting .img files through SDcard and didn't work. I don't know all about rooting, but this is such a specific phone, that I wasn't able to find any tutorial on how to do it properly. I used to root my Huawei P7 and Samsung S5, Samsung Ace; but that was very easy via one-click root options and/or SDcard flashing (for custom ROMs).
I tried with USB debugging on, OEM on, ...
To recap, I only need an "admin" or "root" access to my phone, not necessarily a full custom ROM.
Specs:
Phone - Tesla 6.2 Lite
Model um. - SP6.2_Lite
Chip - MT6737M
MS Board. - F5C
Kernel ver. - 3.18.19+ ([email protected] #1)
Android ver. - 6.0
Appreciate the experts help!
Thanks