Related
This post (#377 on page 38) was originally written under thread "Root Now Available For ASUS MemoPad FHD 10 Model ME302C" (http://forum.xda-developers.com/showthread.php?p=51699593) however OP has not been able to update the original post and this has caused much confusion. Its difficult to read through 40+ pages of posts with new modifications to the originally posted root procedure. I am posting the latest instructions in a new thread.
Thanks to @perpe on the German Android Hilfe forum
[Anleitung]Root, Unroot, Up-/Downgrade, Unbrick ASUS MeMO Pad FHD 10 (ab Android 4.3)
http://www.android-hilfe.de/root-custom-roms-modding-fuer-asus-memo-pad-fhd-10/528918-anleitung-root-unroot-up-downgrade-unbrick-asus-memo-pad-fhd-10-ab-android-4-3-a.html
There is also a Russian Forum 4PDA for this tablet
Прошивка Asus MeMO Pad FHD 10 (Только WW регион)
http://4pda.ru/forum/index.php?showtopic=500286
This is a thread for apps that can be frozen or removed:
[Sammelthread] Apps die man deinstallieren oder einfrieren kann
http://www.android-hilfe.de/asus-memo-pad-fhd-10-me302c-forum/482780-sammelthread-apps-die-man-deinstallieren-oder-einfrieren-kann.html
+++++++++++++++++++++++++++
This guide and below links are for USA build only (Goto Settings -> About Phone -> Build Number). WW build needs WW 5016 update and WW 5017 root update files but, indeed, uses the same procedures. DO NOT interchange USA for WW files otherwise you will BRICK. Links for WW 5017 root can be found on previous forum posts. ASUS hosts the WW 5016 update on its support page http://www.service.asus.com/#!downloads/c1wax
AS ALWAYS, BACKUP YOUR DATA! Titanium backup is a good option. Make sure backup files are copied to your PC or external storage
MAKE SURE THE BATTERY IS FULLY CHARGED!
Tools Needed:
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
For those of you who are already root and would like to update to 5016 it is recommended to download the latest 5016 update (~700mb) directly from Asus website. Please do not do an OTA update as this may fail since you are already root. Make sure that SuperSU survival mode is OFF. Place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
For those of you who are not rooted the easiest method is to accept the OTA update to 5016. (Alternatively, place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet). Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
Please note avoid OTA updates after root is obtained otherwise you will loose root or maybe worse. Keep up to date with developments on this thread for rooting methods when and if Asus release new updates. @perpe recommends all future updates be installed via the internal storage method. You can also check the German FHD 10 forum for updates at the above link
+++++++++++++++++++++++++++
Step by Step Guide for root via Fastboot Method for US version 4.7.3 or below: (read above instructions first as it is much easier to update and root using alternative methods)
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. Some members have suggested downgrading fastboot to 4.7.3 if you have a later version. However this is not recommended and could result in problems. Fastboot downgrade should only be a last resort and limited to advanced users:
fastboot flash fastboot fastboot.img
(fastboot.img can be found inside the 4.7.3 release on the ASUS website. You can extract fastboot.img from the ~700mb update using 7 zip. Or download USA build here: http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip )
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
(Please note do not use command "fastboot erase system" - it has caused many people issues and is useless)
(Please note "fastboot erase userdata" is optional. the command is a "factory reset" and removes all user data. Sometimes after an update the tablet may be sluggish or have issues then you could try this command)
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
If it is working your CMD window will show:
sending 'update' (******* KB)...
OKAY [49.549s]
writing 'update'...
OKAY [3.220s]
finished. total time: 52.772s
Tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
+++++++++++++++++++++++++++++++++++++++++++++++++++
Step by Step Guide for Factory Reset via Fastboot Method for US version >4.7.3:
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. You’ll need to downgrade fastboot to 4.7.3 before restoring your tablet. Extract Fastboot.img from US_ME302C_V4_7_3.rar using 7 zip (~700MB download, link below) or download just Fastboot.img (~10mb, Mediafire link below) into same directory as ADB and Fastboot
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Fastboot 473 IMG - http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip
USA Asus 473 update – http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C_V4_7_3.rar
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
fastboot flash fastboot fastboot.img
be patient while update completes then reboot back to bootloader
adb reboot bootloader
fastboot devices
fastboot erase cache
fastboot erase userdata
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
One little note:
fastboot flash update <name-of-the.zip> only works with the 4.2.2 fastboot. On 4.3 it only works with small zips, like the fake update.zip for root.
The easiest way to update is to place the update zip on to the internal storage and select the triangle from the notification bar to start the update process. (it's the same way like with the root zip)
cantdownload
Cant download 2nd link
Beware
Hey Guys, after I applied these "updates" and checked root (positive) I installed the Xposedframework , when I rebooted my Memo , it does not get much further then the ASUS logo and never-ending busy circle. I will attempt a factory reset, and let you all know.
Just posting this message to make sure you have your backup done as mentioned in the first post. It could be painful otherwise!
Hi
can u help me root asus zenfone 5 ?
or tell me how to make a update ota zip flashable to flashed on stock recovery..
thx for reply me...
Hi all. Thanks for the great post. This forum helps a lot who would other wise be lost.
I am a bit confused about the methods posted in the opening post. The first method explains DL the files and install from internal storage which seems simple enough. But then I scrolled down to see the second method via fastboot.
I would prefer to use the first method as it appears simple as I have said. But unsure which I should use.
Also how can I backup without root access?
Thanks for your help
Mode l# ME302C
Firmware version: 51.31
Android Version: 4.2.2
Build # US_EPAD-4.6.2-20130815
Edit: I jumped in and used the procedure described in "For those of you who are not rooted "(or the second method of the first 2). It worked. My memopad is now rooted and appears to be operating fine. Thank you to the author of this post.
help needed
Why can't I get the magic yellow triangle? Somebody please help me.
Here are my screen shots from my google+, please remove the blank space at the beginning of the address:
ht tps://plus.google.com/106139843999975472357/posts/818h3Tbagkm
ht tps://plus.google.com/106139843999975472357/posts/Z6J5iTEPswP
Asus302c said:
Why can't I get the magic yellow triangle? Somebody please help me.
Click to expand...
Click to collapse
Try plugging it into a computer or rebooting.
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May. http://usterki.hobby-elektronika.eu/biazet.html
Polarbert said:
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May.
Click to expand...
Click to collapse
Yes and you risk to get big trouble if SuperSU survival mode is active. For save updating you have to remove root first.
Gesendet von meinem ME302C mit Tapatalk
I just wanted to say:
I got the Memo Pad FHD 10: It lagged in slowness a bit in a few well known apps. Also when browsing the internet. Also the kicker for knowing I had to 'Root' was certain apps use the 'System font' for Chinese-Pinyin display. Asus-Memo Factory-font does not display accented characters well. But the standard setting do not allow adjustment to the System-font.
Your Easy instructions under: 'For those who are not rooted'... Were simple. I downloaded the two files... 5.0.16 (Although: Note I needed to rename, the 5.016, to exactly match what you said. The filename was slightly different.)
I was a little scared, even though I had already upgraded the firmware of my Tablet to 51.31, but another poster had that number as well, so I decided to boldly press-on.
Then I put the 5.017 and boom... and installed the SuperSU file as instructed... and a way I went! Thanx! Thankx! :good: I put on HiFonts and found a font that was suitable for the system. The pad is also now so much snappier!!! I hope that doesn't mean the battery is now going to drain at an alarming rate. I haven't tested that yet. :
GPS Working 5017
intrepid24 said:
This post (#377 on page 38) was origina
Click to expand...
Click to collapse
Is anyone else having an issue with the GPS on the device on 5016 rooted with the 5017 using the 'intrepid' link above. A favorite app we use: 'Copilot', does not get past "determining position". I'm speaking of when the device does not have an internet connection.
The app I speak about is designed to work without only the GPS available. But since I'm on an odd build, instead of checking with the problems on those ends. I figured, I worry first about the build itself.
I know this may be quite an old thread, but I've stupidly updated my fathers tablet to 5.0.21, and in the process lost root. Is there any trouble with following this method to get back to 5.0.17 and rooting the tablet? After updating I saw no difference, and thus no need to lose root access.
http://www.gory.pun.pl/viewforum.php?id=5
Is there an alternative to getting root? I've tried towel root and framaroot but neither of these worked.
To this day this tablet has treated me well...Is there any kitkat roms floating around the web for this tablet?
asus memo pad me302c stuck on boot screen
Hi guys! I`m new on the forum so i don`t know if this is the right place to ask... I have this Tablet stuck on boot screen and i tried every solution i found on internet but nothing seems to make it work... Can someone give me a clue about what can i do? Thank you!
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
_MsG_ said:
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
Click to expand...
Click to collapse
What works depends on what you were doing before this issue appeared.
If you can read German, you can check:
http://www.android-hilfe.de/thema/a...k-asus-memo-pad-fhd-10-ab-android-4-3.528918/
I'd recommend trying the RAW update.
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
robertkjr3d said:
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
Click to expand...
Click to collapse
How did you get the bootloader unlocked to be able to install a custom recovery and then a ROM to begin with? I chatted with Asus support just now and they said that for the ME302C they never made an unlock tool which I don't believe. I have an ME301T and they made the tool for it and I was able to unlock the bootloader, root and custom ROM. I was going to root my friend's ME302C but without being able to unlock the bootloader to install a custom ROM I don't see the point. Thanks in advance!
Asus ME302KL will this be the same process?
Hello Everyone -
Welcome back , In previous post i explained " How to install twrp and root Xolo Era X,4G" but i forgot to mention some things which resulted errors for many users making it non-beneficial , I mean wasted time , data , or may be the android rom. Thanks for describing problems in previous post.Now it's mine turn to return you something original , something good .Search your question answers here and problems.
Please note that this thread is only for Xolo era X , 4G marshmallow 6.0 version only , 5.1 is not supported .Sorry but update to 6.0.
1. `adb` is not recognized as an internal or external command
Ans - If you are facing this error then probably you are not in the folder where adb and fastboot tools are installed .
You have to open command prompt only where adb tools,drivers are installed.Still not solving then google it.
2. adb devices = blank (nothing is shown)
Ans - I think you have either not connected your smartphone with usb debugging on or you have not installed proper version of adb and fastboot drivers.Please google for different versions of adb and fastboot.
3. fastboot devices = blank (nothing is shown)
Ans - Same as in above answer.
4. fastboot flash recovery recovery.img = <waiting for device>
Ans - It means that you have not installed fastboot drivers properly or you have not connected your devices in fastboot mode.
5. fastboot flash recovery recovery.img = no such file found or recovery.img not found.
Ans - You have not copied or moved recovery.img(twrp or cwm image file) in the folder where adb and fastboot are installed .So put the recovery.img (it can be twrp.img or somename.img) in the adb and fastboot tools folder(it can be either found in local drive C or at any custom location) .
6. Recovery Installed successfully but still booting in stock recovery or Computer shows installation successful but still opens stock recovery.
Ans - This is a great problem for many users and it is happening due to security policies of android 6.0. To fix it Do as following-
(1) Install twrp recovery and when it say success plug your battery out .
(2)Put battery back and open smartphone in recovery mode by holding VOL Up + Power Button for 15 seconds.
(3)Now your smartphone will boot in TWRP recovery but your twrp recovery is still temporary .
(4)Install SuperSu.zip by twrp recovery and this zip file will patch boot.img and system files.
(5)After installation of zip file reboot your smartphone .
(6)Your smartphone will restart 2-3 times and finally will boot .
(7) Finally you have rooted your smartphone and installed TWRP permanently .Now install busybox and enjoy.
Note: Please Select Expert Mode when you open SuperSu app first time after this process(you will be asked by SuperSu app to select two modes 1 Expert , 2 New User ; always select Expert or root will not function properly).
I hope you got what you wanted . If i helped you then please Subscribe , like and share also Hit thanks here on xda.
Download SuperSu zip from here - https://drive.google.com/open?id=0B_Mx_zMB6YZOUENHdHpDTXZucXc
Finaly
ankitnandgavia said:
Hello Everyone -
Welcome back , In previous post i explained " How to install twrp and root Xolo Era X,4G" but i forgot to mention some things which resulted errors for many users making it non-beneficial , I mean wasted time , data , or may be the android rom. Thanks for describing problems in previous post.Now it's mine turn to return you something original , something good .Search your question answers here and problems.
Please note that this thread is only for Xolo era X , 4G marshmallow 6.0 version only , 5.1 is not supported .Sorry but update to 6.0.
1. `adb` is not recognized as an internal or external command
Ans - If you are facing this error then probably you are not in the folder where adb and fastboot tools are installed .
You have to open command prompt only where adb tools,drivers are installed.Still not solving then google it.
2. adb devices = blank (nothing is shown)
Ans - I think you have either not connected your smartphone with usb debugging on or you have not installed proper version of adb and fastboot drivers.Please google for different versions of adb and fastboot.
3. fastboot devices = blank (nothing is shown)
Ans - Same as in above answer.
4. fastboot flash recovery recovery.img = <waiting for device>
Ans - It means that you have not installed fastboot drivers properly or you have not connected your devices in fastboot mode.
5. fastboot flash recovery recovery.img = no such file found or recovery.img not found.
Ans - You have not copied or moved recovery.img(twrp or cwm image file) in the folder where adb and fastboot are installed .So put the recovery.img (it can be twrp.img or somename.img) in the adb and fastboot tools folder(it can be either found in local drive C or at any custom location) .
6. Recovery Installed successfully but still booting in stock recovery or Computer shows installation successful but still opens stock recovery.
Ans - This is a great problem for many users and it is happening due to security policies of android 6.0. To fix it Do as following-
(1) Install twrp recovery and when it say success plug your battery out .
(2)Put battery back and open smartphone in recovery mode by holding VOL Up + Power Button for 15 seconds.
(3)Now your smartphone will boot in TWRP recovery but your twrp recovery is still temporary .
(4)Install SuperSu.zip by twrp recovery and this zip file will patch boot.img and system files.
(5)After installation of zip file reboot your smartphone .
(6)Your smartphone will restart 2-3 times and finally will boot .
(7) Finally you have rooted your smartphone and installed TWRP permanently .Now install busybox and enjoy.
I hope you got what you wanted . If i helped you then please Subscribe , like and share also Hit thanks here on xda.
Download SuperSu zip from here - https://drive.google.com/open?id=0B_Mx_zMB6YZOUENHdHpDTXZucXc
Click to expand...
Click to collapse
Wahooooooo I it happened. Its done TWRP flashed successfully n my phone Is rooted. Big thanks to you and Murali Dharan and that's how it's done. Here is some point
Es file explorer can't excess root of my phone even if I hit allow.
All other root app are working fine
Can I reflash super user zip of kingo root I am asking coz there was additional files with superuser files u provided to fix twrp
I have lost ur channel put links n I will like n subscribe
CheifX said:
Wahooooooo I it happened. Its done TWRP flashed successfully n my phone Is rooted. Big thanks to you and Murali Dharan and that's how it's done. Here is some point
Es file explorer can't excess root of my phone even if I hit allow.
All other root app are working fine
Can I reflash super user zip of kingo root I am asking coz there was additional files with superuser files u provided to fix twrp
I have lost ur channel put links n I will like n subscribe
Click to expand...
Click to collapse
Hii ,
When you open SuperSu app first time , Please select Expert Mode otherwise root will not work even after granting permission.
ankitnandgavia said:
Hii ,
When you open SuperSu app first time , Please select Expert Mode otherwise root will not work even after granting permission.
Click to expand...
Click to collapse
Hallooooo!
I have already selected expert mode and other root apps working perfectly fine.
CheifX said:
I have already selected expert mode and other root apps working perfectly fine.
Click to expand...
Click to collapse
Then please update or install busybox or you have to restart device after installing busybox or try changing es explorer app version..Es file explorer with root is working fine in mine smartphone.
ankitnandgavia said:
Then please update or install busybox or you have to restart device after installing busybox or try changing es explorer app version..Es file explorer with root is working fine in mine smartphone.
Click to expand...
Click to collapse
I will try busybox later what about reflashing kingo root supperuser.
Es explorer root mot work in xolo era 4g ..same with me........can u provide cwm for my phone 5.1....plzzz
CheifX said:
I will try busybox later what about reflashing kingo root supperuser.
Click to expand...
Click to collapse
Flashing kingo root superuser is not a bad idea, you can try it but be aware of risks so take a backup through TWRP.You can try anything new after taking backup,if something goes wrong then restore your backup.Good luck.
Need latest twrp recovery
I want the latest version of recovery for xolo era 4g and want some custom roms....plz make it.....plzz
I'm facing an issue with the OEM Unlock toggle in developer options. When I toggle it On and select OK for the pop-up box that comes. It automatically disables it. Can u help me out with this and tell me why I'm facing this issue?
yes.. i was too facing this problem but if u are trying to install custom rom then u can flash 5.1 version through SPD Upgrade Tool and then toogle that option then install ur custom rom...
no option is there!
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
{
"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"
}
BTW Sorry for my bad English XD
@Cheese-ass
Greetings and welcome to xda. All posts on xda must be in English, I have translated this one for you but please use google translate for all future post's
Regards
Sawdoctor
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
There is a way to connect a lan usb adapter?
fantastic work like a charm, but used recovery download from the german one and worked rooted oukitel k6000 plus yea
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Worked fine. I had to download files from other websites, but this procedure was good.
After reboot, su was working fine in /system. I wanted to reset the device completely, and typed "fastboot oem unlock"; I thought it would wipe data. Now, phone only boots on TWRP, and it seems like the /data partition is broken. TWRP can mount /system, but not /data. Either the device node is missig, or the partition is not formated properly.
Code:
# cat /etc/fstab
/dev/block/mmcblk0p6 /nvdata ext4 rw 0 0
/dev/block/mmcblk0p8 /protect_f ext4 rw 0 0
/dev/block/mmcblk0p9 /protect_s ext4 rw 0 0
/dev/block/mmcblk0p26 /system ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/external_sd auto rw 0 0
/usbotg auto rw 0 0
Losetup-a gives nothing.
I tried all possible commands (adb reboot to everything), and press volume up or down ... always get back in TWRP. Can not even reach the factory menu (the one where there are tests).
After reformating /data i can reboot to bootloader (fastboot), but still not /system.
Stock ROM was looking fine; I would like to be able to keep it. I would like to avoid flashing to an other ROM.
In short, I have TWRP and flashboot, but /system launches TWRP.
I don't know how to get a working system. SPFlashTool does not seem to work with TWRP installed. TWRP does not like OUKITEL_K6000_Plus_V6.0_20170519.rar. I can't find any ZIP ROM for TWRP. And when I try individual .img files from the RAR, TWRP can install them, but it does notproduce a working phone.
I fear something could be wrong with the partition table, or at least /data. /system contains many files and this looks good.
---------- Post added at 01:30 PM ---------- Previous post was at 12:40 PM ----------
How I fixed it:
fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img (EDIT: this MUST be wrong, should be fastboot flash recovery /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img or fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/boot-verified.img )
then, perform again https://fvknl.pro/k6000-plus-v6-0-upgrade/
and now I have a working phone.
* Can't apply Android updates because of TWRP+SuperSU ?
Now that my phone works, and is rooted (i use the stock ROM version 6), may 19th, the system is telling me there are system updates to do. I have downloaded them (200MB), but after reboot, update fails, for obvious reasons: the update is designed to be installed by the stock recovery firmware; and that partition is overwritten by TWRP.
I was given a tip to work around this (wherer the img file is taken from the .rar archive of the stock ROM):
# fastboot boot /tmp/recovery-verified.img
and it worked: fastboot uploaded the recovery image to the phone, ran it, and that recovery firmware started to apply the update.
Started ... but failed before half of it ... PROBABLY because /system was HEAVILY modified while I asked TWRP to install UPDATE-SuperSU-v2.82-20170528234214.zip (read the installation log of SuperSU ... it alters many things).
How can I apply my android updates without erasing the whole phone each time I want to apply them ?
A: how to get the installation log, to see the failure point, and fix it manually
or
B: install the update manually without running the recovery, but extract the update file, and manually copy the new files at due place, one by one
or
C: how to undo installation of SuperSU, so that /system is in a state where the update can be applied.
I want to do this without erasing /data, or /system. I had this issue on my previous phone; since december 2014 I could not apply any Android update; so my phone is stuck to Android 4 from december 2014. There have been many changes and updates during 2015 and I could not apply them. After installing su, i had been able to perform two Android updates; updates broke after installing Xposed. I do not want my new K6000 to have the same issue; I want to find a way to apply updates. And I would like to keep the stock flavour because there are many features I would like to use (don't want to install misc ROMs).
Xposed for oukitel 6000plus root
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
no xposed for k6000 plus
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
sorry latest xposed is for sdk 25 and the latest firmware for this device is android 7.0 (Sdk 24)
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
I have tried many random things; I forgot the details of it. The versions are not a problem; there are links around to download old installers. Even if latest Xposed is for Android 25, archives will let you download v24.
It also depends when you rooted your phone, and which updates you did on your ROM before rooting. Depends if you are using ROM v6, v9, or v18 ...
Also, even if Xposed is installed, it's not working properly; in particular, I wanted Xposed to NotifyClean, and this plugin could not be installed on the Xposed I have (download goes fine, but plugin complains I need reboot to activate it). So, in short, Xposed is useless for me for now. Some other plugins have installed correctly (Taskbar).
The Xposed I have NOW is version 87 by PurifyOS. ATM, Android API 24.
But I said I tried many random things, so, maybe having tried to installed other variations of Xposed by other people was important to have this one installed. I remember that at some point, trying to install this one (purify) failed, and then, worked later ... forgot why.
Error
When you try to upload a TWRP, a message pops up:
"error: cannot load 'recovery-twrp31jemini.img'"
Bootloader should be unlocked. I see a buzz when switching on "yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds"
Phone has a ROM v18
Application procedure on W10.
Does anyone find any solution?
You don't need to burn TWRP in FLASH to be able to use it. You just need to load and run it, this way:
fastboot boot recovery_TWRP-3.1.0.img
This way, if you have backup your whole phone, or downloaded and extracted a ROM, you can boot a stock recovery image:
fastboot boot /tmp/recovery-verified.img
According to your name jemini ... I thjink you have downlaoded the wrong TWRP. Boot and flash may fail if you grabbed a file for an other phone.
This should be ROM independant.
Since I rarely use TWRP, I now keep the stock recovery, and run TWRP from fastboot only when I need it; this way, stock recovery is available for Android updates.
Do you have links to ROM v18, so that I can download and install it directly, instead of having to burn v6, then update to v9 and v18 via update process ? I have issues with updates, and would like to flash directly using v18; but could not find a download link.
I got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) Start unlock flow
OKAY [ 14.791s]
finished. total time: 14.792s
Problem is now:
Orange state
Your device has been unlocked and can't be trust
Your device will boot in 5 seconds.
But it's not booting, just stuck at this screen.
Any help very much appreciated!
EDIT:
I was on V23 ROM which came per OTA.
EDIT-2:
I was able to flash it back to V23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
rom
"Custom Rom Doogee Shot (FreemeOS) :
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!""""
What do you say that this rom picks up on the oukitel k6000 plus ??
I need someone to help me my k6000 plus did not call any more after this procedure.
when I install the rom stock by flash sp this error appears
https://drive.google.com/file/d/0ByEkRDgYmbWtOXdpbngtcGJxQk0/view?usp=sharing
What do you want to do?
Flash the Stock ROM back with flashtool?
You should switch to "Download Only" and not "Firmware Upgrade".
Also the Download Agent was different when I flashed it, it was DA_PL.bin.
cojo11 said:
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Click to expand...
Click to collapse
SIVAKUMAR: yes my mobile also same problem ...boot loop please help me oukitel k6000 plus MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
sivakumarindia said:
SIVAKUMAR: yes my mobile also same problem ...MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
Click to expand...
Click to collapse
SIVAKUMAR: I THINK THIS ROM DIFFERENT MT6750 AND MT6750T:crying:
---------- Post added at 11:19 AM ---------- Previous post was at 11:14 AM ----------
rolex0815 said:
i got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) start unlock flow
okay [ 14.791s]
finished. Total time: 14.792s
problem is now:
orange state
your device has been unlocked and can't be trust
your device will boot in 5 seconds.
but it's not booting, just stuck at this screen.
Any help very much appreciated!
Edit:
I was on v23 rom which came per ota.
Edit-2:
I was able to flash it back to v23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
Click to expand...
Click to collapse
sivakumar: My mobile also same condition boot loop
I got the same and this help me :
For this case, leave SP tool setting as normal. Before connect USB to device:
1. Press and hold vol +
2. Connect USB to device and hold vol + button.
3. Just release the button until you see the download process start working.
with this solution i have Flaht the v6 rom
Boot loop try this Back to STOCK ROM
Cheese-ass said:
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
BTW Sorry for my bad English XD
Click to expand...
Click to collapse
SIVAKUMAR INDIA: BOOT LOOP TRY THIS BACK TO STOCK ROM OUKITEL K6000 PLUS MT6750T
----------------------------ERROR BOOT LOOP -------------------------------------------
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
---------------------------TRY THIS STEPS RECOVERED STOCK ROM--------------------------
step1: Vcom+SPD+and+adb+driver+Installer+Windows+8_10
INSTALL DRIVERS
step2; SP_MDT_v3.1732 (DOWNLOAD )
EXTRACT AND RUN SP-MDT FLASH ,
SCAN ---------CONNECT MOBILE------FLASH SUCCEED----
step3: OUKITEL_K6000_Plus_V23_20170726
THIS LINK AVAILABLE OLD VERSION SP_MDT ONELY SEARCH AND DOWNLOAD NEW VERSION SP_MDT_v3.1732
LINKS: https://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html
Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.
Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.
does anyone have a scatter file or custom recovery for this phone? how did you root?
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip
aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms
Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s
What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img
i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied
Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?
Use an app from google play called Device Info HW
Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)
Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).
Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.
In gt1x its because of this:
So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.
And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.
aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance
please do a read back for boot.img and recovery.img with SP Flash Tool
Actual Firmware https://onedrive.live.com/?authkey=!APMSxpd_UoEEQBY&id=A120532B51026BDA!1816&cid=A120532B51026BDA
Unlock Bootloader https://rootwrp.com/unlock-teclast-t20-bootloader/
and flash with
fatboot flash boot +file
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This is for the new teclast t30 tablet? can you make a video?
Yes Brand New
https://www.youtube.com/watch?v=G4uuLCjBWrs&feature=youtu.be
Video is About Patch/flashing Bootimage with Magisk Manager(Tablet is already rooted)
hello
successfully root new T30 with patched boot.img (with magisk).
I have unlocked bootloader with "fastboot flashing unlock" but now, have a message on boot screen and have to wait 5s more for boot
is there any way to bypass this message and 5s pause ?
there is a TWRP 3.3.1 on 4pda by nemo-nemo and helpers, but touchscreen don't work for me
Unlocked Bootloader cause this warning on Boot(Power Button should override the 5 secs Pause)
Dont using the recovery i dont know
Here is TWRP 3.3.1 for T1P2 (T30):
https://drive.google.com/file/d/1RW5ek_FIAMe_8KvRWpNE_l7wi8qNxmUS/view?usp=sharing
Thx to nemo-nemo on 4pda.ru
Hello,
I can confirm TWRP work fine but you have to use a USB-OTG mouse
The 1st time you boot on TWRP, you have a encryption code request, choose "cancel"
To disable force encryption, flash "DisableForceEncryption_treble" zip with TWRP
When you unlock bootloader of this T30, you have warning message and 5s wait to boot
There is a tweak to bypass this:
download script "orange_state_disabler" zip and flash it with TWRP
this script is fully safe, there is a compatibility test and don't flash if it can't.
Thx to XopmoH97 from 4pda.ru
Download from here: https://drive.google.com/drive/folders/1tSInU_vOFZAfpdbc1bETAuIJsniQqjUd?usp=sharing
edit*
TechGuru123 said:
there is a newer firmware for this tablet
T30(T1P1)_Android 9.0_V1.04_E43D.rar
https://pan.baidu.com/s/1sjEt1jxEOz...arentPath=/sharelink491465238-972273915700760
password
1f9r
Click to expand...
Click to collapse
What's your source ?
Have you verify this firmware ?
T30 is T1P2, not T1P1.
Look at your ID on tablet's backside: T1P2
Go to Teclast website firmware and search for
T1P1: unknown
T1P2 -> T30
Verify and test before publish, please
edit*
My PC can't find any T30 fastboot devices... which drivers use ??
Search for "MTK_USB_All_v1.0.8" on google
Is there no way to root without unlocking the bootloader first?
kestrelv2 said:
Is there no way to root without unlocking the bootloader first?
Click to expand...
Click to collapse
Unlocking bootloader is useless for 90% of users
Why ?:
- Only for fastboot commands
- Unlocking bootloader avoid warranty
You can do lot of things without unlock:
- Install TWRP (with Upgradetool)
- Install custom system, logo, boot, etc ... with upgradetool
and
You can root without unlock:
- Download firmware (T1P2) from teclast website and unpack in PC folder, ex: "T30_firm".
- Download and install "MTK_USB_All_v1.0.8" for MTK drivers (search on google)
- Connect your T30 to PC with usb
- In "T30_firm/firmware" folder, copy "boot-verified.img" to you T30
- Install magisk manager on your T30 an launch it
- Choose install magisk by "patch a file", choose your "boot-verified.img" and wait
- Now, you have a "magisk-patched.img" file in download folder
- Copy "magisk-patched.img" on your "T30_firm" folder PC
- Launch "Upgrade tools.exe" in "T30_firm/upgrade tool" folder
- Unselect all "img" files
- Select only "boot" line and choose your "magisk-patched.img" (click on same line, "location" column)
- Shutdown your T30 (allways connected to pc)
- Clic on "download" in upgrade tool and wait for big popup with green "V"
You can disconnect you T30 and boot.
Open magisk manager, "tada !" magisk is ready
murigny64 said:
Unlocking bootloader is useless for 90% of users
Why ?:
- Only for fastboot commands
- Unlocking bootloader avoid warranty
You can do lot of things without unlock:
- Install TWRP (with Upgradetool)
- Install custom system, logo, boot, etc ... with upgradetool
and
You can root without unlock:
- Download firmware (T1P2) from teclast website and unpack in PC folder, ex: "T30_firm".
- Download and install "MTK_USB_All_v1.0.8" for MTK drivers (search on google)
- Connect your T30 to PC with usb
- In "T30_firm/firmware" folder, copy "boot-verified.img" to you T30
- Install magisk manager on your T30 an launch it
- Choose install magisk by "patch a file", choose your "boot-verified.img" and wait
- Now, you have a "magisk-patched.img" file in download folder
- Copy "magisk-patched.img" on your "T30_firm" folder PC
- Launch "Upgrade tools.exe" in "T30_firm/upgrade tool" folder
- Unselect all "img" files
- Select only "boot" line and choose your "magisk-patched.img" (click on same line, "location" column)
- Shutdown your T30 (allways connected to pc)
- Clic on "download" in upgrade tool and wait for big popup with green "V"
You can disconnect you T30 and boot.
Open magisk manager, "tada !" magisk is ready
Click to expand...
Click to collapse
Ill give it a try thanks.
It worked, thanks a bunch!!!
When I turn off the T30 and press download, nothing happens anymore. I tried it on both Windows 7 and Windows 10. Just nothing. I'm waiting 10 minutes, then I'll put a stop and i'm done. No change. Does the tablet really have to turn off? Otherwise it's very well described, I think I'm making a mistake somewhere, I just don't know where.
Zuzzana
Try press "download" first and then, power off
zuzzana said:
When I turn off the T30 and press download, nothing happens anymore. I tried it on both Windows 7 and Windows 10. Just nothing. I'm waiting 10 minutes, then I'll put a stop and i'm done. No change. Does the tablet really have to turn off? Otherwise it's very well described, I think I'm making a mistake somewhere, I just don't know where.
Zuzzana
Click to expand...
Click to collapse
For me these mtk tools only do anything when i plug into a certain usb port. I couldnt find one that worked on my desktop pc but on my laptop its the usb 2.0 slot that worked and not either of the usb 3 slots. Turn it off click download and then plug in the tablet and it should start assuming you have properly installed the needed drivers.
Thank you, thank you, thank you. It just wanted to press download first and then plug it into USB. Thanks again.
Zuzzana
WARNING !!
Don't flash chinese firmware mentioned above by @TechGuru123
This firmware erase all your partitions,your NVRAM and IMEI
You will lose IMEI and it's hard to recover !