Just want to install one app as System app... - Moto E4 Questions & Answers

I have a stock xt1766, which I use primarily as my kid's Pokemon Go phone. That app is often updated to detect root (despite Magisk), so I need to remain unrooted. But I need to install one app as a system app.
Is there a way to do this without rooting, or, if I do root the device and install my system app, is there a way to de-root and retain the system app? I recall there was a method called "kingo root" or something, but not sure if it's trused of effective on this device...
Currently on NCQS26.69-64-5, getting prompted to install NCQS26.69-64-8.
Thanks for any advice!
Mike

resarfekim said:
I have a stock xt1766, which I use primarily as my kid's Pokemon Go phone. That app is often updated to detect root (despite Magisk), so I need to remain unrooted. But I need to install one app as a system app.
Is there a way to do this without rooting, or, if I do root the device and install my system app, is there a way to de-root and retain the system app? I recall there was a method called "kingo root" or something, but not sure if it's trused of effective on this device...
Currently on NCQS26.69-64-5, getting prompted to install NCQS26.69-64-8.
Thanks for any advice!
Mike
Click to expand...
Click to collapse
You might be able to root with magisk, install your system app, then use fastboot to flash the stock boot.img. which could unroot your phone. But it may not be able to boot because of dm verity or even forced encryption. Kingroot will not work on this device, and is most certainly not to be trusted since it sends your device info to unknown Chinese servers. The only way to successfully unroot, that I know of, is to flash the stock firmware. Which, of course will remove any system changes.
So, short answer, not likely.

madbat99 said:
You might be able to root with magisk, install your system app, then use fastboot to flash the stock boot.img. which could unroot your phone. But it may not be able to boot because of dm verity or even forced encryption. Kingroot will not work on this device, and is most certainly not to be trusted since it sends your device info to unknown Chinese servers. The only way to successfully unroot, that I know of, is to flash the stock firmware. Which, of course will remove any system changes.
So, short answer, not likely.
Click to expand...
Click to collapse
I suspected as much, thanks for confirming.

Related

[T-Mobile D6616] Updated Root Method Request

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.

Modifying Host File Without Root

I just ordered a Moto G5 Plus and expect delivery next week. I am not sure if I really want to root. I would be happy if I could just modify the host file to prevent ads. Is it possible to change the host file without root and still accept OTA updates? Any guidance in doing so is appreciated.
This is not possible as the hosts file lives in somewhere in the root folder or in /su
Your best bet would be to just root which is really no big deal, or use your home wifi router to block ads somehow.
MrTooPhone said:
I just ordered a Moto G5 Plus and expect delivery next week. I am not sure if I really want to root. I would be happy if I could just modify the host file to prevent ads. Is it possible to change the host file without root and still accept OTA updates? Any guidance in doing so is appreciated.
Click to expand...
Click to collapse
Or root and still apply OTA using FlashFire
GopalKaul said:
Or root and still apply OTA using FlashFire
Click to expand...
Click to collapse
I did not know it was possible to flash an update to a rooted stock ROM. With my Moto G3 I was restoring pre-root ROM, accept OTA, re-root, then re-flash rooted ROM data. Modifying the host file is my primary reason to root. I will search the G5 forum for FlashFire instructions.
MrTooPhone said:
I did not know it was possible to flash an update to a rooted stock ROM. With my Moto G3 I was restoring pre-root ROM, accept OTA, re-root, then re-flash rooted ROM data. Modifying the host file is my primary reason to root. I will search the G5 forum for FlashFire instructions.
Click to expand...
Click to collapse
It is hit and miss using Flashfire on Moto devices... sometimes it works and sometimes it doesn't, depends on what you had changed with root. Some people used it with the G 2015, but it often failed. I can't speak to the viability of it on this device though.
There is no way to modify the host file without root, period... You can use something like Adblock Browser or another browser with build in ad blocking though.
You can import host files without root with Netguard: https://github.com/M66B/NetGuard/blob/master/FAQ.md
Dunno if it can accomplish what you want though.
MrTooPhone said:
I did not know it was possible to flash an update to a rooted stock ROM. With my Moto G3 I was restoring pre-root ROM, accept OTA, re-root, then re-flash rooted ROM data. Modifying the host file is my primary reason to root. I will search the G5 forum for FlashFire instructions.
Click to expand...
Click to collapse
If you only get Adblock, fine... But if you remove system apps , then it surely wouldn't work
acejavelin said:
It is hit and miss using Flashfire on Moto devices... sometimes it works and sometimes it doesn't, depends on what you had changed with root. Some people used it with the G 2015, but it often failed. I can't speak to the viability of it on this device though.
There is no way to modify the host file without root, period... You can use something like Adblock Browser or another browser with build in ad blocking though.
Click to expand...
Click to collapse
Can TWRP be booted (not flashed) on the G5 like the G3?
MrTooPhone said:
Can TWRP be booted (not flashed) on the G5 like the G3?
Click to expand...
Click to collapse
Yes. If you have twrp.img it's just
Code:
fastboot boot twrp.img
while you are booted into the bootloader.
Excellent news. Looking forward to my new phone.
MrTooPhone said:
Can TWRP be booted (not flashed) on the G5 like the G3?
Click to expand...
Click to collapse
Yes, but as with the G3 the Bootloader must be unlocked. Remember, that simply unlocking the Bootloader will cause SafetyNet API checks to fail in Nougat without rooting with Magisk, thus breaking OTAs as well.
acejavelin said:
Yes, but as with the G3 the Bootloader must be unlocked. Remember, that simply unlocking the Bootloader will cause SafetyNet API checks to fail in Nougat without rooting with Magisk, thus breaking OTAs as well.
Click to expand...
Click to collapse
If SafetyNet API check fails, understand no OTAs, what about playstore access and updates? With the G3, even though an unlocked bootlader makes the device uncertified, the device still has full access to the playstore. I am thinking some day Google will be shutting down playstore to uncertified devices and those that fail SafetyNet API checks.
MrTooPhone said:
If SafetyNet API check fails, understand no OTAs, what about playstore access and updates? With the G3, even though an unlocked bootlader makes the device uncertified, the device still has full access to the playstore. I am thinking some day Google will be shutting down playstore to uncertified devices and those that fail SafetyNet API checks.
Click to expand...
Click to collapse
SafetyNet failure itself won't stop OTAs, but just about any modifications to boot, system, or recovery will cause a failure.
Apps will install and update, however, some apps check SafetyNet and will not function if it fails... Pokemon Go, Netflix, Android Pay, Snapchat, and most most banking and financial apps come to mind, but there are plenty of others.
I am in agreement that eventually devices that are not certified will not be allowed Play Store access, someday... But SafetyNet is only part of device certification.
I can not find a way to do it.
Overwriting the hosts file on the system with twrp does not work.
Install a zip using twrp with the hosts file, either.
There really is no way to do it without having to root?
Did you try Netguard?
Knutselmaaster said:
Did you try Netguard?
Click to expand...
Click to collapse
Using PIA with Mace enabled works as well.

