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

super su

Anyone know why it wont stay

Ssys no batty

Says no binary installed

pbedard said:
Says no binary installed
Click to expand...
Click to collapse
1st, did you flash the SU file? 2nd, what rom are you on?

Yes 5 times 2 im using dev digitals rom im on sprint

pbedard said:
Yes 5 times 2 im using dev digitals rom im on sprint
Click to expand...
Click to collapse
The latest SU File? which is SR3 2.79? if it didnt work try the Unsu.zip file to remove SU and then flash the SU file again. see if that works.

Devdigital help me thanks

pbedard said:
Devdigital help me thanks
Click to expand...
Click to collapse
did you flashed the unsu file then flashed the Su file?

Devdigital tols me replash the rom cause ite not using super su its using majiskSU

pbedard said:
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
Click to expand...
Click to collapse
AAhh i see. Now i know where you are standing at. you are using magisk. But do you have magisksu ? or keep having supersu as main root but magisk installed? . What i mean to say is, when you go into the magisk app, in the 2nd box of the main screen, does it shows supersu as root method? or magisksu? if it is magisksu then you dont need supersu, now, if it does says supersu, then you do have to fix the issue of supersu to unroot by using supersu function and then go directly into recovery mode and flash magisksu once again.

It says majisksu

pbedard said:
It says majisksu
Click to expand...
Click to collapse
then you dont need su (unless you want it). It is because you already have magisksu (which is pretty much doing the same as su). one overrides the other and then one gets thrown out. Usually to install magisk manually, one does as follows:
1) install magisk app from playstore
2) give supersu access (granted to magisk su)
3) use unroot function in supersu
4) flash magisk zip in recovery mode.
Now, there are other methods to achieve magisksu but the point is that maisksu has changed the binary (which is what SuperSU is telling you that you dont have).But that doesnt mean you are not rooted. you are already rooted with magisk and can achieve pretty much anything that you could achieve with supersu. (it will ask you for prompts asking you whether you want to give su access to "x" or "y" app. etc... Now, if you want SuperSU, you could try to flash the magisk uninstaller. Then do the process of rooting that has been specified for your phone. That should return the SU binary to normality . (this assuming you try to unroot and then flash SU back but didnt work)

hey guys bought my ls997 used. has root because i get the flash screen (untrusted)and twrp is installed and working. how do i find out which to flash ? any advantages to use supersu over magisk ?
i installed magisk manager and it states no root found.

Majisk u have to turn root access on majisk works alot better

@pbedard
Did the help @jinkerz9430 gave work for you?

Yws

Lost root after upgrading

Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.

RautMike said:
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
Click to expand...
Click to collapse
Flash magisk 13

​
RautMike said:
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
Click to expand...
Click to collapse
Of course you lost root and TWRP because a update.zip contains also recovery and other things(vendor, custom, etc.) and by flashing it the stock recovery will overwrite your TWRP and the new system will delete your root access.
And NEVER install KingRoot on this device! It will mess a lot of things(SuperSU and Magisk work)
You will need to flash TWRP again in order to have root because both supersu and magisk need to be flashed through TWRP(because they are .zip files, at least a part of the root, you will need to install the magisk app to have full root)
SuperSU root just needs to be flashed, just magisk needs an app to be installed after .zip flash.

XTutorials said:
​Of course you lost root and TWRP because a update.zip contains also recovery and other things(vendor, custom, etc.) and by flashing it the stock recovery will overwrite your TWRP and the new system will delete your root access.
And NEVER install KingRoot on this device! It will mess a lot of things(SuperSU and Magisk work)
You will need to flash TWRP again in order to have root because both supersu and magisk need to be flashed through TWRP(because they are .zip files, at least a part of the root, you will need to install the magisk app to have full root)
SuperSU root just needs to be flashed, just magisk needs an app to be installed after .zip flash.
Click to expand...
Click to collapse
Ok, thank you very much. Ill just wait to come back home from my Vacation and then flash twrp

[Question] Can i get twrp and root on official nougat

just got nougat in the UK, and i was wondering if i can get twrp and root on it. The answer is probably yes but i just want to make sure, thanks

yes, i did it today

fliperpl said:
yes, i did it today
Click to expand...
Click to collapse
Thanks, good to know. Might wait on it, as if i do this and theres a new update im screwed

What about Systemless Root?

CLETjB said:
What about Systemless Root?
Click to expand...
Click to collapse
magisk works without problems

Instead of flashing TWRP as the permanent recovery, just boot to it by putting your phone into Bootloader mode and use the command Fastboot boot twrp.img (replace twrp.img with the filename of your twrp). Then you can install either SuperSU or Magisk as you desire. If using SuperSU, I would recommend using the SuperSUConfig to ensure that it is installed in Systemless > SBIN so that you can then install SUHide in order that you can get the likes of Snapchat working. Magisk of course has this all ready built in so you don't have to mess about flashing extras.
All being well, your device *should* then be able to accept any further OTA's, although I wouldn't hold my breath for any further ones being released.
You might also want to look at Flashfire by the same chap who gave us SuperSU.

lmulli said:
Instead of flashing TWRP as the permanent recovery, just boot to it by putting your phone into Bootloader mode and use the command Fastboot boot twrp.img (replace twrp.img with the filename of your twrp). Then you can install either SuperSU or Magisk as you desire. If using SuperSU, I would recommend using the SuperSUConfig to ensure that it is installed in Systemless > SBIN so that you can then install SUHide in order that you can get the likes of Snapchat working. Magisk of course has this all ready built in so you don't have to mess about flashing extras.
All being well, your device *should* then be able to accept any further OTA's, although I wouldn't hold my breath for any further ones being released.
You might also want to look at Flashfire by the same chap who gave us SuperSU.
Click to expand...
Click to collapse
Thanks a lot! The only problem was that suhide doesn't seem to want to flash. However my root works and so does my snapchat
Edit: Logging out of snapchat wont let me log back in? So is there any way to hide the root?
Edit 2: Nvm. You have to flash SuperSu-SR4 instead of the normal 2.82 one. I was now able to flash suhide and get everything working

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?

jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.

cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.

please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager

@cssr any other input or suggestions?

jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.

cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(

@cssr should i try another version of magisk?

jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?

cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?

What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.

I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.