[Question] Rooting a Timmy E82 Android 4.3 MTK MT6582 device?

[Android-uk]

Hello,

Does anyone have any idea which method to root a Timmy E82 Android 4.3 MTK MT6582 device? Can't seem to find any information on the MT6582 on the forum?

So far I've tried:

Android JB, easy method A
All versions of Android, easy method G - TRY THIS FIRST

Help

[Android-uk]

vroot method worked, only issue I have now is I can't seem to figure out how to replace the default China super user application with SuperSU.

I install SuperSU and then attempt to have it uninstall the other application but at that point it fails to do and states Binary update failed.

Anyone have any ideas?

[GizBeat]

Good you tried the other methods until one worked.

What happens if you install SuperSU and leave kinguser on there?

[Android-uk]

Good you tried the other methods until one worked.

What happens if you install SuperSU and leave kinguser on there?

If I have both of them on there, Kinguser continues to act as the superuser app, given giving SuperSu root permission. SuperSu askes to download binary, then states it detected other superuser app and will attempt to remove, it then closes, kinguser disappears but SuperSU still asks for a new binary but now states installation failed.

I used vroot v1.7 to do the root. Can't recall which method it is on the sticky. I'm at work and my workplace blocks the download links.

[Android-uk]

A bit of an update with this. I believe my phone is not 100% rooted, at least not correctly. China superuser may be there and provided root, but when I attempted to run the command:

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

Via Terminal Emulator it gives the error:

mount: Operation not permitted

Researching tells me it means my phone lacks true root, which would also explain why when I try to replace vroot SU with SuperSU it states superuser.apk cannot be found.

Going to have to go back to the drawing board and attemping other rooting methods.

I'll report back once I figure out a method that works correctly.

[GizBeat]

You can try one of the other methods. See if they work for you.

Regarding if it's correctly mounted now, it could be an issue with the USB or driver connection between the PC and the phone.

Have you checked with a root checker from Play? They're quite accurate. They'll test if the SU Bin is in /system as well.

Another way to do it functionally - use ES Explorer. Make sure 'root explorer' in ES Explorer is 'on' (Menu > Tools). If it allow it, it means you're mounted. To take it one step further, then try to copy and paste a text file or image or any file into /system.

[Android-uk]

I'm just about ready to give up hope. Is it because my device is android 4.3? Nothing seems to work, so damn annoying. Really regretting getting this phone now.

Most tools claim my phone is rooted, and yet root checker states its not, no SU app functions as well. Just don't know what to do.

The only method that comes close is "All versions of Android, easy method B". I got the crap China SU, but can't replace it, busy box won't install and my /system remains ro

Regardless if I use root explorer or es file explorer /system refuses to mount as r/w - is there any other way I could do this?

the issue points to /system being locked for some reason

[GizBeat]

You've tried all seven methods there? This is actually the first time out of many hundreds we've had someone not succeed.

You can try to factory reset, then use a method other than vroot. I've had situations similar to yours where a root method would partially succeed, but it wouldn't be truly rooted. The only way to get it to work was to factory reset and use a different method.

Or, the next step is to build CWM. There are a couple tutorials in the sub-forums.

[Android-uk]

I guess my phones a stubborn one XD

I'll do a factory reset via the phone and test each method one by one, factory resetting it inbetween each.

I'll let you know how I get on

[Android-uk]

Hi,

Well I have tired all methods again, they all fail because they cannot remount /system as r/w! Even the latest version of MTK Droid tools fail, but it does manage to get shell root, make a backup of the ROM and then fails.

I have attempted the custom CWM root, and I've now hit a slight issue with this, which I could use help with.

I managed to complete the following steps using yulypis method:

1. Create a scatter file for your phone with MTKDroidTools and leave MTKDroidTools open
2. Open SP Flash Tools and load the scatter file you just created
3. Go to ReadBack Tab and Add a new entry - name it as you wish but leave the ROM_0 prefix - double tap the new entry and choose the length of ROM you want to read - to create the recovery it is enough to put the number of the partition right after the recovery (you can take that number from the scatter file you created) - Keep in mind the number must be in Hex - so when you copy it from the scatter file - make sure it's with the 0x prefix - something like 0x03d80000 for example.
4. Hit the Readback and disconnect your phone from the computer, shut it down, pull out the battery for a few seconds and then put the battery back - don't turn the phone on - just connect it to the usb - it should start the readback and eventually should finish with a green circle - if everything went good Smiling

B. Process the ROM and generate the recovery (should be automatic):
1. Go back to your MTKDroidTools - which should still be open from before - and hit "Process ROM" and choose the one you just read from the SP Flash Tools.
2. If the reading was successful - you should see the partitions you read being copied - and you would be asked if to create CWM recovery automatically - answer YES Smiling
3. After this process has ended successfully - go into the backups folder inside the mtkdroidtools folder - and you should see the ROM partitions you read - including the original boot.img and recovery.img as well as the newly created patched_recovery.img and patched_boot.img

C. Flash the generated recovery:
1. Create a new folder and copy your original scatter file you created in step A1 and your patched_recovery.img into this new folder.
2. In the new folder you created, rename the patched_recovery.img to just recovery.img
3. Open SP Flash Tools, choose the scatter file you copied in the new folder and you should see that it also adds automatically the recovery (make sure it's the correct folder) - Make sure that ONLY recovery section is selected !!!!!!

I'm using:

SP_Flash_Tool_v3.1332.0.187
MTK Droid tools v2.5.1

Where it fails is I get to the last step

- hit Download and disconnect your phone from the computer, shut it down, pull out the battery for a few seconds and then put the battery back - don't turn the phone on - just connect it to the usb - it should start the flashing of the recovery and upon successful flash - you will see the green circle ;)

This doesn't happen, instead SP Flash tools gives me the following error:

FLASH TOOL ERROR (8038)

I've read up and it appears to be a scatter file issue. I've attached my last log from SP Flash tools and my scatter file, is there something I'm missing? This is getting way over my head.

Please help