Root problem (full root not systemless)

Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
zishhaider said:
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
Click to expand...
Click to collapse
I don't understand your goal?
Systemless root IS full root. Your terminology is incorrect.
SuperSU doesn't really support system root on Android 7.
I also dont see the point of making SuperSU a system app. Even though its rather pointless if that is all you require for whatever strange reason then you can just move the Supersu app to the system partition.
There is a better way to stay rooted after a hard reset and it's called FRP.
First there is nothing strange in stay rooted after hard reset, trust me. My friend use this mobile. He needs root for lucky patcher. When first he came to me I rooted it via twrp and after couple of days he came back with custom binary block option and plus he doesn't remember newly created gmail id pass. For me it was hell of a job. So i decided to root it permanently. I am not an expert though but my point was to take full root instead of systemless root. Thanks for clearing that 7.0 isn't supported for full system root. I saw here a rom stock dexoded and pre rooted. Is it better option to install it rather than stock rom?
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
zishhaider said:
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Click to expand...
Click to collapse
Like I already stated Factory Reset Protection (FRP) is already built in to SuperSU.
Just do the following in a terminal then re-install SuperSU:
echo "FRP=true">>/data/. supersu
.

EngineerMode unroot?

back when engineermode exploit backdoor 'thing' whatever you want to call it, was still a thing i seized to opportunity to gain root access, however since then magisk hide has begun failing me and i would like to either find a way to update magisk from v14.0 safely, or to unroot completely (preferably without wiping) as this has started being problematic. I am on the latest oxygenOS update and i used this guide to root (i originaly linked it here but apparently i cant do that, it was on github, called OneplusRoot by a fella named aldur.)
If anyone can help id really appreciate it.
Thanks in advance
Since One Plus removed engineering mode I'm surprised you were able to update OOS and maintain the exploit. Why don't you just unlock your bootloader and root the proper way? Your phone won't melt if you do.
I would like to avoid wiping if possible. I too am surprised at the persistence of root after at least 3 OTAs. At this point I no longer really need root and would rather my phone run smoothly without some applications crashing or not running due to root.
bump?
gbesh said:
bump?
Click to expand...
Click to collapse
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
manor7777 said:
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
Click to expand...
Click to collapse
Well my system doesn't boot with root. I have to manually mount something and start the magisk service.
Which is why I'm not sure how to update as I've been told the updated version has a different file structure that the one I'm on.
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
yohouse2 said:
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
Click to expand...
Click to collapse
no unfortunately i am still waiting for a solution.
gbesh said:
no unfortunately i am still waiting for a solution.
Click to expand...
Click to collapse
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
yohouse2 said:
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
Click to expand...
Click to collapse
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
gbesh said:
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
Click to expand...
Click to collapse
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
yohouse2 said:
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
Click to expand...
Click to collapse
After one of the recent updates, magisk hide started working again and my apps are no longer crashing. It is strange but i guess this situation has turned out favourably after all.

How unroot MI A1 without reflashing?

I ever read how root and unroot with magisk, but it must download and reflashing stock rom to unroot it.
Is there a more simple way to unroot MI A1?
As simple as choose menu > unroot
I really want root my phone, but only after I found simple way to unroot it again.
Thanks
mrtbb said:
I ever read how root and unroot with magisk, but it must download and reflashing stock rom to unroot it.
Is there a more simple way to unroot MI A1?
As simple as choose menu > unroot
I really want root my phone, but only after I found simple way to unroot it again.
Thanks
Click to expand...
Click to collapse
Why? At the very least you will need to uninstall via a flashable ZIP, but this will still mean the dm-verity is probably disabled and the bootloader is unlocked. Any half decent app which detects root will also detect these, and without MagiskHide they will be even more easily detected.
I thought there is a option to un-root phone in Magisk manager with restoring stock boot image.
CosmicDan said:
Why? At the very least you will need to uninstall via a flashable ZIP, but this will still mean the dm-verity is probably disabled and the bootloader is unlocked. Any half decent app which detects root will also detect these, and without MagiskHide they will be even more easily detected.
Click to expand...
Click to collapse
I think I just too lazy too reflashing, beside bricked risk.
TrueMS said:
I thought there is a option to un-root phone in Magisk manager with restoring stock boot image.
Click to expand...
Click to collapse
Yes this option used to update OTA too, but I dont know if it is really restoring stock and unroot or not
----
I think I will root my phone with magisk and hoped not need to unroot again

Categories

Resources