<SOLVED> How to Root Android MM 6.0.1 on YD201 ? - YotaPhone

How to Root Android MM 6.0.1 on YD201 ? i try kingroot, kingoroot and flash supersu flashable zip through TWRP failed me and already oem unlock. any idea? thanks
---solved---
Flash using SuperSU v.2.79 via TWRP... Done

uuuaaaqq said:
How to Root Android MM 6.0.1 on YD201 ? i try kingroot, kingoroot and flash supersu flashable zip through TWRP failed me and already oem unlock. any idea? thanks
Click to expand...
Click to collapse
Unlock bootloader.
Install/boot TWRP and flash SuperSu zip.
What error did you receive?
Sent from my YD201 using Tapatalk

rufy93 said:
Unlock bootloader.
Install/boot TWRP and flash SuperSu zip.
What error did you receive?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
During flashing didn't mention the error on TWRP, then bootloop happen.

A couple of questions.
Were you able to access TWRP?
If yes, Did you install TWRP or did you just boot?
Which version of SuperSu did you try flashing.
Are you sure it was a clean install?
I am just speculating now, but i suspect if you tried other root methods they may have change some items in system which messed upp SuperSu installation.

rufy93 said:
A couple of questions.
Were you able to access TWRP?
If yes, Did you install TWRP or did you just boot?
Which version of SuperSu did you try flashing.
Are you sure it was a clean install?
I am just speculating now, but i suspect if you tried other root methods they may have change some items in system which messed upp SuperSu installation.
Click to expand...
Click to collapse
Yes, my mistake flashing using old version SuperSU, flashing using newer stable version 2.79, success without problem. Thanks to you.

Related

[Q] SuperSU gives me an error - "There is no binary installed" (Android 5.0)

[Q] SuperSU gives me an error - "There is no binary installed" (Android 5.0)
I have just updated my nexus 4 to Andorid L 5.0 and I rooted the device using CF-Autoroot.
I have the SuperSu app but I dont have access to root and when I open it, it says :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device."
I am quite tired of unlocking my bootloader over and over again.
Is there a flashable zip that can fix this problem ?
Thank you!
LegitCarry said:
I have just updated my nexus 4 to Andorid L 5.0 and I rooted the device using CF-Autoroot.
I have the SuperSu app but I dont have access to root and when I open it, it says :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device."
I am quite tired of unlocking my bootloader over and over again.
Is there a flashable zip that can fix this problem ?
Thank you!
Click to expand...
Click to collapse
Download Supersu beta 2.27 zip from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
But you need to have a custom recovery like CWM or TWRP to flash it.
venu123 said:
Download Supersu beta 2.27 zip from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
But you need to have a custom recovery like CWM or TWRP to flash it.
Click to expand...
Click to collapse
Hey thanks for the comment. I flashed it and im stuck now on bootloop
Okay I gave up. I will just flash factory image again and ill leave the bootloader unlocked.
Waiting for the stable version.
LegitCarry said:
Okay I gave up. I will just flash factory image again and ill leave the bootloader unlocked.
Waiting for the stable version.
Click to expand...
Click to collapse
you need to flash .img file of modified kernel from chainfire. and yr .zip of supersu will work
SuperSU 2.2.7 will work but CF-Autoroot flashes a modified kernel so you need to flash a stock kernel first then install SuperSU from TWRP. You can leave you bootloader unlocked.

(REQ)Samsung A700YD android 5.0.2 root

Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Anyone can help?
Install twrp then use supersu v2.65
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I have tried some twrp recovery. It can enter the recovery successfully but it cannot boot normally. It stuck at samsung logo.
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I've tried to dig more in it, and what I get is
1. The only way I succeed is by using KingRoot, and the method it's using is by exploiting and keeping a daemon background and the su file for calling the daemon. So that means after reboot, root is lost.
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
4. In the bootloop, logcat shows that it is repeating a particular normal boot process
5. In the bootloop, using adb shell and typing "su" will not get into root, despite su is located in xbin.
6. Busybox functions normally.
Any ideas?
ProtoAES256 said:
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
Click to expand...
Click to collapse
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
ashyx said:
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
Click to expand...
Click to collapse
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
From my current experience, no. The sad thing is I'm not skilled enough to do it myself, and seemly there is no reason that skilled devs are willing to have a head in to this not-quite-popular device.
Btw, you need to format /system partition before you flash the kitkat(well, maybe it works maybe it don't, it's just my experience.)
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
If you have twrp installed I will upload a modified version of SuperSU which will allow systemless root on 5.0.2.
This will patch the boot image and should prevent a bootloop.
ashyx said:
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
Click to expand...
Click to collapse
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
ProtoAES256 said:
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
Click to expand...
Click to collapse
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
ashyx said:
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
Click to expand...
Click to collapse
here you go, extracted from A700YDZSU1BOL4_A700YDZZT1BOL4_A700YDZSU1BOL4_HOME.tar
https://mega.nz/#!14IE3YoA!mRAhQSJCgZ53r5teACeJGWMwrftIY0g0GvZM0LMX9Kg
Hi everyone!
I found this two files, they are recovery.img and supersu 2.46. I still haven't tested them, because recovery is in img format and it has only the Chinese language. If anyone can help me translate the recovery and convert it in tar.md5 format. I found this 2 files on a700yd chinese forum. Thanks!
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
ashyx said:
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
Click to expand...
Click to collapse
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
ProtoAES256 said:
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
Click to expand...
Click to collapse
Try the supersu version above.
ashyx said:
Try the supersu version above.
Click to expand...
Click to collapse
i just update myphone to new firmware. i see something new eg : About device > "android security patch level"
i have same prolem (myphone boot stuck after flash superuser.zip v2.62-2.72 via twrp). And i try reflash one old boot.img via odin then myphone boot up normally with superuser.
i think the new boot.img make myphone stuck.
Can you please help me patch the new boot.img !?
ps: i'm so sorry for my bad english
https://drive.google.com/folderview?id=0B7uFmNBw-G1QalBCZERkeUpjd0U&usp=sharing
Hi Guys!
I ask you if someone used cf-auto root on this device and it was able to root the phone? Thanks.
hkopenh17071 said:
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Click to expand...
Click to collapse
http://forum.xda-developers.com/samsung-a-series/development/galaxy-series-cf-auto-root-t3280406

