I've dug around here for about 20 minutes and don't see any successful root for the Moto G XT-1028 (Android 4.4.4). I found a way to ROOT it! The particular Moto G XT-1028 I had could not be rooted by any method I tried (that included about everything) until a couple days ago I found a version of the Kingroot App and it rooted SUCCESSFULLY! As much as I'm not a fan of Kingroot and similar root apps you can't knock it if it is the only way that works. The Kingroot that worked is version V4.5.0.803. Older versions I had tried did not work. I'll attach it here. This is really a sweet little phone and glad it finally has root. :good:
droidzer1 said:
I've dug around here for about 20 minutes and don't see any successful root for the Moto G XT-1028. I found a way to ROOT it! The particular Moto G XT-1028 I had could not be rooted by any method I tried (that included about everything) until a couple days ago I found a version of the Kingroot App and it rooted SUCCESSFULLY! As much as I'm not a fan of Kingroot and similar root apps you can't knock it if it is the only way that works. The Kingroot that worked is version V4.5.0.803. Older versions I had tried did not work. I'll attach it here. This is really a sweet little phone and glad it finally has root. :good:
Click to expand...
Click to collapse
Is this for 4.4.4?
I checked for Root initially by using ROM Toolbox which will warn you if you don't have root. It will not "Freeze" and App unless it has root so I froze an App and it worked. I'll post some screen captures here in a while showing the exact build and proof of Root.
Yes it is 4.4.4 I have on this phone.
Screen cap of my exact build. Also a screen cap after Kingroot success - the actual 'Success' screen only flashed for a second and then the screen below shows root access. Weird the second screenshot keeps coming up a Zero byte file - doesn't seem to save. Working on that....
More info: This version of Kingroot seems to have it's own root and you cannot install SuperSU (not so far anyway - I haven't tried everything yet). But it does allow root access for sure. However based on what I have found so far if you reboot you may lose root. But it is a very quick and simple process to re-root. Just run the App - wait a few seconds it you have ROOT. It is also similar in how it works like SuperSU in that it asks you to Allow or Deny root access when an App or function requests root access.
droidzer1 said:
Screen cap of my exact build. Also a screen cap after Kingroot success - the actual 'Success' screen only flashed for a second and then the screen below shows root access. Weird the second screenshot keeps coming up a Zero byte file - doesn't seem to save. Working on that....
Click to expand...
Click to collapse
This is awesome!!
T10NAZ said:
This is awesome!!
Click to expand...
Click to collapse
I had some trouble getting screen caps as the built in OS (power button + vol down) didn't work but installed this screenshot app that shows a couple from Kingroot screens in attached pics:
Here's one from Galaxy tools ( Yes I know it's not a Galaxy but it still works on the Moto G and it shows the details like it being an XT-1028 and states it has ROOT access right on the same screen.
This has been posted about many times, especially by me. This root is temporary. And it becomes extremely unstable after a while and your phone starts to crash and you're forced to reboot, losing root. Sorry to rain on your parade, but it doesn't exactly work still
Teet1 said:
This has been posted about many times, especially by me. This root is temporary. And it becomes extremely unstable after a while and your phone starts to crash and you're forced to reboot, losing root. Sorry to rain on your parade, but it doesn't exactly work still
Click to expand...
Click to collapse
I do see that it doesn't hold root if you reboot but I see it as stable about half the time now that I've played with it a bit. Sometimes apps start to crash but upon reboot and re-root sometimes it is totally stable. Apps that I have frozen when rooted stay frozen. I'm also looking at it's sister app 'Purify' which was downloaded from within Kingroot as 'Kingmaster'. It says it can keep root. I'm working on testing that. Can you give me a link to other discussions on this? This is a version of Kingroot that just came out a few days ago. In doing a search I do not get any hits here on this version of Kingroot
droidzer1 said:
I do see that it doesn't hold root if you reboot but I see it as stable about half the time now that I've played with it a bit. Sometimes apps start to crash but upon reboot and re-root sometimes it is totally stable. Apps that I have frozen when rooted stay frozen. I'm also looking at it's sister app 'Purify' which was downloaded from within Kingroot as 'Kingmaster'. It says it can keep root. I'm working on testing that. Can you give me a link to other discussions on this? This is a version of Kingroot that just came out a few days ago. In doing a search I do not get any hits here on this version of Kingroot
Click to expand...
Click to collapse
Look at my threads and posts in my profile. I tested the new one. It's a root, maybe more stable. But what we all want is perm root which we haven't accomplished yet. I have high hopes future versions of kingroot give full perm stable root
Finally caught this one:
After playing with this a couple days I admit it is sometimes stable and sometimes not. I believe Kingroot tries a lot of different options to root a phone as it gets the methods online during rooting and I believe it does not always use the same method for a particular phone. So sometime it works better than other times and it has even failed to root at all a few times. It was stable for a 12 hour test but some things will quickly destabilize it - like trying to install Busybox. At best you can get root access to fiddle with some things like making a custom boot screen etc. Any reboot will remove root and phone will be stable again but I did notice Kingroot as an app is running and I normally will stop it - no need for it if you aren't running in root mode.
I've been using kingroot as well, even before the .803 release (it was like .7xx i think when it first worked for me, about 1-2 months ago)
For me, it never fails to root. However the root destabilizes after approximately 5-15 minutes every time. Its literally just enough time to run titanium backup, or some other important thing before it starts going to crap and needs a reboot.
Still its a step in the right direction. I absolutely hate the pre-installed VZW bloat: Navigator, sync, NFL.
I'd be satisfied with a locked bootloader if i could just have perm-root. However temp-root is fine for now.
Yeeeeessss this jus made my weekend. Thanks for the update 4.4.4 rooted. Well temp root but better than nothing)))))
Related
Hello. I'm new here and finally have an Android (a Samsung Fascinate.) I installed Z4Root yesterday, and managed to root my phone. It worked great! Later in the night I downloaded the new update for the Fascinate, and even after that the phone was still rooted.
This morning, though, the phone was no longer rooted. None of the programs I could use hours before like Titanium Backup said I did not have root access. Worse still, I could not get Z4 to work properly. It gave me the Temporary, Full, and Unroot options. Each option seemed to work fine when I tried to use them, but once it "finished" and went back to the home screen, still not rooted, and eventually caused Z4 to crash, and eventually I had to reboot the phone as well.
Any ideas? Sorry, I'm new to all of this! Thanks!
I have tried to UNROOT my Verizon Note 3 (SM-N900V) 4.3/MJE using Kingo, but Kingo shows that I am NOT rooted and doesn’t provide the “Unroot” option as it should. I used Kingo to root my phone, and I haven’t installed any custom ROMs or recoveries other than upgrading to SuperSU Pro and installing Xposed Installer.
I’ve watched dozens of videos on unrooting, but little without Kingo. Unfortunately at the end of these videos, they all show that the Knox warranty being voided (0 x 1) and some can’t remove the Custom Padlock screen. Just wondering if anyone has successfully unrooted and not having the Custom Padlock screen or Knox tripped.
Any help would be greatly appreciated!
Also, sorry if I didn’t post this right as this is my very first post or thread.
Easy Solution to Kingo Unrooting Found
I contacted Kingo about a week ago and gave them a decent donation along with my question. Unfortunately I never got any response back whatsoever. I’m thinking that they are really busy. So, I went ahead and took the leap and did the work successfully myself.
1. I uninstalled Xposed Installer through its own uninstaller. Then I removed it along with Titanium Backup, and the Pro version through CleanMaster with no problems.
2. I was able to uninstall SuperSU through it’s own “Uninstall” feature, then rebooted.
3. The first thing I noticed was the “Custom” and Padlock logo still on my screen at bootup, but the great thing was that I booted up without any problems.
4. I had discovered that the SuperSu Pro apk was still present through the phone’s Application Manager and was able to uninstall it from there.
5. Finally and fearfully, I rebooted one more time.
Everything booted normally again, and this time, the “Custom” logo and padlock were finally gone! I checked the Knox counter and both flags showed 0 x 0. Kingo had a problem with their servers in early February and I tried to root about 15 times over a period of about ten days or so. Suddenly one evening, I was able to successfully root within 3 or 4 minutes, and it really was a one click ordeal. Just be aware that you may not be able to unroot with their program. Don’t fear. Unrooting manually the way I did reveals absolutely no traces of a previous root or that the phone had been tampered with. I’m not sure that anyone who has flashed a custom ROM or recovery would have the same results though, so proceed with caution.
So I can successfully install superuser v2.40, but it's not working with one of my apps (puzzle and dragons). I have been told me to downgrade to 2.25, but I have been having issues.
The problem is no matter what, when I flash 2.25 it gets stuck in a bootloop. Flashing it on stock, and even flashing it over 2.40, and flashing it over 2.40 when clicking the replace button in the superuser app. What am I doing wrong? Is 2.25 not compatible with my phone?
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
experience7 said:
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
Click to expand...
Click to collapse
Thanks for the reply. On the game's forums, I have been told that masking does not work (if you look at xposed rootcloak it says it's not compatible). And some users have been able to get the game to work with certain versions. I am on the latest binaries and it still doesn't work. The only way to get it to work is to unsinstall SuperSU and reflash it every time I want to play.
On some forums I've read that SuperSU has got a function to "hide" or "temporarily disable" it... Take a look at the app. Hopefully this feature hasn't been removed and maybe that's enough for you to get the game working. It's not a perfect solution but at least you don't have to uninstall / reflash every time. Let me know if it worked
Hello xda.
A few weeks ago I started getting this notification telling me a new system update was available but when I tried to do it, it wouldn't install. I quickly discovered it was because my device was rooted. I followed this guide to get the update (more to get rid of the annoying notification really) ; I made sure do download the right stock image (my device is a XT1541 2 GB) and to flash all the system.img_sparsechunk files (there are 8 in this case) and it went smoothly (booted alright) up until the rooting part.
Basically, I followed RootJunky's video tutorial but after applying the root I can't get past the bootloader's warning screen. The only difference between me and RJ is both TWRP and SU I used are more recent versions (the latest ones).
In the end I just restored the backup I had made "just in case" before the manual update (boy am I glad I made this one) and my phone's back to working order, except not updated.
So here I am : what can I do about it? Is it still possible to root this phone (youtube commentaries indicate I'm not the only one with this issue)? Worst case scenario, is there a way to get rid of the update notification?
Any help is appreciated.
You'll need a systemless root.
Broadcasted from Zeta Reticuli
How to root ANY Moto G 2015 model on Marshmallow
Thank you both for your answer.
Turns out the method linked didn't work for me. Not only was the root not applied according the supersu app, but I still got an update notification after 'rooting' the phone (even though I checked for update after booting the newly installed rom for the first time and there wasn't any).
I decided to go a different route and used Titanium Backup to freeze the Motorola Update app. Hopefully this will do the trick of sparing me the notifications until I can figure out how to get OTA updates.
Isley_FR said:
Thank you both for your answer.
Turns out the method linked didn't work for me. Not only was the root not applied according the supersu app, but I still got an update notification after 'rooting' the phone (even though I checked for update after booting the newly installed rom for the first time and there wasn't any).
I decided to go a different route and used Titanium Backup to freeze the Motorola Update app. Hopefully this will do the trick of sparing me the notifications until I can figure out how to get OTA updates.
Click to expand...
Click to collapse
No offense, but if you didn't have root then TiBu wouldn't work properly... Obviously the rooting worked.
Rooting itself doesn't prevent updates or there notification, it just keeps it from being applied properly. Freezing the app in TiBu should prevent it though.
acejavelin said:
No offense, but if you didn't have root then TiBu wouldn't work properly...
Click to expand...
Click to collapse
I forgot to mention I restored my functional backup when I saw my manipulations didn't work. I used TB after that.
Isley_FR said:
I forgot to mention I restored my functional backup when I saw my manipulations didn't work. I used TB after that.
Click to expand...
Click to collapse
Fair enough..
Quick update : after a couple more tries I successfully rooted my phone by following this method.
I now have the latest stock rom and it's rooted
Thank you for existing XDA! :good:
Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim
same here
Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.
I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.