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
I'm on a B09, bootloader unlocked and rooted with SuperSU 2.65 A2017G.
Except from the 2.65 version, is there another one working for the A2017G?
I want to get Xposed and if I do understand I need SuperSU 2.75 or above to get Xposed to work in systemless.
If there isn't another version could you guys help to get Xposed working on my phone?
That would be much appreciated.
EDIT: Well I'm dumb, I assumed Oki's guide only worked on the A2017U variant. Sorry guys :/
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Yeah I figured it out with the help of Oki's guide.
Thanks for the answer!
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
nuserame said:
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
Click to expand...
Click to collapse
Did you make sure to disable system write protection? Boot into TWRP, open up the terminal emulator, and issue the command: reboot disemmcwp
I'm having a similar problem while flashing superuser. The error happens after the "patching sepolicy" line runs. The error prevents SuperSU from being installed at all. Any suggestions?
You need to flash twrp 3.0.3 or above and flash SuperSU 2.79
Latest SuperSU Causes Endless Loops on the Axon 7
Literally, every time I install the latest version of SuperSU on my axon I get an endless bootloop. These are SuperSU files I get directly from chainfire's website. There must be something im missing, or maybe im downloading the wrong version? Im not sure i was hoping to get some help. I just tried installing: SR3-SuperSU-v2.79-SR3-20170114223742.
>> Can anyone point me in the right direction of the latest SuperSU that works with the Axon 7 that doesnt bootloop it.
I remember that the Pixel phones had SuperSUs that were made for it. I am wondering does the same thing apply here?
I have installed everything right on my phone to the T. Everything was brand new stock.
Kinanizer said:
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Click to expand...
Click to collapse
Hello,
yesterday I tried to root my Huawei P8. I've unlocked the bootloader and installed TWRP and in TWRP I installed SuperSU v2.46 (I didnt't wipe dalvik cache after that). Then I rebooted my phone and it didn't boot up, it just stayed by the pulsating Huawei logo. I let it in this process over night but still no result. Today I tried to flash the B110 recovery stock, after that the TWRP was gone and I can only access Huawei eRecovery and Bootloader mode. With some research I found another version of SuperSU v2.67 and I flashed another TWRP but that won't work, I can only access eRecovery, even after several tries and in the console it said it was successful.
I hope I made my problem clear and anybody can help me
I do not know anything with such old firmwares but I experienced similar issues with with SuperSU above B393 firmwares. I gave up the old school way of rooting and SuperSU as it coused bootloops like you described above and switched to the magisk way with the B398 firmware. Everything works. Will upload all needed files in the B398 thread in an hour or so.
PlzFixMyPhone said:
Hello,
yesterday I tried to root my Huawei P8. I've unlocked the bootloader and installed TWRP and in TWRP I installed SuperSU v2.46 (I didnt't wipe dalvik cache after that). Then I rebooted my phone and it didn't boot up, it just stayed by the pulsating Huawei logo. I let it in this process over night but still no result. Today I tried to flash the B110 recovery stock, after that the TWRP was gone and I can only access Huawei eRecovery and Bootloader mode. With some research I found another version of SuperSU v2.67 and I flashed another TWRP but that won't work, I can only access eRecovery, even after several tries and in the console it said it was successful.
I hope I made my problem clear and anybody can help me
Click to expand...
Click to collapse
search on google huawei p8 custom kernel and download from where it says androidhost and flash using twrp and it will boot had same problem too but fixed it and now successfully rooted
Hello,
iam now very frutrated trying to unroot my Huawei P8.
Searched the net again and again ending on tons of crappy blogs with unusual information :-/
My Problem :
I have a Huawei P8 (Not that dumb "lite" )
The USB Port is faulty, so no ADB is aviable.
The Phone was on B370 and i used crappy Kingroot to install TWRP. This worked and i have a functional TWRP.
I tryed to unroot the phone for Safetyet by installing Magisk to get rid of Kingroot. This didnt worked (ERROR 1 insufficient partition sice at flashing boot.img)
I found a B370 Stock prerooted (FF) here and flashed it with TWRP. This worked and i got rid of Kingroot.
https://forum.xda-developers.com/huawei-p8/development/rom-huawei-p8-stock-b370-prerootet-t3421507
But i need a unrooted B370 Rom to pass Safety Net Check.
I tryed to unroot with the preinstelled SuperSu, but this didnt work.
The B370 non FF in the linked post is no longer aviable on MegaNZ
So i tryed to flash the system partition from a unrooted Rom. I extracted the system.img from the update.app and created a flashable zip.
But the phone hangs on the first bootscreen and doesnt pass to the boot animation.
Does anyone know, how to unroot the phone without USB by KEEPING TWRP ?
Greetings Chris