I just bought a Moto g5 plus and rooted it, evidently successfully. Every time an app tried to access the system folder, root access was lost. I could not access the system folder myself to fix the problem without losing root.
Magisk did nothing. Every time I tapped it, it showed nothing but ads.
So I switched to Resurrection Remix 5.8.4 2017-09-17. The versions with Oreo did not work on my phone so I got the latest one with Nougat.
The phone app crashes repeatedly. I wiped/reflashed this time leaving the Google dialer out in the GApps install, I cleared cache after cache, turned off battery optimization for Phone and SIM toolkit, nothing helps
The latest problem I've had is that no apps will download files directly to the SD card. I can access it and move files over, but the whole point of purchasing a large SD card is in case something goes wrong (like installing a faulty rom or breaking the phone on a dryer), my files are safe and accessible once the problem is fixed. It also prevents the phone's internal storage filling up.
The phone this replaced is a Moto g4 play, on that phone I ran a stock room, root stuck like gum on a shoe, and the SD card worked properly.
I have already googled fixes for my issues, nothing in the first page of any search worked.
What I need is a way to make keepvid, Firefox, ACR, and any other program that downloads stuff save it to the SD card AND a working dialer on Resurrection Remix, or instructions on how to make root stick on the stock room, or a *reliable* custom ROM recommendation.
shadow460 said:
.....Magisk did nothing. Every time I tapped it, it showed nothing but ads.....
.
Click to expand...
Click to collapse
This sentence makes me attentively.
I use magisk a long time now and I NEVER saw any ads in it because there aren't any. Where did you download the file?
Also I never heard of losing root when accessing system. How do you realize that an app tries to access system? It seems your device isn't properly rooted, maybe because of a wrong magisk installation. Btw, instead of opening a new thread I would post the problem in the Magisk thread:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page2721
The only place to download magisk.zip and Magisk Manager is here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Moto G5 Plus using XDA Labs
https://forum.xda-developers.com/showpost.php?p=75114774&postcount=236
This is the guide I used to root the phone. All the files I needed came from the links there. I went through step by step and, once I finished I ran Root Checker to verify root. Next I flashed super su and went about installing apps until I realized root access had been lost. I found out by trying to run Root Explorer. At the time Super SU was handling all root access requests normally.
The next day I wiped and tried again. I tried several ways to retain root access, with and without Super SU. When I clicked Magisk, it prompted me to update it and sent me to the Play Store for something called Magisk Manager. That appears to be the only update available for whatever's in that guide. I installed it, but it's straight up adware.
Root Explorer, ES File Explorer, and any app that attempt to access the phone's root (system?) folders will cause root access to disappear when they try.
So I gave up on the stock ROM, backed up that install to my SD card, wiped the phone's memory, and flashed Resurrection Remix with Oreo. It was the first thing that came up by searching "best custom rooms for Moto g5 plus". The SD card access in that rom is completely broken, making it useless to me. I wiped that one too and installed the ROM listed above. I ran that without really setting up any of my apps... I downloaded them and left them on their stock settings. I installed the Google dialer with the Aroma GApps, and was later shown this would cause the phone app to crash, which it did.
Wipe and reflash AGAIN, this time sans Google dialer. Turn off battery optimization for phone and SIM toolkit. Wipe cache and data for both. Boot to TWRP and wipe cache/dalvik. NO CHANGE, phone app *still* reports it has crashed but will allow a conversation.
I decide I can live with that and start customizing apps. That's when I find out the *only* apps with write access to my SD card are the camera, the stock file browser, and ES File Explorer. Another app, FX explorer, shows write access is enabled on the SD card. Firefox, AdBlock Browser, and keepvid all need access to it. I grabbed Firefox hoping the issue was just that the others were simply too outdated to work with Nougat, but evidently that's not the case.
The camera and ES went through some kind of weird dialog telling me to select the root directory of the SD card before they would write to it. It's almost as if ES is functioning as a skin for the stock file browser and those other programs have no permission for that.
BTW, the forum chucked me an error about my IP address already being used once today when I tried to reply to this the first time. I was steamed already and about to Chuck the phone out in the freeway.
Basically what I need is advice on a custom ROM that, as Microsoft puts it, just works.
In case it matters, the SD card is a 200GB SanDisk model, A1 / V10 rated (the phone can't transfer data to it that fast anyway) and there's a ~2500 mAh Newdery battery case attached. There is no USB OTG in the battery case... just a cheap Chinese battery.
shadow460 said:
https://forum.xda-developers.com/showpost.php?p=75114774&postcount=236
This is the guide I used to root the phone. All the files I needed came from the links there. I went through step by step and, once I finished I ran Root Checker to verify root. Next I flashed super su and went about installing apps until I realized root access had been lost. I found out by trying to run Root Explorer. At the time Super SU was handling all root access requests normally.
The next day I wiped and tried again. I tried several ways to retain root access, with and without Super SU. When I clicked Magisk, it prompted me to update it and sent me to the Play Store for something called Magisk Manager. That appears to be the only update available for whatever's in that guide. I installed it, but it's straight up adware.
Root Explorer, ES File Explorer, and any app that attempt to access the phone's root (system?) folders will cause root access to disappear when they try.
So I gave up on the stock ROM, backed up that install to my SD card, wiped the phone's memory, and flashed Resurrection Remix with Oreo. It was the first thing that came up by searching "best custom rooms for Moto g5 plus". The SD card access in that rom is completely broken, making it useless to me. I wiped that one too and installed the ROM listed above. I ran that without really setting up any of my apps... I downloaded them and left them on their stock settings. I installed the Google dialer with the Aroma GApps, and was later shown this would cause the phone app to crash, which it did.
Wipe and reflash AGAIN, this time sans Google dialer. Turn off battery optimization for phone and SIM toolkit. Wipe cache and data for both. Boot to TWRP and wipe cache/dalvik. NO CHANGE, phone app *still* reports it has crashed but will allow a conversation.
I decide I can live with that and start customizing apps. That's when I find out the *only* apps with write access to my SD card are the camera, the stock file browser, and ES File Explorer. Another app, FX explorer, shows write access is enabled on the SD card. Firefox, AdBlock Browser, and keepvid all need access to it. I grabbed Firefox hoping the issue was just that the others were simply too outdated to work with Nougat, but evidently that's not the case.
The camera and ES went through some kind of weird dialog telling me to select the root directory of the SD card before they would write to it. It's almost as if ES is functioning as a skin for the stock file browser and those other programs have no permission for that.
BTW, the forum chucked me an error about my IP address already being used once today when I tried to reply to this the first time. I was steamed already and about to Chuck the phone out in the freeway.
Basically what I need is advice on a custom ROM that, as Microsoft puts it, just works.
In case it matters, the SD card is a 200GB SanDisk model, A1 / V10 rated (the phone can't transfer data to it that fast anyway) and there's a ~2500 mAh Newdery battery case attached. There is no USB OTG in the battery case... just a cheap Chinese battery.
Click to expand...
Click to collapse
In the rooting thread you mentioned it says "Chose your preferred rooting app, superSU OR magisk".
Never use both.
I recommend to use this guide:
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post74673573
As superSU is abandoned and not supported anymore I recommend magisk.
If you say "when I tap magisk" than it's the magisk manager you're using. Magisk consists of two parts: The magisk.zip for flashing through TWRP and the Magisk Manager which is the interface.
Nor magisk neither Magisk Manager is in the playstore! Only use the files from the thread I mentioned above. The Magisk Manager apk is inside the zip and also downloadable in the magisk thread. Normally the manager is present when you have flashed the magisk.zip. Sometimes it is not, than install it just like any other apk. But don't use any other sources than
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
So my advice is flash your actual stock ROM (the one you were on) via fastboot.
Hopefully you made a backup in TWRP because if you don't have a backup of EFS and persist you have a big chance of losing your IMEI/4g/voLTE if you switch from an Oreo custom ROM back to stock.
If you have a backup of EFS save it for your life!
If your IMEI and/or 4g is gone after flashing stock restore EFS and if you have it persist when you have TWRP after the next step.
Flash latest TWRP 3.2.3.1.
Boot into TWRP and flash magisk 16 (it's the most stable one at the moment).
If the Magisk Manager is there don't update it if it prompts you to. If it's not there install the apk found in the magisk 16.zip.
This is it in short form, the rooting guide I posted is more detailed.
I think most of your problems result from the not complete rooting solution.
And one hint: Forget ES, it's a data thief.
Use Solid Explorer, Total Commander or imho the best: MIXplorer. This one is not in the playstore, you find it on XDA:
https://forum.xda-developers.com/showthread.php?t=1523691
Sent from my Moto G5 Plus using XDA Labs
I have two backups: one with the stock rom that was losing root and one with the custom ROM above that I took an hour ago. The phone has had Oreo on it and gone back to Nougat, I think with the stock rom.
I took the first backup when I thought I had everything running stable on the stock rom. Is there a way to unroot it and try again?
Not sure what version TWRP is, whatever was linked to in the root guide.
I'm not sure what EFS refers to and I don't yet know how to flash a room via fastboot. I assume it's similar to installing TWRP.
Ok. TWRP is version 3.2.3-1.
I went into the thread above and downloaded Magisk 17.1, which is claimed to be the most stable release. I downloaded the Magisk uninstaller. Next I booted into recovery mode to restore the stock ROM I had used at first (with my apps loaded on it) and uninstall Magisk 16.7.
The uninstaller refused to "install".
Magisk 16.7 refused to install. (Error 1, failed to install from zip)
Magisk 17.1 refused to install. (Same error)
Super SU installed perfectly, though I didn't load into the OS to play with it.
Now is it sinking in that Magisk is CRAP??
I found the stock ROM over at androidfilehost, matched it to the version I have, and attempted to flash that with TWRP. Another error... this one said invalid zip file format.
I'm back on Resurrection Remix, wondering exactly what else I will find broken in it.
The solution here isn't going to be the stock rom, and I will NEVER attempt Magisk again. It's going to be answering three questions:
1. How do I set global permissions for *every* app on this phone to write to the SD card?
2. How do I keep com.android.phone from crashing?
3. Is there a custom ROM that has these issues addressed?
shadow460 said:
Ok. TWRP is version 3.2.3-1.
I went into the thread above and downloaded Magisk 17.1, which is claimed to be the most stable release. I downloaded the Magisk uninstaller. Next I booted into recovery mode to restore the stock ROM I had used at first (with my apps loaded on it) and uninstall Magisk 16.7.
The uninstaller refused to "install".
Magisk 16.7 refused to install. (Error 1, failed to install from zip)
Magisk 17.1 refused to install. (Same error)
Super SU installed perfectly, though I didn't load into the OS to play with it.
Now is it sinking in that Magisk is CRAP??
I found the stock ROM over at androidfilehost, matched it to the version I have, and attempted to flash that with TWRP. Another error... this one said invalid zip file format.
I'm back on Resurrection Remix, wondering exactly what else I will find broken in it.
The solution here isn't going to be the stock rom, and I will NEVER attempt Magisk again. It's going to be answering three questions:
1. How do I set global permissions for *every* app on this phone to write to the SD card?
2. How do I keep com.android.phone from crashing?
3. Is there a custom ROM that has these issues addressed?
Click to expand...
Click to collapse
Stock ROM has to be unzipped in your Fastboot folder on PC and flashed from there. That's why you've got an invalid zip error message.
If you think magisk is crap you will have problems in the future as superSU is dead.
You should read the instructions for installing magisk and how to use the uninstaller.
You have such a lot of problems that I recommend to do a full wipe and install any Oreo custom ROM you want, they all are stable. AOSP Extended or Pixel Experience are good choices. If you want to root them try superSU 2.82 SR5 (the latest stable) or use magisk 16 (I said before that it's the most stable, not 17.1). Do a full unroot if you change from one rooting method to the other. There's a script called unsu.zip from Osmosis which deletes all traces of every rooting method:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
If you know what you're doing it's an easy job and magisk is a very cool piece of software if you use it correctly.
Sent from my Moto G5 Plus using XDA Labs
Will look into those when I get home. I patched up the g4 play that got crushed by a clothes dryer (oops) and will run it a few days while I work out the g5 plus.
For full unroot do I need to return to stock recovery or can I keep TWRP?
Does Pixel experience have anything to do with the Pixel launcher?
Last question... if I flash the stock room do I still need to unroot?
I actually patched up the g4 play that got crushed when I was moving a clothes dryer and am running it, so I have some time now to work out any issues with the g5 plus. I'll probably go ahead and try one of those custom rooms with SuperSU. I don't use any apps that require non-root and by the time I need to root something again there will probably be a new Superuser type app out there. If I go with the stock rom, I don't see much of a choice, but I'm not thrilled about Magisk.
Let me get on the download for one of those custom rooms you listed...
I hear bad things about 17.1 for Magisk. Find the Magisk 16.0 and you will be fine. But follow the instructions first.
Also there's a thread somewhere for flashing actual stock Nougat zips according to your version (may it be RETUS or RETEU) if anything has gone horribly wrong as it sounds you have at least a working TWRP. Once you got that going, then reboot into recovery, back it all up.
Then format system, cache, data and dalvik (MUST always be done on clean flash). Then flash desired Oreo rom. Then flash Gapps. Then flash Magisk. Then boot it.
I found the thread on TWRP flashable stock roms and am downloading one now. I also found my credit card statement, which reminded me how much I spent on that electronic curse... and I ought to actually put some software on it and use it. Been running the g4 play (harpia) for a bit as I got a semi decent quality screen to replace the broken ones. Parts are getting harder to find... which is the same reason I retired my last Galaxy. (actually I think that one is just missing the ROM...)
Anyway, I backed up the EFS on the G5 plus using TWRP. I plan to try to TWRP flashable stock rom and give Magisk another shot since I have a working phone I can use while I set the G5 up (I have all the time I need).
I think I understand how to recover the imei if it gets deleted.
Update: TWRP flashable stock room appears to be working. Gonna make a nandroid backup of it, grab the Magisk 16 download on *this* phone and then head off to bed. Will attempt root again later this week.
Thanks ya'll!
Next step was getting Magisk 16 on there with the TWRP flashable stock ROM. That was a simple process. I put Joey krim's Root Checker and Root Explorer on also and ran them both to try and remember create the loss of root problem. Root stuck like duct tape... for now.
I looked through Magisk 16's settings using it's manager. I'm not 100% sure what all of that does so I left them alone.
There were some tweaks in RR I liked such as the battery var and swipe the status bar for brightness. If there's a way to run that kind of thing, I'm all ears.
Going for round 2 with the Moto G5 plus. I haven't had any trouble since September 20 aside from needing a screen replacement (I dropped it).
Wife broker HER screen on a Galaxy J3, so she's getting a G5 plus. It's backing up its stock ROM now. I made a backup of the install on my phone with what I consider essential apps. I'll flash that in but put her efs on it from the new to us G5 plus not mine from my phone.
From there everything should be the same save for the phone number, esn, and SD card, plus whatever she puts on it.
Should be a lot faster than her in rootable AT&T J3.
Related
Hey I'm looking around and found 2 interesting posts.
http://forum.xda-developers.com/lg-...fficial-cyanogenmod-13-lg-g2-t3264508/page422
http://forum.xda-developers.com/lg-g2/help/starting-root-recovery-custom-rom-t3440752/page1
Click to expand...
Click to collapse
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
andrew2432 said:
Hey I'm looking around and found 2 interesting posts.
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
Click to expand...
Click to collapse
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Code:
su
mount -o remount,rw /system
rm /system/xbin/su
rm /system/bin/su
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
blastagator said:
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe everything
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
Click to expand...
Click to collapse
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
andrew2432 said:
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
Click to expand...
Click to collapse
Recovery lives in /recovery partition, so I guess I should clarify, don't wipe EVERYTHING, lol. I can't remember if I enabled ability to wipe recovery, DONT DO THAT :silly:
edit: Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
But, as for everything else, recovery will live through wiping /system /data, etc. You need to backup anything you want to save though. Wipe will destroy everything.
Other than that, you pretty much got the rest.
edit 2: http://download.cyanogenmod.org/?device=d800
See image for ROM vs CM Recovery.
CWM = Clockwork Mod (a different recovery)
CM = CyanogenMod (a ROM)
.
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
EDIT: awesome, I have to run all Internet functions off of the sprint lte network and was downloading one of those behemoths during that posts....that let's me know my efforts aren't in vain
andrew2432 said:
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
Click to expand...
Click to collapse
Please read my edits and don't kill your phone. I am not always so timely in my responses :good:
Other than that, good luck!
There are tons of posts that go into more detail about what I wrote. Just make sure you have a plan before you do it. Think: Measure twice, cut once.
This g2 I found service locked while cleaning out a rental property. I have a galaxy s5 stupid sprint for my primary. I use the g2 for...well everything game and other related. until my Hotspot mod on my galaxy suddenly stopped working on lp. I blame the man
Äptiva is the one I read about a gutted 802 into an 800 or something, got you guys confused!!
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
andrew2432 said:
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
Click to expand...
Click to collapse
CM13.
If you're trying to get safety net to work, you have to enable magisk hide (in the magisk app)
Also, if you're using xposed, you can't use safety net.
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
andrew2432 said:
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
Click to expand...
Click to collapse
If the safety net test app passes, it should be working. perhaps downgrade your pogo a version or two, maybe they added something else.
Well, it's on a WiFi only, no SIM device...
I'm thinking this is the issue I'm experiencing now. Which may stem from an update. An older apk is a good idea, I was able to log on with magisk v6 a bit a go and when magisk 7 and 8 first came out I could.
Good afternoon,
After MUCH research, I have arrived at the conclusion rooting the D6616 with T-Mobile's likely final Z3 build for 5.0.2 (Build 23.1.C.0.399 and, really anything past KK) is no longer possible without involving Kingroot.
Why does this matter? Because there may not be a feasible way to remove the most recent builds of Kingroot from the D6616 ROM. Using Kingroot's own uninstaller in the App settings fails and factory resetting using the ROM/stock recovery threw my phone into a bootloop. Other users report it successfully factory reset their ROM with kingroot installed as a system app and their device no longer rooted. I attribute the variety of outcomes to different software builds and Kingroot versions.
It seems as though the only working root method also uses ZXDualRecovery. Though I have not tried it, all procedures that show the ZXDualRecovery method of pushing recovery and superSU involved rooting the device with Kingroot first and removing it after SuperSU is installed. This appears to be the only still-working method of acquiring temporary root long enough to install recovery. The only way to remove Kingroot is to use flashtool and a new Sony TFT, which also removes root and recovery.
Has anyone successfully been able to pull off rooting a D6616 lately? I want to keep this phone but it is unfortunately useless to me without working root so I'll likely be returning it if nobody still has one that's running the last software with a locked bootloader.
I would really appreciate any help anyone can give.
I believe I have done it! I think SuperSU is ever so slightly ahead of Kingroot.
What I did:
1) Rooted via Kingroot app on Google Play. Run rootchecker after it's done its business to make sure. DO NOTHING ELSE IN THE APP. Doing so may prevent SuperSU from kicking its ass later.
2) Downloaded and upacked to desktop the file for Xperia Z3 from here:
http://nut.xperia-files.com/path/XZD...ecovery_2.8.26
Z3-lockeddualrecovery2.8.26.-RELEASE.combined.zip
3) Disabled antivirus
4) Installed USB drivers via Windows 7 plug-n-play. Unplug phone.
5) Downloaded SuperSU recovery flashable zip from here:
http://www.supersu.com/download#zip
6) Ran install.bat from extracted ZXDualRecovery zip
7) Enabled developer options in phone, enabled USB debugging, revoked USB devices, rebooted phone, plug in phone.
8) Connect Phone, wait for device to register in windows.
9) Okayed communication from PC.
10) Place in USB Install Mode on phone.
11) Choose option 2 to install to device rooted by SuperUser. Kingroot has blocked option 1 (old method)
12) Enter TWRP (Automatic) and go to Backup, check all boxes, create Nandroid by sliding the slider
13) Reboot, ensure phone boots. Put SuperSU.zip on the external flash drive. Go to your new App: NDR Utils. Choose TWRP as Primary Recovery. Choose Reboot to Primary recovery
14) Flash zip for SuperSU. DO NOTHING ELSE. Do not wipe cache, do not fix permissions. Click REBOOT.
15) Launch SuperSU App. Attempt to update Binaries. It will not, but it will detect Kingroot, and somehow can get rid of it itself using onboard capabilities. It will do so and update binaries.
16) Reboot (Automatic via SuperSU)
17) Check to make sure SuperSU binaries installed by launching the app.
18) Reboot to recovery using the steps from step 13) above.
19) Create another backup using step 12) above
20) Reboot and DONE.
To the best of my knowledge, nobody has indicated how to do this in a clear Step-By-Step for the final build of this ROM. So because I've troubled you all for small chunks of the process I figured I would.
This applies to T-Mobile's likely-final software release for the Xperia Z3 android 5.0.2 on build 23.1.C.0.399.
DISCLAIMER TO ANYONE ATTEMPTING THIS: It appears Kingroot is "onto" what it is being used for. Given the behavior of this application, there is no reason for anyone to believe it is not a malicious program, but it is a necessary evil for this purpose. Newer versions of SuperSU are capable of removing Kingroot on their own, but alternative methods may be necessary. I attempted an earlier version of SuperSU and it was incapable of removing Kingroot.
It might remove via debloater. This is the only way to remove the system apps on this phone reliably, so you WILL need it if you intend to keep the bootloader locked. I couldn't get any root-enabled appstore app to do it including ES File explorer and Titanium Backup. It looks like you need a computer to remove system apps on this phone. Fantastic. Debloater works great though so don't be afraid to use it. Use the filter to search for Apps. You can remove them, but they will not be gone until you reboot your device. Hooray no more filecommander and lookout! Debloater can be found here:
https://forum.xda-developers.com/and...bloat-t2998294
Plug in your phone. Give it root access. Easy peezy.
Then Xposed current framework and installer:
https://forum.xda-developers.com/sho....php?t=3034811
Version 3.1.1 fixed the bootloop problem, so you shouldn't need the fix zip, or at least I didn't. But if you do, you can find it here:
https://dottech.org/187028/how-to-fi...-z5-z4-z3-tip/
Flash the framework for your device in recovery (arm) and then the installer APK from the ROM using a file browser.
FINALLY Youtube Adblock and minimized playback. SCORE!
I think that's about it. That's literally the best we can currently hope for from this device. I think there is an Xposed module to heavily alter the look of the ROM here but I have not tried it. Plus it only claims to work w/ 4.4, and we have 5.0.1.
https://forum.xda-developers.com/z3/...6#post71601966
For devicewide adblocking I use DNS66 since there are no proxy settings for adblocking on this device, unless I'm missing something. I really hope I am. This means there's no native adblocking.
Xposed modules worth using you can find by searching in the Xposed store: Blurred System UI (LP), Gravity Box [LP], RootCloak, Xperia/AOSP NavBar Buttons, Xperia Super Radio, YouTube AdAway, YouTube Background Playback. And of course DNS66 (PlayStore).
I have tinkered with the rest and find them of no value.
I followed the steps but SU didn't ask to update anything. It just opens up and everything is fine?
Then all I did was unistall kingroot(purify) and it looks like it's gone, but is it?
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
stef-nix said:
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
Click to expand...
Click to collapse
Were you able to install twrp without rooting first on your PC? It doesn't work for me. I did option 3, install on unrooted device.
Are you able to systemless root?
When I run the installation it fails at step 3 on the install bat.
Hi, a bit of an old thread, but has anyone had any success rooting the D6616 without using Kingoroot or Kingroot? Both are malware which are designed to not be fully removed and be as resilient as possible, and uninstall does not actually uninstall them...
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
i followed these steps, and have gotten to the point where you flash supersu and reboot, but i'm stuck in a reboot loop now. wanted to use this old z3 as a dedicated audio player, and needed to root for some audio enhancements...
edit: i did have TWRP for a minute, but now when i go into recovery it's the stock recovery again, with options only to continue booting, boot to safe mode, factory recovery or power down. the first two options return to a boot loop. can/should i attempt to use flashtool, or factory recovery? i don't want to accidentally wipe something i might need in the backup.\
UPDATE 10/19: I was able to get back to ground zero using Sony's xperia companion software repair. Flashtool 9.25 and 9.26 would never successfully install flashmode drivers, nor would it display the stock .ftf file.
fierogt42 said:
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
Click to expand...
Click to collapse
this new method seems to fail for me on both of my old z3's. does the method you're referring to involve downgrading to 4.4.4? i've done some extensive searching of this forum (and the android development ones as well) but don't seem to be able to find any other info.
Hello,
Right now I'm having the biggest issue with Snapchat, I've read numerous posts that say that if your phone is rooted or you have XPosed framework installed then Snapchat will not allow you to login, this is the issue I'm having.
I don't have a backup either of the latest data and app of Snapchat to put it on my phone and Titanium Restore it.. Or else I would have done this first.
I don't have Xposed installed (app) but I'm not sure about the framework? How do I check, or remove it in case I do have it installed? I faintly remember installing it.
Is there any alternative to allow me to login to Snapchat?
Thanks!
Download the latest super user zip file.. Lets say you know how to reboot to twrp.
*First of all open the super user app and go to the setting and unroot it.
*It would ask you to confirm it, after that a new screen will pop up, cancel it has to with wiping all super user and recovery files.
*So make sure you get the superuser from xda latest..then put it on your sd card or internal memory.
*Do not flash it yet.
*Unroot and reboot the phone, then login to snapchat. It should be successful.
*Reboot to twrp and flash the zip file
Good luck
This worked, thank you!!!
You could also use a root hider or switcher, such as magisk, and not have to switch and do reboots each time
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
hey all!
I'm a newb....
I have a rooted 6p with the factory image installed, twrp recovery.
I don't recall doing a backup before rooting.....yeah I know not smart....didn't know what the heck I was doing in this process....never rooted a phone.
I installed Magisk......then in my infinite wisdom installed supersu
the phone for the most part works fine, but I am having a problem running frida, it complains about magisk hide. I have removed all the magisk modules...
I am hoping I can some how clean up this phone and completely remove magisk.....and get frida running.
am I toast without a backup?
what is the best way to completely remove and uninstall magisk.
tried to run magisk install again and also magisk uninstall gives me error 1, which I see there are videos for dealing with on youtube...though haven't gone done that rabbit hole
I am quite comfortable using adb
I see bits of magisk all through the file system, just not sure if I should be deleting as I might be getting myself into more trouble.
TIA
Well if you don't mind starting fresh (backing up all your data) as this would erase everything and set your phone back to "factory stock" on the latest official version from google and its as easy as clicking one batch file to get things sorted. You may have messed up some stuff permanently on your system partition by installing/uninstalling two incompatible root solutions etc.
Link: https://developers.google.com/android/images#angler
Direct link to latest file: https://dl.google.com/dl/android/aosp/angler-opm7.181205.001-factory-b75ce068.zip
Then you just plug your phone in and run the 'flash-all.bat' file.