Database Users

(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

Plz help me!!!!

Can u tell me how can i root my galaxy grand prime g-530h?

Devansh11 said:
Can u tell me how can i root my galaxy grand prime g-530h?
Click to expand...
Click to collapse
You can download supersu's latest version flashable zip and flash it via twrp, you'll automatically get your root

ok but
D.R-Ult.Googler said:
You can download supersu's latest version flashable zip and flash it via twrp, you'll automatically get your root
Click to expand...
Click to collapse
Can u tell me how to do via odin

Devansh11 said:
Can u tell me how to do via odin
Click to expand...
Click to collapse
You can use cf root if you want, but you must at latest lollipop stock and you'll get a guaranteed auto reboot to recovery every time you reboot your phone, but i can suggest you how to do it via twrp
1.download latest supersu flashable zip and put in your phone
2.flash twrp via odin
3.reboot to twrp recovery, find your location of your supersu zip, and flash it
3.once it's done, reboot.

Devansh11 said:
Can u tell me how to do via odin
Click to expand...
Click to collapse
Or just flash TWRP 2.8.7.0 via Odin then reboot ur phone to recovery mode. And reboot system from recovery it'll say Install supersu for confirming swipe right. Ur phone will automatucally reboot and in Menu u will see SuperSU installer just download and install SuperSu from Play Store or if u got SuperSU.apk install it and after installing it'll ask Update binary, update it via TWRP/CWM recovery not via Stock.
There u go =)

OTA full 1.4gb 4.0 update.

I realize there are other threads but they are full of questions. Chugging this back. And they aren't for the full OTA. Only the partial 919 MB update patch.
First I was on stock os with root and TWRP.
I download the full on through the OTA because my patched version failed. Anyhow it won't be any different.
If you can't flash. Download this 1.4gb full version.
http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
(md5 sum: 5D8CB6BA9E6C4281E208CB952E0B43A6)
Then flash it via TWRP. It will wipe root and return TWRP to stock recovery. Does not wipe apps or data.
It will flash fine. Then flash SuperSU 2.79. It will flash fine.
Clear cache.
Then you will have to flash TWRP. You can do this via the toolkit later. Unless you have a zip download somewhere.
Anyhow no DMverity issues. No update issues. Full OTA problems solved.
I'd imagine it will change beta into OTA as well.
Doo all this at your own risk.
To recap. Download and then flash in TWRP and flash 2.79 SuperSU after. Then flash TWRP however you did it the first time.
All problems solved.
Be aware I use encryption so this seems to encrypt your phone if decrypted. Apparently a backup is needed to make sure Incase it encrypts and messes up files. As stated above I take no responsibility. But will help anyway I can.

thank you!

Skwerl23 said:
I realize there are other threads but they are full of questions. Chugging this back. And they aren't for the full OTA. Only the partial 919 MB update patch.
First I was on stock os with root and TWRP.
I download the full on through the OTA because my patched version failed. Anyhow it won't be any different.
If you can't flash. Download this 1.4gb full version.
http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
Then flash it via TWRP. It will wipe root and return TWRP to stock recovery. Does not wipe apps or data.
It will flash fine. Then flash SuperSU 2.79. It will flash fine.
Clear cache.
Then you will have to flash TWRP. You can do this via the toolkit later. Unless you have a zip download somewhere.
Anyhow no DMverity issues. No update issues. Full OTA problems solved.
I'd imagine it will change beta into OTA as well.
Doo all this at your own risk.
To recap. Download and then flash in TWRP and flash 2.79 SuperSU after. Then flash TWRP however you did it the first time.
All problems solved.
Click to expand...
Click to collapse
I see you stated that you get no dm-verity issues. I've installed through twrp and before bootup I get the Dm-verity has not started with some red words. Do you get this?

As stated above I got no dm-verity issue. To fix use recovery and usb to push SuperSU. Then flash via recovery.
You can try using the toolkit to push it. Go into fastboot and push that way.
SuperSU fixes the issue when flashed. 2.79 specifically. I'll try to find you a guide and post it above.

delete

Seems that this upgrade encrypt data, so make an backup

Skwerl23 said:
As stated above I got no dm-verity issue. To fix use recovery and usb to push SuperSU. Then flash via recovery.
You can try using the toolkit to push it. Go into fastboot and push that way.
SuperSU fixes the issue when flashed. 2.79 specifically. I'll try to find you a guide and post it above.
Click to expand...
Click to collapse
I flashed supersu 2.79 in twrp and still have that on bootup.It boots with root access. Any ideas?

tdamocles said:
I flashed supersu 2.79 in twrp and still have that on bootup. Any ideas?
Click to expand...
Click to collapse
Internet said to flash stock recovery and it fixed it. Not sure I'd do that. You can try the no dm-verity patch included with the toolkit.

tdamocles said:
I flashed supersu 2.79 in twrp and still have that on bootup.It boots with root access. Any ideas?
Click to expand...
Click to collapse
I want to work this with you so anyone who needs help I can post the fix above.

Skwerl23 said:
I want to work this with you so anyone who needs help I can post the fix above.
Click to expand...
Click to collapse
Toolkit pushed dm verity disabler to device and I flashed through twrp but it still shows on bootup.

I can just clean flash using twrp right?

