Related
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
This device seems to be a little trickier to root compared to my old Galaxy S3.
I just received a brand new Moto X Pure, XT1575 (North American variant I'm assuming since I bought it from the US).
It's currently running Marshmallow 6.0, and has been OTA updated to the Feburary 2016 security update.
I want to keep the stock ROM, but I want it to be rooted. XPosed would be nice as well, but not necessary. I do not want any custom ROMs, just the stock ROM rooted.
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Fantastic advice!
Sent from my XT1575 using XDA-Developers mobile app
You'll have to use a very specific - older systemless root though. I think supersu-2.64, but I'll let someone else confirm that. The other superusers will not work.
jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Sorry I been away from the rooting methods for too long (since my note 2) I already unlocked the bootloader on my phone but to install twrp can I still follow this tutorial? TIA
https://youtu.be/iPspDlbRf88
Sent from my XT1575 using XDA-Developers mobile app
jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Thanks!!! that little line of code for TWRPs built-in terminal did the work
rmaspons said:
Thanks!!! that little line of code for TWRPs built-in terminal did the work
Click to expand...
Click to collapse
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.
martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
It didn't work for me via adb command.... Had to use TWRPs built-in terminal. Just wrote wrote the line, as it is, go back to the main menu and flash Supersu (I used the latest one: 2.67) just as you normally do. Then reboot. No more stock in the M logo
jason2678 said:
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.
Click to expand...
Click to collapse
Thanks! This did work for me. I am now rooted.
I am using twrp 3.0.0.0 I used 2.62 however when I tried to click the option in the terminal keyboard for the = (equal sign) I keep getting a blue screen. 3.0 keyboard works ok. I entered the, echo "SYSTEMLESS=true" > /data/.supersu and pressed the go button. It showed up on the main terminal screen. Im a bit confused at this point....do I flash supersu from my pc using flashboot on the bootloader page? or download the supersu.zip to my phone and use twrp to flash it? When twrp asked to flash supersu I did that and wound up stuck on the big M again. I think I restored my phone about 6 times so far. lol
Flash in recovery. Use 2.62-3.
So using 2.62.3 will void having to type SYSTEMLESS=true" > /data/.supersu. or do u still have to type that in terminal? Plus using the twrp-3.0.2-0-clark. Should I use and older version?
No just flash.
Flashed Supersu 2.76 on top of xt-1575 18-4 image without any problems usung TWRP 3.0.2.
I did add .supersu text file to /data just as an insurance.
Nuts. Didn't see the part about doing a backup first (hitting head, as this isn't my first rodeo). Too anxious I guess. Now I'm stuck at the M android screen. (didn't do the "SYSTEMLESS=true" > /data/.supersu" command). Any way to fix or am I just screwed?
I can get to TWRP, so theoretically, I could flash a stock version of Android back onto it. Anyone know where I can pick one up?
Did the same ****. Was so excited getting the phone and didn't read the systemless =true crap for M. Didn't do a back up but got a system file from Motorola. You can pick one up here to start over. http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Anxiety might lead to unexpected results
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance
eat-man said:
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance
Click to expand...
Click to collapse
Not really sure what you need a video for, the process is simple and the same for all Gen3/4 Moto devices... the chanced of "breaking" something are near zero. You need fastboot working, that is on you.
1) Unlock the bootloader
2) Download the latest TWRP and SuperSU. Place TWRP img in your fastboot directory and SuperSU zip on your device so you know where it is, internal storage or SD card is not relevant.
3) Start the bootloader, either with `adb reboot bootloader` or power off and hold VOL DN and then press and hold POWER until the menu comes up
4) Start TWRP with `fastboot boot twrp-3.0.2-0-clark.img` and backup
5) Go to TWRP's Advanced menu and select Terminal
6) Enter `echo SYSTEMLESS=true>>/data/.supersu` press enter , exit, and Home button
7) Install (Flash) SuperSU ZIP file, clear caches if you wish but it isn't necessary.
8) Reboot
That is all there is too it
man u are awesome it took me a while and just stumbled on to this and u couldnt have made it less confusing
I have been using TWRP+SuperSU on my HTC 10 (sprint). However, I am not happy not being able to use Android Pay due to root. I searched and found a MAGISK root can do the trick.. I searched and was surprise to find not much of info on this variant.
I only found this: [ROOT] Magisk AutoRoot: Magisk + phh's SuperUser for Nougat (No TWRP required). But that's for the Unlocked version:
Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zip
I assume I cannot use above boot image for Sprint variant. My question is, where to get this prebuilt boot image for Sprint?
I am on Android 7.0 (2.42.651.6).
Thanks!!
ctzw said:
I have been using TWRP+SuperSU on my HTC 10 (sprint). However, I am not happy not being able to use Android Pay due to root. I searched and found a MAGISK root can do the trick.. I searched and was surprise to find not much of info on this variant.
I only found this: [ROOT] Magisk AutoRoot: Magisk + phh's SuperUser for Nougat (No TWRP required). But that's for the Unlocked version:
Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zip
I assume I cannot use above boot image for Sprint variant. My question is, where to get this prebuilt boot image for Sprint?
I am on Android 7.0 (2.42.651.6).
Thanks!!
Click to expand...
Click to collapse
That's old info for Magisk, the main Magisk thread has all the up to date files...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Sprint HTC Bolt using XDA Labs
OMJ said:
That's old info for Magisk, the main Magisk thread has all the up to date files...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Sprint HTC Bolt using XDA Labs
Click to expand...
Click to collapse
Thank you. I am following the guide you provided..
"If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
"
Can you please let me know how to Flash Magik zip? I am on Stock Android 7.0 by RUU. Custom Recovery (TWRP) is gone... Downloading to download mode does not have an option to install zip.... Install Magisk Manger gives me this.. Still requires boot image? Thanks.
ctzw said:
Thank you. I am following the guide you provided..
"If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
"
Can you please let me know how to Flash Magik zip? I am on Stock Android 7.0 by RUU. Custom Recovery (TWRP) is gone... Downloading to download mode does not have an option to install zip.... Install Magisk Manger gives me this.. Still requires boot image? Thanks.
Click to expand...
Click to collapse
You flash Magisk v11.1 zip via TWRP.
JediMindTrixx said:
You flash Magisk v11.1 zip via TWRP.
Click to expand...
Click to collapse
He just said he doesn't have TWRP.
ctzw said:
Thank you. I am following the guide you provided..
"If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
"
Can you please let me know how to Flash Magik zip? I am on Stock Android 7.0 by RUU. Custom Recovery (TWRP) is gone... Downloading to download mode does not have an option to install zip.... Install Magisk Manger gives me this.. Still requires boot image? Thanks.
Click to expand...
Click to collapse
Try my post from the Bad Boyz ROM thread. I'm pretty sure that covers it all. If you're already RUU'd you can skip that part, but you will need to unlock your bootloader if you haven't already. I think that factory resets the phone. There's another thread on how to do that via HTCDev that should be stickied, but the process is easy.
https://forum.xda-developers.com/showpost.php?p=71341441&postcount=593
Edit: I see you're already in the process on the other thread. Good luck!
MagisK v11.6 update looped my phone at white screen when taking update from app prompt...
kaw900r said:
MagisK v11.6 update looped my phone at white screen when taking update from app prompt...
Click to expand...
Click to collapse
Worked fine for me.
Update boxes
SilverZero said:
Worked fine for me.
Click to expand...
Click to collapse
There were 2 boxes that could be checked did you check either of them? I checked both and was going to try without checking them but also figured they would update the rom soon and it would be in there. t/u
Hello I'm on 6.0.1 Bad Boyz and I flash this but it doesnt root my phone, I used un-su.zip beforehand
Edit nevermind I RUU'd to Android 7.0 and flashed Bad Boyz Magisk!!!
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
By the way, you can just work with twrp after installing that... stock recovery (fastboot adb) doesn't belong anymore. At first I would suggest that you post the details which are shown in your bootloader.
Furthermore I would recommend just to flash stock rom and testing that case.
Sent from my Moto G (4) using XDA Free mobile app
Ferwerda said:
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
Click to expand...
Click to collapse
First of all, if you read their corresponding threads, you need to do the following when rooting:
- Unlock bootloader/flash TWRP (you did)
- Flash a custom kernel (Vegito or ElementalX)
- And then wipe ART/Dalvik Cache
Second, for LineageOS- you cannot dirty flash custom ROMs, EVER EVER EVER! By this I mean you have to wipe system/data/cache/dalvik etc.- you can ignore Internal Storage and the SDCard/OTG.
You may (should) have to flash the Moto G4 Nougat radio that's floating around XDA somewhere. LOS worked fine for me without doing that, but I know other ROMs require it.
Finally, as a quick heads up, all Moto G4 Plus ROMs work fine with the G4, including any stock ROMs/backups.
Edit: I heavily suggest Magisk or phh SU over SuperSU- Magisk allows you to use SnapChat and Pokemon Go, and phh's is open source.
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
I have the same problem than you... Can you send me the link that you use to fix it?
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
raulcalaca said:
I have the same problem than you... Can you send me the link that you use to fix it?
Click to expand...
Click to collapse
Just flash ElementalX 1.04 kernel (after flashing SuperSu or Superuser or Magisk) when trying to root STOCK Nougat 7.0 as it's designed to thwart any root attempt.
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
can you please give the step by step guide you followed to recover your phone!!!
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