[Question] Leagoo Lead 1 impossible to root (solved)

[algert]

Hi All,

I've gone through quite some rooting tools and non of them are working.
NExt thing up I tried to do was use the magic CWM maker.

This came up with the following messages

You have a secure boot.img
You have a MTK 6582_SOC
You have kitkat

Termination of program and goodbye.

When hold vol up and power I get into 3 boot modes.
Recovery
Fastboot
normal

the fastboot command reckognizes my phone but when I enter Fastboot oem unlock nothing happens. So my trail runs dead when unlocking the boot.img.

this makes me kinda stuck in the process.
Also MTKDroid tools does not see the phone.

Usb Debug on/off doesn't make a difference.

Does anyone has good ideas that won't brick my phone but do Root it? I'm on a dead trail.

Thanks in advance

[Sniper47]

Did you install the ADB drivers?

[algert]

yup I did. But after some further research I figured that the phone is loaded with Yun Os AKA Aliyun...

How to get this rooted then? hmm..

[algert]

Looks like I (accidentaly) managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingo soft one click root, Mobile uncle tools
I Downloaded from kingosoft the sony bootloader unlocker.
It puts the phone in fastboot mode and then it hangs. I unplugged my phone, switch it off (keep the unlocker running) and manually booted into fastboot (vol up+power) the bootloader unlocker then proceeded untill finished.

Next I installed Kingoroot and started it while the phone was still in the fastboot mode. after a couple of restarts it says checking for Root, then I decided to start MTK uncle tools and scroll to "log and debugging" and select User2Root. then clicked Root and all of a sudden the phone was sucessfully rooted.. I don't know what exactly sparked the root access but It's rooted and works!

If anyone can reproduce this in a correct order. please feel free to share.

[aus9]

You have a secure boot.img

Can you install a terminal from playstore then do a full reboot
Now follow the true test down to and including Android section 1 & 2
and report your results
[Only registered and activated users can see links Click here to register]

If your id is good just say so no need for screenshot

if your /system is showing up as ro then you confirmed secure mode is still functioning (well) on your phone. Secure mode is safer. Less likely for you to delete things you shouldn't etc.

Leaping ahead ....now see if you can make it rw with terminal commands

Code:

su
mount -o remount,rw /system
mount | busybox grep /system

If you can't, please consider buying the playstore app called abdb insecure.
Assuming you want rw on full reboot or shutdown and normal startup.

If that app fails for you.....uninstall it and get a refund.

YMMV and good luck

[algert]

OK. You are the specialist this goes way above my head.

This is the screenshot from terminal w/o adbd insecure
       

Next post is with adbd insecure

[aus9]

great first image is proof you have secure mode and ro
second image you got read write.

I forgot to ask you to redo the id command
If it is the same as my image you have 2 choices

1) Each time you boot up....do what you just did to get rw status and test id
2) install the app and set it to insecure mode
---tick the box to keep it insecure mode over reboot

but you need to test it.....as each phone differs

[algert]

and this is with ADBD insecure.    

Looks like nothing changes and that IF I want to make my system rw. I have to execute it manually.

       


And here with the ID command added
   

Looks like the phone is rooted with RO permissions then I guess?

---

Here the ADB terminal commands with Adbd insecure
   

And here without ADBD insecure
   

[aus9]

Hi

please don't use Windows adb commands as I use Linux only. Everyone though can understand Android terminal commands.

When you enabled abdb insecure....it is supposed to give you rw without doing anything manual
Secondly you need to test it by doing a full reboot.

Can you do so before asking for a refund.

2)

And here with the ID command added

I am assuming you got rw then issued the id command ....good
which is bad .....as you do not have true root.

3) LETS TRY THAT AGAIN
If you have the patience, reboot phone initially with adbd insecure unticked for both boxes
do not do anything in the terminal
Now open insecure and tick both boxes
do nothing in the terminal and immediately do a full reboot

Now open ANDROID terminal and just test for rw status with id
----sorry for shout

Code:

su
id
mount | busybox grep /system

If you still have bad id results.....then you should consider un-install of that app and getting refund.

I am still assuming you want permanent rw status?

[algert]

I am still assuming you want permanent rw status?

system returns Read only. So the insecure is not helping me out on it.
Have to manually set the permissions to RW manually every reboot.

So will do ask a refund

Do you know also how to get the GPS going? it sees between 11-13 sattelites but it fails to get a fix. Epo mode is not available in kitkat. and from engineermode I can only get A-GPS . but no fix whatever I do. I injected GPS.conf with fasterfix to have the right NTP pool. but no success.. :/