tdamocles said:
Toolkit pushed dm verity disabler to device and I flashed through twrp but it still shows on bootup.
Click to expand...
Click to collapse
Try flashing stock recovery.
Or
Flash the entire ROM again. Then SuperSU again.
Don't swipe right to modify data unless you install SuperSU before rebooting. Swiping to allow system mods with out flashing SuperSU or dm-verity disabler will give the dm-verity error.

youngstar07 said:
I can just clean flash using twrp right?
Click to expand...
Click to collapse
Dirty flash will upgrade. Clean flash will wipe all user data. As you should know.
Both will bring your phone online.
They flash stock recovery and not rooted.

Skwerl23 said:
Try flashing stock recovery.
Or
Flash the entire ROM again. Then SuperSU again.
Click to expand...
Click to collapse
I tried flashing the entire rom and it does not flash over twrp. I'll flash rom with twrp then flash stock recovery in fastboot and let it boot into OS and then go back and flash twrp in fastboot and then flash supersu in twrp, in a few minutes.

Skwerl23 said:
Dirty flash will upgrade. Clean flash will wipe all user data. As you should know.
Both will bring your phone online.
They flash stock recovery and not rooted.
Click to expand...
Click to collapse
Thanks for the reply.
I was wondering how does flashing this will revert recovery to stock.
And the other thread in xda has kinda different method. So I thought maybe its better to just clean flash. Also since this is an incremental upgrade I thoughy maybe clean flash will be better.

It's up to you. But it is the 100% ROM. Not a patch so a clean flash will work.

tdamocles said:
I tried flashing the entire rom and it does not flash over twrp. I'll flash rom with twrp then flash stock recovery in fastboot and let it boot into OS and then go back and flash twrp in fastboot and then flash supersu in twrp, in a few minutes.
Click to expand...
Click to collapse
What do you mean it doesn't flash? Didn't it flash before? Or does it require system modification to work.
Did you have encryption enabled before the patch?

Skwerl23 said:
What do you mean it doesn't flash? Didn't it flash before? Or does it require system modification to work.
Did you have encryption enabled before the patch?
Click to expand...
Click to collapse
Stock recovery is not flashed when flashing the rom for me. TWRP has remained on flashes. I'm always encrypted.
---------- Post added at 02:06 PM ---------- Previous post was at 01:53 PM ----------
Skwerl23 said:
Try flashing stock recovery.
Or
Flash the entire ROM again. Then SuperSU again.
Don't swipe right to modify data unless you install SuperSU before rebooting. Swiping to allow system mods with out flashing SuperSU or dm-verity disabler will give the dm-verity error.
Click to expand...
Click to collapse
It doesn't ask me again about modifying system....Since TWRP is on it already it doesn't ask about modifying system. It goes directly into TWRP main menu.

tdamocles said:
Stock recovery is not flashed when flashing the rom for me. TWRP has remained on flashes. I'm always encrypted.
---------- Post added at 02:06 PM ---------- Previous post was at 01:53 PM ----------
It doesn't ask me again about modifying system....Since TWRP is on it already it doesn't ask about modifying system. It goes directly into TWRP main menu.
Click to expand...
Click to collapse
You flashed the all zip? Not the patch zip?
In other words the 1.4gb one above? Maybe your download is corrupted. Download via PC and push over OTG or whatever from pc

One other thing to me is since it's not installing right, can you go in TWRP to mount. And then check what it says about system "read only" or what?
Is that checked or not? What error does it say when you full flash?

Root after Oreo update...

Can someone do the tutorial for rooting ze553kl after the Oreo update? Can I use the same recovery?
Thank you..

Root with magisk on Android O
You can root Zenfone 3 zoom with magisk on Android O
I tried rooting it by flashing latest super su but it stuck while booting
1. Unlock the bootloader with the asus's official unlock tool(you can get if on there website)
2. Download magisk app from their website
3. Open the app and download the latest magisk zip file
4. Download TWRP recovery for Asus Zenfone 3
Zoom(search on xda for recovery)
5. Flash TWRP recovery via fastboot method .Then
directly reboot to recovery
6. Now install magisk zip file via TWRP
7. Reboot and enjoy root and magisk modules

Thanks man, but my recovery keeps turning to stock.

TaeBR said:
Thanks man, but my recovery keeps turning to stock.
Click to expand...
Click to collapse
Once you have flashed TWRP, reboot straight into recovery rather than back into the system, otherwise the system overwrites with stock recovery. Once you've done it once it should stick. Hope that works for you.

pjcarrmole said:
Once you have flashed TWRP, reboot straight into recovery rather than back into the system, otherwise the system overwrites with stock recovery. Once you've done it once it should stick. Hope that works for you.
Click to expand...
Click to collapse
Thanks man, but now when i flash the supersu i got the error:
-Patching sepolicy
---Failure, aborting
its getting worst

How can i fix the fingerprint with magisk on Oreo?

I keep losing my root after reboot

Hi, just as the title says everytime i reboot my devices after successfully installing magisk through a patched boot image file i lose root. Root works i also checked with the root checker when i don't reboot my device. What is causing this ?

Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.

tanapak1 said:
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
Click to expand...
Click to collapse
thanks i'll give it a try

emiljano539 said:
thanks i'll give it a try
Click to expand...
Click to collapse
Flash magisk 16.7

tanapak1 said:
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
Click to expand...
Click to collapse
now its working after i flashed the magisk by twrp thanks

ProchyGaming said:
Flash magisk 16.7
Click to expand...
Click to collapse
i just flashed by twrp and its working now

Doesn't twrp unable ota updates?