Dear XDA,
I have had a Tudou 91 D1 for over a year, and i tried every rooting method. (one click root, srs root, etc) I tried looking for roms but there is little on google about this phone, and nothing on xda. It is a good phone, very happy with it, but no roms. Is there any rom that could be tweaked to work on my phone? I checked about rom porting and creating a new rom via kitchen but all those require a rom for my phone, and a rom i want to change. The problem is i got nothing for my phone.
ALPS Tudou91 D1
quadrant standard review
4.2.1 Jellybean
ID: JOP40D
OS Version:3.4.5
dalvik: 1.6.0
Model:Tudou91 D1
Product/board: ratech89_we_rlk_jb2
ARMv7 Processor rev 2 (v7l)
1.2ghz
4 cores
architecture 7
bogoMIPS:2439.94
MT6589
revision 2
serial: bunch of zeros
total memory:995912 kb
540x960
5'3 in
240 dpi
51.02 fps or refresh rate
PowerVR SGX 544MP
OpenGL ES 2.0
bootloader: unknown (although when i boot into recovery "volume up + power" it shows no command, hold volume down + power, and i get into "Android system recovery <3e>") and its yellow, if that helps lol
http://www.cheapunlockphone.com/?p=1688 <--the phone
if it helps, i extracted launcher apk and it had something like s3 launcher.
Thank you very much!
First off, try to see if the manufacturer provides existing firmware on their website. It would be ideal if you can get that. If there is one, then that would be your backup.
Now the next step towards rooting is to either use z4root or try to inject the root into the stock firmware and then flash it yourself. You may also use this guide to enhance it further.
Now supposing you do not find a Stock firmware by the manufacturer, there is a way to backup the current stock firmware on the phone. At least for most of the phones. Here's a nice Guide on how to do so. I am aware its for a different phone. But it will give you ideas and pointers.
FYI on SRS page they say your phone is supported. So Try These steps
1. Use USBDEVIEW to uninstall any usb devices that look like they may be your phone.
2. Download the Universal Drivers from here http://hexamob.com/drivers-smartphone-tablet/tutorial-universal-adb-driver-koush/
3. Once you have your phone installed with the proper drivers and can access ADB via cmd (if you need adb tool search the forms) download the srsroot and run it.
Like i said in the first line Your Phone is Supported by SRS root. Once you have root back up your phone. Back up your WHOLE phone not just system and data. Everything. Once you have a good backup. start playing. If you just want to use some simple mods install xposed. If you want a custom AOSP rom u will prob have to build it your self.
Have fun!
I will try! i think i messed up somewhere with adb, when i tried srs root. does srs root need adb drivers? if so, then that was my problem.
messed up
Perseus71 said:
First off, try to see if the manufacturer provides existing firmware on their website. It would be ideal if you can get that. If there is one, then that would be your backup.
Now the next step towards rooting is to either use z4root or try to inject the root into the stock firmware and then flash it yourself. You may also use this guide to enhance it further.
Now supposing you do not find a Stock firmware by the manufacturer, there is a way to backup the current stock firmware on the phone. At least for most of the phones. Here's a nice Guide on how to do so. I am aware its for a different phone. But it will give you ideas and pointers.
Click to expand...
Click to collapse
I just tried this method, followed your steps, and srs root results:
10:11:58 AM [+] Testing exploit: root4b (please wait..)
10:12:05 AM [+] Device Reboot #1 (Wait till it's started)
10:13:27 AM [+] Device Reboot #2 (Wait till it's started)
10:14:41 AM [+] Remounting /system Filesystem as R/W..
10:14:41 AM [+] Installing SU Binary...
10:14:41 AM [+] Installing SuperUser APK...
10:14:42 AM [+] Remounting /system Filesystem as R/O..
10:14:48 AM [+] Rooting Complete !
I cant find the superuser app, and i checked with root checker pro if i had root, and it says that the device is not rooted.
root checker pro:
superuser application- is not installed!
SuperSU application- is not installed.
analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
I found the file in system/bin/su but i dont know how to execute it.
also to top things up, when i tried srs root option for gesture lock, it said this
10:33:43 AM - Starting ADB Server..
10:33:48 AM - Manufacturer: alps
10:33:48 AM - Model: Tudou91 D1
10:33:48 AM - Android Version: 4.2.1
10:33:48 AM - Build ID: Tudou91_D1_V1.0
10:33:48 AM - Board ID: ratech89_we_rlk_jb2
10:33:48 AM - Chipset Platform:
Device is not rooted, To use this function you need to root it first...
its messed up
Have you tried the steps I had mentioned ?
Hello,
After looking at your thread we have decided to close it. XDA assist is here to help users learn their way around XDA. It is not here to fix issues for users. Please have a look at the goals of the forum:
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Click to expand...
Click to collapse
As there is no dedicated forum available for your device, the best we can offer is to create a thread in: Upgrading, Modifying and Unlocking section in the general forum. Other users on XDA may be able to help you there. If you can provide as much detail on your device as possible and the steps you have taken so far it will help.
We do hope you can get your issue resolved.
Many thanks,
Ghost
Forum Moderator - XDA Assist forum.
Related
this is a work-in-progress development project for porting ClockworkMod Recovery 5 to Ingenic JZ4770/JZ4760 tablets.
this is not perfect at all. and I'm very busy. progress will be very very slow. I may not be able to answer your question/request. if you have some idea for improvement, please do it freely.
there is no support from any makers/vendors. you must agree all risks by installing non-supported files, it may brick your tablet, and you may lose official support/warranty.
* YOU MUST READ CAREFULLY POST#1, #2, AND #3!
* DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW. IT WILL BRICK YOUR TABLET!
* project page
http://androtab.info/mips/ingenic/clockworkmod/
* supported tablets
ainol NOVO7 Basic and Paladin
Velocity Micro Cruz T100 series (Android 2.2 updated model and Android 2.0 PT701i model)
Velocity Micro Cruz T301
ronzi A3
* changelog
refer git log
* resources
http://developer.mips.com/android/
https://github.com/naobsd/cm_bootable_recovery/compare/ics...ics-mips-naobsd
https://github.com/naobsd/mips_build/compare/mips-ics-mr1...mips-ics-clockworkmod
https://github.com/naobsd/mips_external-busybox/compare/ics...ics-mips
* How to install ClockworkMod Recovery 5 (for ainol NOVO7 Basic/Paladin, Cruz T100 series, Cruz T301)
1. download recovery-signed.zip for your tablet (DO NOT USE FILES FOR OTHER TABLETS!)
2. (if you are using stock recovery)rename it to update.zip, then put it on root of SD card
3. install update.zip from recovery
on stock recovery, update.zip will be installed automatically. on ClockworkMod Recovery, you need to select menu item manually.
* How to install ClockworkMod Recovery 5 (for ronzi A3)
1. download recovery.zip for your tablet (DO NOT USE FILES FOR OTHER TABLETS!), then extract recovery.cpio.img from it
2. make backup of stock recovery
Code:
adb remount
adb shell mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
3. copy recovery.cpio.img into your tablet, then flash it
Code:
adb shell inand_flash_image recovery recovery.cpio.img
* How to boot recovery
push & hold VOL+ while power on
* How to boot recovery (alternative)
Code:
adb reboot recovery
*How to control ClockworkMod Recovery 5
VOL-/HOME: down, VOL+: up, POWER/MENU: select, BACK: back
* Superuser, su, and busybox
it can be installed from ClockworkMod Recovery 5
- Superuser, su, and busybox for JZ4770 ICS
- Superuser, su, and busybox for JZ4760 Froyo
* random notes
- stock recovery
if you installed update.zip from stock recovery, stock recovery image should be renamed as /system/recovery.cpio.img.bak. (unless you didn't remove /system/recovery.cpio.img)
it can be flashed by "inand_flash_image" command. (use "flash_image" command for T100 series except PT701i model)
- mbr, xboot, boot, and recovery areas
backup/restore doesn't work for mbr, xboot, boot, and recovery areas
- time for reboot/poweroff (NOVO7 Basic)
I don't know why but reboot/poweroff take long time (as same as stock rom). you should wait 1 minute. if nothing is happened in 10 minutes, use reset hole
for now I'm preparing to push my changes to github. I'm very busy so it needs some time.
if you made some.zip file to do something for MIPS Android (e.g. superuser.apk with su binary for MIPS), please tell me. I'll add link to post#1.
if you have some idea for next work, please tell me too. (but, as I wrote, I may not be able to answer your request. sorry)
Thanks for your starting thread and project.
I bought a Advanced model but they send us a Basic Novo7.
All we know the incompatibilites using a cpu MIPS, that doesnt allow to run a lot of Android software that for default its compiled for ARM processors.
Im getting a bundle pack of apps running under our device.
Kashamalaga said:
Thanks for your starting thread and project.
I bought a Advanced model but they send us a Basic Novo7.
All we know the incompatibilites using a cpu MIPS, that doesnt allow to run a lot of Android software that for default its compiled for ARM processors.
Im getting a bundle pack of apps running under our device.
Click to expand...
Click to collapse
thank you. I understand your condition.
but here is dev thread for clockworkmod for novo7 basic. if you want to talk about apps which support mips android and/or any general things about novo7b, I recommend you to make new thread for it.
fun_ said:
thank you. I understand your condition.
but here is dev thread for clockworkmod for novo7 basic. if you want to talk about apps which support mips android and/or any general things about novo7b, I recommend you to make new thread for it.
Click to expand...
Click to collapse
I will do as you said
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Also here SHOULD be a working SU for MIPs. It work's on the cruz tablets
vanduhl said:
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Click to expand...
Click to collapse
I couldn't read what you did exactly. if you flashed my image w/o modification, it must not work. as I wrote, DO NOT USE file for other tablet.
please explain what you did, and please explain detail about your tablet before any random work.
fun_ said:
I couldn't read what you did exactly. if you flashed my image w/o modification, it must not work. as I wrote, DO NOT USE file for other tablet.
please explain what you did, and please explain detail about your tablet before any random work.
Click to expand...
Click to collapse
Attempted using the above stated method(understanding you said DO NOT US file on other tablet) I was curious to see as what kind of error would or may of come up. I'm interested in modifying this for the Velocity Cruz T301 tablet(running a JZ4760 processor) as that community of tablet users has been left under the dust. Now with the novo coming out it will further pile under the dust. I have not yet made any modifications to it, although I would very much like to.
vanduhl said:
Attempted using the above stated method(understanding you said DO NOT US file on other tablet) I was curious to see as what kind of error would or may of come up.
Click to expand...
Click to collapse
kernel must not work because it's for NOVO7B. in general, kernel can't be shared among different products.
key assign, and partition layout may be different too. but currently I have no idea how to fix them because I don't have any detail about your tablet...
http://en.ingenic.cn/product.aspx
it seems JZ4760 is NOT MIPS32R2. then I need to recompile userland binaries.
anyway, technical detail is required to support other tablets.
http://bbs.imp3.net/thread-10520163-1-2.html
it seems source code for xboot, android 2.2 and (part of?)kernel source for NOVO7B is released. I don't try to compile them yet so I may be wrong.
I'll check them later.
Is it possible that someday this recovery will be also ported for ainol novo7 Advanced ?
endrju100 said:
Is it possible that someday this recovery will be also ported for ainol novo7 Advanced ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1378594
you should use search engine before post a question.
vanduhl said:
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Click to expand...
Click to collapse
How did you get back to your stock recovery image on the T301? I think I borked mines on a T105 accidentally with ROM Manager. I accidentally pressed the screen too many times while 'exploring' and the delayed input caused ROM Manager to start flashing a recovery. Now I can't boot into recovery. I just see black nothing.
EDIT:
Disregard - My stock recovery boots. I was performing the boot into recovery procedure incorrectly. Also, because the recovery.cpio.img was in /system I assume it was flashed on each power cycle.
Apologize: I have read the complete topic and now understand that at present it is only for Novo.
Please dont use this thread to talk for another devices that arent be Novo7 Basic.
Asi cant start a new thread yet, here is my thread at spanish forum comunity with a full starter packs of mips app + games and a guide to be root.
htcmania. co m/showthread.php?t=303749
I´ve got successfully get a compiled MIPS version of Titanium backup that works like a charm for our device Novo7 Device! Checkout at the link upside.
Regards. (I will open a new thread when i´ve got 50 messages...)
fun_ said:
it seems source code for xboot, android 2.2 and (part of?)kernel source for NOVO7B is released. I don't try to compile them yet so I may be wrong.
I'll check them later.
Click to expand...
Click to collapse
what other info would you like?
Rooting Guide for any Android Device
Code:
*Your warranty is now void
*I absolutely disclaim all responsibilities
*I am not responsible for bricked devices, since rooting is by your own will and not mine
*You point the finger at me for messing your device up, I will laugh at you
Prerequisites
- Drivers for your phone installed on PC
- USB Debugging ON and Unknown Sources Checked
- Knowledge of your Mobile's Android Version ( e.g 4.0.4 or 4.1.1 )
What is rooting?
Click Here
Pros and Cons of Rooting an Android
Pros
- Total Control over CPU Frequencies ( Under/Over clock )
- Install Stock Based Custom ROMs
- Remove Rubbish from System files
- Custom Recovery like CWM or TWRP
- Install tweaks to speed up and improve your phone ( e.g. Crossbreeder, Supercharger )
- Terminal Emulator control
- Duh! Root Access
Cons
- Your warranty may be voided
- If done wrong may result to a bricked device or bootloops
- If you overclock the device too often the battery life will deteriorate
So should I root my Android?
That is completely up to you. Rooting is for those who want to explore Android and really experiment on their phones on what to install and what not to,
Methods
There are many ways to root your Android Mobile. This guide will sum it all up in a clean and orderly manner for convenience
1) Rooting through "One Click Applications"
UnlockRoot and SuperOneClick are famous and are known to root and have rooted many devices ranging from Android 2.3 - 4.1
The Simplest way to root Android devices, and Easy As ABCs
1) Connect Phone ( USB Debgguging on, Drivers Installed )
2) Press Root Button ( Some devices need to be Shell Rooted first )
3) Wait for reboot prompt and click yes
FAQ
My device isn't detected, What should I Do?
Install Pdanet and it will detect what phone drivers to install to your PC, just select your phone brand or if your phone brand is not on the list
select Other Brands
Failed to Root? WTF!
Calm down, there are more ways on how to root,
Through In-Mobile Apps
For Android 2.2 below rooting is made easier by an app called "Universal Androot", very simple, no drivers required, no PC required just install the APK on your phone and press Root
Another alternative to Universal Androot is z4root
For Android 2.3 - 4.3
Some devices vulnerable to exploit rooting can be rooted via "Framaroot", Just press the exploit mode below the SU management app ( You may even choose whether to install SuperSU or Superuser ) and voila your rooted
Root through kernels
Well if your mobile's bootloader is unlocked, Most kernels have auto root function which roots your phone with the latest SU and just flash the Kernel via ODIN or Flashtool through fastboot and your rooted
* This requires Unlocked Bootloader
Rooting Manually ( No Apps or whatsoever )
If the tricks above variably failed there is one last, method. Rooting the phone Manually
Click Here for Unlocked Bootloader
Click here for Locked Bootloader
This requires sufficient amount of knowledge with ADB commands and the like
If your device was rooted Congratulations, You are now really using Android Like A Boss!
Please consider hitting thanks :good: ! Happy to help
*bump
Thanks for your work.
Thanks
love it, especially the insecure boot image tutorial!
Great Guide :good: will do better with some screenies but it will do thanks
*bump Some Devices ( 4.4 ) can't be rooted via Unlock Root
Will be updated with ss soon
@Revontheus
If I may suggest, please add Kingo root too "One-click apps", there's also eroot for xperia 2011 devices to "One-click apps"
Then here's the rising superstar by shuame download link: http://www.shuame.com/en/root/ under "one click apps"
Hope this helps
Thanks will add that
Benifits
What are benifits of rooting android ?
komalshres said:
What are benifits of rooting android ?
Click to expand...
Click to collapse
See OP. Pros are written there.
theres custom recovery
custom roms
root browing
delete and install any system app
run scripts on kernels with init.d support
custom kernels (overclock and otg possibilities etc)
custom baseband
better ram management
swap partition
link2sd
if u want more, just search xda or google
hope this helps
I seriously believe this thread needs more upvotes.
BTW I wish to link to this thread in my new thread Hope you can update OP with SS and add more roting options.
Rooting Guide for any Android Device
Code:
*Your warranty is now void
*I absolutely disclaim all responsibilities
*I am not responsible for bricked devices, since rooting is by your own will and not mine
*You point the finger at me for messing your device up, I will laugh at you
Prerequisites
- Drivers for your phone installed on PC
- USB Debugging ON and Unknown Sources Checked
- Knowledge of your Mobile's Android Version ( e.g 4.0.4 or 4.1.1 )
What is rooting?
Click Here
Pros and Cons of Rooting an Android
Pros
- Total Control over CPU Frequencies ( Under/Over clock )
- Install Stock Based Custom ROMs
- Remove Rubbish from System files
- Custom Recovery like CWM or TWRP
- Install tweaks to speed up and improve your phone ( e.g. Crossbreeder, Supercharger )
- Terminal Emulator control
- Duh! Root Access
Cons
- Your warranty may be voided
- If done wrong may result to a bricked device or bootloops
- If you overclock the device too often the battery life will deteriorate
So should I root my Android?
That is completely up to you. Rooting is for those who want to explore Android and really experiment on their phones on what to install and what not to,
Methods
There are many ways to root your Android Mobile. This guide will sum it all up in a clean and orderly manner for convenience
1) Rooting through "One Click Applications"
UnlockRoot and SuperOneClick are famous and are known to root and have rooted many devices ranging from Android 2.3 - 4.1
The Simplest way to root Android devices, and Easy As ABCs
1) Connect Phone ( USB Debgguging on, Drivers Installed )
2) Press Root Button ( Some devices need to be Shell Rooted first )
3) Wait for reboot prompt and click yes
FAQ
My device isn't detected, What should I Do?
Install Pdanet and it will detect what phone drivers to install to your PC, just select your phone brand or if your phone brand is not on the list
select Other Brands
Failed to Root? WTF!
Calm down, there are more ways on how to root,
Through In-Mobile Apps
For Android 2.2 below rooting is made easier by an app called "Universal Androot", very simple, no drivers required, no PC required just install the APK on your phone and press Root
Another alternative to Universal Androot is z4root
For Android 2.3 - 4.3
Some devices vulnerable to exploit rooting can be rooted via "Framaroot", Just press the exploit mode below the SU management app ( You may even choose whether to install SuperSU or Superuser ) and voila your rooted
Root through kernels
Well if your mobile's bootloader is unlocked, Most kernels have auto root function which roots your phone with the latest SU and just flash the Kernel via ODIN or Flashtool through fastboot and your rooted
* This requires Unlocked Bootloader
Rooting Manually ( No Apps or whatsoever )
If the tricks above variably failed there is one last, method. Rooting the phone Manually
Click Here for Unlocked Bootloader
Click here for Locked Bootloader
This requires sufficient amount of knowledge with ADB commands and the like
If your device was rooted Congratulations, You are now really using Android Like A Boss!
Please consider hitting thanks :good: ! Happy to help
This thread shall strive to be an all-in-one thread for the phone O+ 8.31z. And to be noob friendly as well. As of now, I have only very limited knowledge so I'll be adding stuff as I go.
Phone Specs:
CPU: MT6572 1GHz Dual-Core
Architecture: ARM Cortex-A7
Clock Speed: 598 MHz - 1.00 GHz-----
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
UBIFS File system
Android: 4.2.2
Kernel Architecture: armv7I
Default Governor: Hotplug
Screen Res: 320x480
Density: 160dpi
RAM: 219MB
Internal Storage: 0.16GB
Sensors: Proximity, Light, 3-axis.
Click to expand...
Click to collapse
For drivers, connect your phone to windows PC, download PDANET (search for it on google) and let it install drivers for your phone.
Preface: TOOLS and THREADS TO BE USED
1. MTK Droid Root and Tools by xda senior member rua1. Press thanks in his thread! Compatible with Windows and Linux(with wine).
2. SP Flash Tool Credits to Khonshu of china.phonearena. I downloaded v3.1344. Here's an xda thread on what you can do with it: Click Me! Troubleshooting SP flash tools: .Click here!
3. Pdanet for Windows drivers
Chapter 1.0.0: HOW TO ENABLE PHONE MODES
Steps:
1.1.0 For MTP mode
1.2.0 For ADB mode
1. Go to Settings>About Phone
2. Click Build number about 6 times, quickly. Developer Options should now appear.
3. Go back to settings then click Developer Options. Here you find so many things you thought didnt exist
4. For now, we only check USB debugging. When a pop-up appears, just click "ok". Done!
1.3.0How to enter recovery mode: (Credits to phcorner.com O+8.52 thread)
Method 1:
1. Remove battery and reinsert.
2. Press Volume Up and power key simultaneously.
3. A blank screen with an android lying down and a red exclamation triangle should appear now.
4. Press Power button once, and the menu will appear.
5. To navigate, Power: Show/Hide options. Vol UP: Confirm. Vol Down: Scroll.
6. When done, reboot system to exit.
Method 2: When you're on a PC,
1. Connect Phone in USB debugging mode.
2. Open cmd (or terminal then change directory to your adb folder) and
Code:
adb reboot recovery
1.4.0 For Phone test mode
1. Press Volume Down and Power simultaneously.
2. Choose among the options.
3. When done, remove battery to exit.
(It seems like reinserting the battery and doing VolDown+Home combo does not do anything else)
1.5.0 For fastboot (aka bootloader) mode
Requirements: Since you want to use fastboot, then you must be on an adb configured computer
1. Open cmd (or terminal then change directory to your adb folder)
2.
Code:
adb reboot bootloader
3. Wait for the phone. Done!
Chapter 2.0.0: ROOTING
Why root?
There are many methods to rooting. I will list what I know might work. I'm 99.9% sure the first one works (given you are not stuck in a bootloop.)
2.1.0 Shuame ROOT GeniusDownloadInfo: This is a one-click PC application. I have used this in Windows 7 32-bit and in lubuntu 13.10 and it works. If your phone is not an MT6572 I'd still recommend that you try this as it can root almost anything! It installs Kinguser as the superuser app.
2.1.1 Requirements for Windows PC: A Windows PC, a USB cable, your phone, and a fully downloaded shuame root genius. No drivers needed as shuame root genius already installs them for you.
2.1.2 Requirements For Linux PC users: A linux PC, a USB cable, your phone, a fully downloaded shuame root genius, WINE, and adb (I might be wrong here, but get this: Since drivers are not really used, we need our phone to be given adb permissions by linux, or else shuame will not be able to recognize your phone. So you will probably need to have adb installed first, just to be sure.)
For info on how to do that, check here: Click Me!
Also, shuame root genius does not display well under wine in my case, but the buttons were clickable anyway so it still works. From here, it's pretty much the same procedures.
2.1.3 Steps:
I made a visual guide here:
And in text, here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open Shuame Root Genius. It will connect to your phone automatically and install drivers for about 3-5 minutes. (No more driver installation on linux PCs)
6. Click "Root it". You should now see your device as rooted. And if you click back, you can unroot. Done!
2.2.0ErootDownload/help threadInfo: Another tool by Chinese developers. I tried it on my lubuntu 13.10 WINE and it worked flawlessly! I'm pretty sure it'll work on a Windows PC as well. It installs superuser by clockworkmod.
2.2.1 Requirements: See 2.1.1 and 2.1.2.
2.2.2 Steps:
Visual guide
Textual guide here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open eroot. It will connect to your phone automatically.
6. Click the root button. It's the only button anyway. When you have rooted successfully, you can click the 解除 button to unroot if you wish. Done!
2.3.0 MTK Droid root and tools
Connect Phone in ADB and MTP mode.Download/Help thread can be found in PrefaceRun MTK Droid Tools. Wait for it to recognize and establish a connection with your phone. This should appear after a minute:
Take note that a blue rectangle on the lower left means you're still not rooted. Press ROOT.
Wait for about three to five minutes. In my case, MTK Droid tools crashed So I didn't see a superuser app.
But I downloaded root checker and sure enough, my phone was rooted. Only the superuser app was missing.
I also opened MTK Droid tools again and saw a green rectangle (which means I am rooted :victory: )
So now, technically, you are rooted. But we still need a superuser app, so I downloaded a superuser app that I liked and updated the binary. I downloaded SuperSU by chainfire from the play store. Done!
or, you could try the superuser button in the root, backup, recovery tab. I didn't try it though
2.4.0 Other stuff you might wanna try or know about if none of these methods worked for you, here: http://forum.xda-developers.com/showthread.php?t=2523814
Chapter 3.0.0: RECOVERY STUFF
3.2.0 How to backup stock recovery
3.3.0 What is clockworkmod recovery?
3.4.0 What is carliv touch recovery?
UPDATE: I think O+ 8.31z was primarily sold for the Philippine Market; as such, I may be in competition with more Philippine based forums such as symbianize and gsmworldfive. Therefore, I think it would be best that I leave the two 8.31z links here and discontinue any plans on improving this thread. Here they are:
http://www.symbianize.com/showthread.php?t=1094034&page=10
^this link contains a SPFT flashable pre-rooted clean stock rom.
http://www.gsmworldfive.com/forum/showthread.php?t=37787
^this link uses the SPFT method too, but the rom here has much more root apps installed already, like swapper, greenify, auto ram cleaner etc. (Oh, stock keyboard was also taken out).
Both confirmed working to bring back a bootlooped 8.31z. I prefer the first one though
Until next time! My dad plans to sell this phone soon so I guess I won't be learning how to make custom roms anytime soon yet... Hope you guys are doing well
Click to expand...
Click to collapse
UPDATE: Since my dad hasn't sold it yet, I'm playing with it again. There is a Filipino facebook group that is dedicated for 8.31z users. I think they have custom roms ported there.
Click to expand...
Click to collapse
Chapter 4.0.0: ADD INIT.D SUPPORT TO STOCK ROM
Check here! http://forum.xda-developers.com/showthread.php?t=1933849
I haven't personally tried any one yet. You are always proceeding at your own risk
Tweak for speed, battery life, and other cool/useful stuff.
Chapter 5.0.0: Speed
There are tons of stuff to speed up your phone, and they're not just limited to one specific phone. So bring in the list.
1. Use Greenify (find it in the play store)
Requirements: Root (optional for auto-hibernation. Highly Recommended.), Android 4.0+
You may greenify stuff like Guardian if you are not using it, or maybe the FB app too. Saves some battery and gives a little free ram for better multitasking.
2. Disable fancy window animations and transitions
Go to settings>developer options and disable the three animation options to animation off.
3. Use a cpu controller like No Frills CPU control (find it in the play store)
Controls how fast or slow you want your CPU to go. Default Governor is hotplug.
For a faster phone, set the governor to performance. It sets the CPU to scale to the max that you set. Use when you are playing heavy games.
For a battery saving phone, set the governor to powersave. It sets the CPU to scale to the min that you set. Use when you only plan to use really light apps.
For a balance between performance and battery save, it's probably best to go back to hotplug since it can turn the second core on or off depending on your usage.
4. Tweaks and Scripts
Info: Tweaks refers to build.prop tweaks. Scripts refer to init.d scripts. So this is a two-part thing. Adding build.prop tweaks, and running init.d scripts. Some do this two-part thing simultaneously in one flasher. Others, separate the tweak part from the script part. The reason they do this is because phones running from stock usually do not support init.d scripts, but only build.prop tweaks.
Our 8.31z cannot support init.d (yet) so for now we will only do the tweak part.
1. Tweak part of [ SCRIPT | TWEAK ] ◢ Project Fluid™ ◣ by Spex. [size="+1"]Recommended.[/size]
Please press thanks in his thread! This is not my work.
Project Fluid has a separable tweak part. I didn't apply all as some are optional. So I just applied it and what happened?
Using Antutu X Benchmark
Before Project Fluid Tweak: 7334
After Project Fluid Tweak: [size="+1"]9264!!![/size]I only selected some of the tweaks (i.e. I didn't use "unlock with volume rocker and other stuff like that) Here's what I added to my build.prop. Feel free to do the same.View attachment 2785183
How to:
1. Open ES explorer (I'm using latest version)
2. Copy the tweaks that you want to add to build prop. Find the tweaks in spex's post or copy my selected tweaks. And thank spex in his thread.
3. Press the menu button on your phone. Click tools. Click on for root explorer and grant root permissions.
4. Click root explorer. Click Mount R/W. Choose R/W for /system and click ok.
5. Navigate to /system and open build.prop with ES note editor. Press the menu button on your phone and click edit.
6. Now paste the tweaks into the build.prop file. Or type them manually
7. Reboot and enjoy!
2. Tweak of Dash-M Script and tweak by myaservip
Please press thanks in his thread! This is not my work.
Dash-M has a tweak part and a script part too. If you want to try Dash-M Tweak, go to his myaservip's thread and download the zip, transfer to the root of your sdcard, go to recovery mode, and flash from there.But personally, Project Fluid's tweaks are more complete. I haven't tried Dash-M script since we haven't added init.d so stay tuned.3. Script and Tweak of ★ [MOD] ◢ PurePerformances™X ◣ | Golden Edition | Scary performances on Android by Jeeko
Please press thanks in his thread! This is not my work.
This is a single inseparable script and tweak in one so we cannot use it yet. Stay tuned.[size="+1"]General reminder: Tweaks and scripts are usually not mix-able. So remove one before trying another.[/size]
Chapter 6.0.0: Cool/Useful Stuff
1. Xposed Framework and Modules.
Our device can definitely benefit from Xposed modules! 4.2 is capable of running these.
2. TouchPal Keyboard
A good replacement to stock keyboard. Contains different keyboard layouts and support for tons of languages! And if you have experienced the keyboard not pressing the right button, this might be a better replacement.
3. Moreto come.
Hi there fellow Filipino! Please continue what you're doing. I can help you in some way in installing CWM-esque recovery tool for our phone. As it is a UBIFS-type system, many have said that it's a tricky job. A lot have failed but some did it successfully like me. I followed this tutorial from here
chinaphonearena.com/forum/Thread-CWM-For-All-MTK-Easy-Magic-CWM-MT6575-MT6515-MT6577-MT6517-MT6589-MT6582-MT6592
Sorry I can't post links yet because this is a new account.
So I was able to boot into recovery, but I stopped there until someone successfully restore our phone from a backup (even if it's just stock ROM)
Cheers! You should try it!
PS. I tried your build.prop and benchmarked afterwards, only to get about 7100+. HOW DID YOU GET TO 9K?! Please indicate if you have a lot of apps and is greenify and that cpu tool the only apps you're using for speed?
After sometime though, my phone got slow, so I deleted the added lines in build.prop and speed went back on. What's happening?
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
zildjosh97 said:
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
Click to expand...
Click to collapse
Hi! I've been a little busy lately haha. I'll get back to updating this thread in a week or so
Are you new to this stuff? Or have you had previous experience before? Seems like you're going pretty well! I don't know much about this phone of ours yet, maybe you know more than I do
Update: So my O+ phone wasn't sold, and now I plan to use it. Just tested Carliv 2.4 using Yuweng's Auto Magic Installer, and it installed! Restore doesn't work though. And don't advance restore > restore system. You'll get a bootloop haha.
HELP
What is the best CWM or TWRP on my o+8.31z, newbie here. and How? any Help. Thank you for rooting process. as well.
Sory
Sorry if I'm wrong forum, I just want to ask, is there any one can help me to do the rooting of the device Himax H TWO with the following specifications
CPU: MT6735 OCTACORE @ 1.3GHz
GPU: Mali-T720 MP3
Screen : 5.0 inc 720 x 1280 pixels (~294 ppi pixel density)
Android : Marshmellow with lewa os
Karne : 3.18.19
Ram : 2GB
Internal memory : 16GB
I HOPE there that will help me to do the roots and modify twrp for this device
Thankyou fery much
nothing working for MT6572 device (not that O+) for root.. tried all one click or simple root methods nothing working
MTK Droid root and tools waiting for hours and hours and nothing happens it just wont root my mobile idk what to do
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samitan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
I am looking for the same!
T5 Rom Needed
Hi, i'm looking for the same rom, i miss my phone's imei,
I was able to install the t5 lite Rom, but the NVRAM partition seems to be incompatible.
Thanks
Doogee t5s Stock rom
Please doogee t5s Stock rom link
Not a new ROM, but a step forward. (TWRP & SuperSU)
ethan_hines said:
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samaritan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
Click to expand...
Click to collapse
(Edited: Removed all external links due to my newcomer status)
To be brief:
I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.
I have managed to install a TWRP with SuperSU powers.
These instructions might help you clean up your current system.
Bonus: the recovery menu (TWRP) is multilingual.
Caveat emptor:
My stock ROM came with a nasty couple of Trojans(a) and other potential malware(b) embedded. The Trojans subscribed me to "premium" phone services, costing me some money. I went through the whole hassle in order to get rid of them.
If you have a DOOGEE T5S, your phone is probably infected too. Owners of other DOOGEE phones should beware. (c,d,e)
DISCLAIMER: The following instructions could seriously harm or brick your phone. I make no guarantees of any type, shape or form as to the end results. These operations WILL VOID YOUR WARRANTY.
What I did:
Last warning: during these operations I had to do a factory reset of my phone. I strongly recommend you BACKUP ALL YOUR DATA before you continue.
1] Install TWRP & root the phone (f)
* Download the required files:
- The TWRP image file here:
[Search the NEEROM dot COM website]
- The SuperSU patch file here:
[Search the NEEROM dot COM website]
* Unrar the TWRP image. Leave the SuperSU patch zipped.
* Enter fastboot mode.
Using ADB in terminal:
Code:
adb reboot bootloader
* Flash the TWRP image in the recovery partition.
Code:
fastboot flash recovery /path/to/twrp/image/recovery.img
(in my case fastboot requires root privileges, so sudo it.
* Reboot and enter in recovery mode.
In fasboot send the reboot system, but press Volume UP during reboot.
* Enter into TWRP and Install the patch "SuperSU 2.78-SR1"
Once in TWRP, ADB is again functional.
Load SuperSU patch to your sdcard:
Code:
adb push /path/to/your/patch/SuperSU_Pro_v2.78-SR1.zip /sdcard/
In the TWRP menu, go to "Install". Browse to the "sdcard" directory. Select the SuperSU patch and Install.
* Reboot to the system.
Beware: system will not start if you haven't installed the SuperSU patch. It will loop at startup, and won't progress beyond the startup logo.
2] Initial setup.
From factory reset, the phone will go through the first installation procedures. Follow the setup until your system logs on, and you can connect again to your phone via ADB.
3] Get rid of the malware.
* Disable the apps:
Without need of supercow powers:
- Enter an adb shell:
Code:
adb start-server
Code:
adb shell
Disable the apps:
In a normal ADB shell:
Code:
pm disable your.package.name.here
If you don't know the name of the packages, you can always get the full list with:
In your normal terminal (not adb):
Code:
adb shell 'pm list packages -f'
In an ADB shell:
Code:
pm list packages -f
* Remove the apps:
First try a normal removal. If they are system apps this will fail, but try anyways.
Code:
pm uninstall your.package.name.here
* Escalation to remove apps:
Now that the first try has failed, get supercow powers:
In the ADB shell:
Code:
su
(You should get a message on your phone telling you that ADB is requiring root privileges. Say OK)
Now your ADB console should read something like "[email protected]"
And we try again:
Code:
pm uninstall your.package.name.here
But we have a super hardcore app that fails to be removed with the normal supercow powers. So we step it up. (g)
Code:
pm uninstall -k --user 0 your.package.name.here
... SUCCESS!
But wait, the app is still there. Yes, you only removed it for root. So... lets do some overkilling:
Meanwhile:
Let's check the ID of the system user:
Code:
id system
In my phone "system" is 1000
So, here we go:
Code:
pm uninstall -k --user 1000 your.package.name.here
Your mileage may vary. Sometimes the first command does the trick, sometimes the app is still there.
Is it gone? Not always.
Can it creep out from the netherworld? Maybe. So, let's beat the dead horse.
* Silence the dead (h)
Just in case the app is still lurking, let's make it harder for it to creep up on us.
Code:
pm hide your.package.name.here
Great. Silent in its coffin.
But is the app still there? Sadly, yes. I looked around and the apps were still there, in a privilege data folder.
* Root it out (i)
This is an extreme measure. You can really harm yourself doing this, so... you have been warned.
At this stage, you should be using supercow powers. If you are not, brief recap:
Code:
adb shell
su
Now, the systems partition is read only, so you cannot remove the content there. So, to remove the files there, you have to remount it in read-write mode. Here we go:
Code:
mount -o rw,remount /system
Now, find the app directories you want to remove. In my case, the apps were in "/system/priv-app". So:
Code:
rm -rf /system/priv-app/YourAppFolder/
And, eventually, erase the associated data:
Code:
rm -rf /data/data/your.package.name.here
A read-write /system/ partition is not a good idea, so we reset as read-only:
Code:
mount -o ro,remount /system
[You might need this]
I don't remember if this is required. Maybe to be able to write to the recovery partition via fastboot...
Code:
adb shell setprop ro.secure 0
This voids the GUARANTEE. You have been warned (AGAIN).
----
(a) Found Trojan.Hiddad & Adware.Retsanvie. Probable carrier app: com.gangyun.beautysnap (aka com.android.snap).
(b) Antivirus programs tag the OTA program as potentially dangerous: com.fota.wirelessupdate
(c) [Some articles on DOOGEE and LEAGOO shipped with Trojans]
(d) [Some articles on DOOGEE and LEAGOO shipped with Trojans]
(e) [Some articles on DOOGEE and LEAGOO shipped with Trojans]
(f) [NEEDROM dot COM website]
(g) [ROMPROVIDER dot COM website]
(h) [Reddit Post]
(i) [ANDROID dot STACKEXCHANGE dot COM Post]
rrm. said:
(Edited: Removed all external links due to my newcomer status)
To be brief:
I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.
I have managed to install a TWRP with SuperSU powers.
These instructions might help you clean up your current system.
Bonus: the recovery menu (TWRP) is multilingual.
I am amazed you were able to do as much as you did with just ADB! Usually this type of phone (ChinaPhone) requires flashing the bootrom with a utility called SP Flash Tool and , VCOM Drivers as well as the aforementioned Scatter file! BTW There is a rom for the T5S LITE but not T5S (Despite many many requests, falling on deaf ears)
Click to expand...
Click to collapse
ethan_hines said:
rrm. said:
(Edited: Removed all external links due to my newcomer status)
To be brief:
I have not found the stock ROM for the DOOGEE T5S, nor tried any new custom ROM to replace it.
I have managed to install a TWRP with SuperSU powers.
These instructions might help you clean up your current system.
Bonus: the recovery menu (TWRP) is multilingual.
I am amazed you were able to do as much as you did with just ADB! Usually this type of phone (ChinaPhone) requires flashing the bootrom with a utility called SP Flash Tool and , VCOM Drivers as well as the aforementioned Scatter file! BTW There is a rom for the T5S LITE but not T5S (Despite many many requests, falling on deaf ears)
Click to expand...
Click to collapse
Yes, I did notice the lack of help regarding the release of the stock ROM. Given that (in my case) it was a compromised ROM (Trojans & Co.), I would imagine why they would not release the original one. It surprises me they are not releasing a cleaned up version, though.
The TWRP for the T6 works fine on the T5S. I was tempted to try one of the custom roms for T6 pro available at needrom DOT com. The thing is I need a working phone, so I cannot hard or soft brick my T5S. Not having a fallback ROM, that kind of nails it down for now.
I'm deploying LineageOS on a series of other devices. If all goes well, I might give LineageOS for T6 pro a try on my T5S. My concern is not the chipset of the SOB, it's the periphericals. Chiefly the capacity to recognize the SIM cards. It would defeat the purpose to have a running Android Nougat on my phone and not be able to make calls.
Click to expand...
Click to collapse
Replacement stock ROM: use the T5 lite stock ROM
ethan_hines said:
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samitan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
Click to expand...
Click to collapse
UPDATE:
Previously described to have successfully flashed TWRP 3.0.3 from needrom, with root powers, allowing for housekeeping of the original ROM.
I now inform you to have successfully flashed the T5 Lite stock rom (the UPDATE) into the T5S.
The ROM is apparently fully functional: RadioFM, front camera, back camera, WiFi, SIMs. I have not found any non-functioning feature.
I have tried to flash in a custom ROM, but until now I have been unsuccessful. While flashing the ROM with TWRP I get a 255 error. I'm thinking I need TWRP 3.1 or 3.2 to flash the custom ROMs I have. Sadly, there doesn't seem to be a TWRP 3.2 for the DOOGEE T5 lite/T5S.
I'll keep you all posted.
Need SuperSU
Is anyone here who can send me the "SuperSU_Pro_v2.78-SR1.zip"
PLEASEEEE don't send me the needrom link. Thanks!
ethan_hines said:
Surely someone has or can get the Official ROM for The Doogee T5s Note it's T5s not T5 nor T5 Lite.
It's Processor is MTK6735 not MTK6753. I need the ROM with the Scatter file. If you have a Custom Recovery TWRP/CWP that would be helpful too.
If need be I'll put a bounty on it but I am hoping some samitan will be so kind as to post it.
Thanks in Advance.
Included is a screen cap of the Diagnostic Software:
Click to expand...
Click to collapse
Finally the T5S firm is available at doogee.cc comunity!
I had to use it to revive my T5S after trying to flash TWRP recovery: I tried TWRP from T5, T6 and T6 Pro but in all cases phone got stuck in a boot loop. :crying:
I don't know if the official firmware contains bloatware... I'll keep any eye on it...
Doogee T5S rooten
After some time consuming experiments, I finally got my T5S rooted.
The main point after installing TWRP, througth fastboot or SP-Flash tool is:
1st: Booting immediatly into the recovery mode (prevents the operating system to switch to the original recovery app)
2nd: installing Super-SU before booting in the system (I my case it prevents the boot-loop. I think a must!)
When you finally restarted successfully the operating system, deactivate the APP "Aktualisierung mit Funknetz" (in englisch I think something like "OTA WiFi upgrade") , which seems to be reason for the malware. I my case, since I did it, no pop ad's appeared! (since 3weeks)
Remark:
As the T5S has the some CPU as T5light you can flash this firmware as well. I did it with the SP-tool but with same problem of poping up of unwished AD's, i.e. you have to root to put the above mention APP in deactivat mode (I did it with the app: 3C System Tuner Pro).