After update to 6.01 rooted with CF. After few days root lost

Hi I updated my 910F to MM then rooted with CF, and all went fine.
Now after few days the phone lost root (no idea how) and now redoing with CF Chainfire will not root the phone ???
How to root now?
Maybe try reflash firmware, then fash TWRP via Odin and then flash latest supersu via TWRP. That's how I did it an have no problems
Sent from my SM-N910F using Tapatalk
claudioita said:
Hi I updated my 910F to MM then rooted with CF, and all went fine.
Now after few days the phone lost root (no idea how) and now redoing with CF Chainfire will not root the phone ???
How to root now?
Click to expand...
Click to collapse
CF AutoRoot is not up to date so it will disappear after some time.
Its better to you to root it on this way :
Download Latest SuperSU and TWRP Recovery ;
Copy the Latest SuperSu zip on your phone/sd card ;
Flash TWRP via Odin ;
Reboot on TWRP ;
Flash SuperSU and all should be good.
tried it, re doing CF chainfire, install latest stable superSU from TWRP, still cannot get the root access back.
horsyneeh said:
tried it, re doing CF chainfire, install latest stable superSU from TWRP, still cannot get the root access back.
Click to expand...
Click to collapse
Use File Manager in TWRP del folder "supersu" then flash supersu zip via TWRP again .
Note_4 said:
Use File Manager in TWRP del folder "supersu" then flash supersu zip via TWRP again .
Click to expand...
Click to collapse
still no luck mate, maybe i will try re flash using different firmware later and redo the step all over again, hoope it works.
thnx :good:
I had the same problem due to security policy update. I did hard reset and then CF auto root passed successfuly.
Sent from my SM-N910C using XDA-Developers mobile app
IronMaidenBG said:
I had the same problem due to security policy update. I did hard reset and then CF auto root passed successfuly.
Sent from my SM-N910C using XDA-Developers mobile app
Click to expand...
Click to collapse
i have the same problem, what are you doing to "hard reset" the phone please..?
edit: wipe data factory reset in recovery not working for me... impossible to root after
brunsman6229 said:
i have the same problem, what are you doing to "hard reset" the phone please..?
edit: wipe data factory reset in recovery not working for me... impossible to root after
Click to expand...
Click to collapse
Yes. In stock recovery factory reset and wipe cache.
Sent from my SM-N910C using XDA-Developers mobile app
Can someone post links to latest TWRP and superSu for N910F 6.0.1....thanks...
Sent from my SM-N910F using Tapatalk

Stuck at supersu binary

Hi everyone,
I tried to root my G2 on KK with IOroot. After flashing supersu didn't work. It asks to update supersu binary and when i try to udate binary, it fails. I have also tried updating binary after updating supersu app from playstore but same happened. Now i can't remove supersu from phone as it is a system app now. How can i root my phone properly at this stage?
Kindly help
ali.akbar01 said:
Hi everyone,
I tried to root my G2 on KK with IOroot. After flashing supersu didn't work. It asks to update supersu binary and when i try to udate binary, it fails. I have also tried updating binary after updating supersu app from playstore but same happened. Now i can't remove supersu from phone as it is a system app now. How can i root my phone properly at this stage?
Kindly help
Click to expand...
Click to collapse
Try flash newest beta from SuperSU zip or try new better Magisk and after flash not forget to bump with blastagators bumpscript
Zero_Rik said:
Try flash newest beta from SuperSU zip or try new better Magisk and after flash not forget to bump with blastagators bumpscript
Click to expand...
Click to collapse
I don't have any custom recovery installed on my phone, i can't flash what u mentioned. Kingroot also fails

[Q] Successful rooted, but /system is read only?

Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2

Categories

Resources