Related
Bought the unlocked Moto X, and loving it so far.
But there are a few things I want changed: I want easy access to block certain permissions to certain apps, block ads, see how much percent of the battery is left in the top bar along with the icon.
If I understand correctly, there are two ways to achieve those things: Get root access and install apps which require superuser access, or install a custom ROM.
What would you recommend? Is there a custom ROM that can even be installed on the Moto X? How mature is it?
Thanks! Just trying to see what my options are.
I just unlocked the boot loader then installed twrp which will ask if you want to root the first time you boot into it. I then installed xposed and gravity box. It's the best combo I have for now.
Sent from my XT1060 using Tapatalk
Thanks! Now I see some keywords - will be reading more about all this stuff
So if I understand correctly, you didn't install a custom ROM? What factors went into this decision?
Roms aren't needed because most of us can do customization ourselves with xposed modules. Unlike sense and touchwiz, Moto adds very little bloat so there's no need for any tweaks a rom may promote since the device has never been laggy for me. GravityBox is a very useful app to have. Additionally you can use modules like Xprivacy and MinMinGuard to help with restricting data apps have access to and toning down ads, respectively.
Thanks, guys!
Will follow your advice here - I'll stick with the stock ROM.
Already unlocked the bootloader (super easy).
Now I need to install TWRP, but to do that I need software which is called mfastboot
This thread
http://forum.xda-developers.com/showthread.php?t=2603358
gives this link for the mfastboot software
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
But it never says who developed it, and where it actually comes from. Do we just need to trust it?
sksol said:
Thanks, guys!
Will follow your advice here - I'll stick with the stock ROM.
Already unlocked the bootloader (super easy).
Now I need to install TWRP, but to do that I need software which is called mfastboot
This thread
http://forum.xda-developers.com/showthread.php?t=2603358
gives this link for the mfastboot software
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
But it never says who developed it, and where it actually comes from. Do we just need to trust it?
Click to expand...
Click to collapse
It´s made by Motorola themselves. mfastboot was made to flash Motorola devices since normal flashboot can´t or something like that (can´t remember )
sksol said:
Bought the unlocked Moto X, and loving it so far.
But there are a few things I want changed: I want easy access to block certain permissions to certain apps, block ads, see how much percent of the battery is left in the top bar along with the icon.
If I understand correctly, there are two ways to achieve those things: Get root access and install apps which require superuser access, or install a custom ROM.
What would you recommend? Is there a custom ROM that can even be installed on the Moto X? How mature is it?
Thanks! Just trying to see what my options are.
Click to expand...
Click to collapse
Permissions (Only works on 4.3-4.4)- LINK
Ads- LINK
-Or-
DO A LOT WITH THIS
gokart2 said:
Permissions (Only works on 4.3-4.4)- LINK
Ads- LINK
-Or-
DO A LOT WITH THIS
Click to expand...
Click to collapse
Once rooted, AdAway is a really good app. I like how it uses the phones Host file, the same method I use to block ads on my computer.
I went with the xposed way.
Everything works like a charm.
Until I got a message "New system software available!" It asks me to upgrade to 4.4.2.
What does this mean? Do I have to revert all changes I've done so far? I clicked No, maybe later just to be safe. But what is usually done in this scenario?
sksol said:
I went with the xposed way.
Everything works like a charm.
Until I got a message "New system software available!" It asks me to upgrade to 4.4.2.
What does this mean? Do I have to revert all changes I've done so far? I clicked No, maybe later just to be safe. But what is usually done in this scenario?
Click to expand...
Click to collapse
It would probably fail if you did take the update since you have made modifications to the Stock ROM. You have to be 100% Stock without any modifications to take the Update.
I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.
sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Why did you need root for the Google now launcher?
mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?
Your original post made it seem like you need root for double tap to wake and Google now launcher.
sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).
HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?
is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.
Hi, I have been seeing significant lag of my phone and various times to the point that my phone becomes inoperable for a period of time and after the phone recovers it never goes back to full speed., I have to restart. I'm stock not rooted anymore and recently formatted and started from scratch but see no improvement. This is especially annoying when running android auto at which point the phone and the app barely work. Any suggestions? I don't think its a better thing because i had it happen at 60 and at 40 though definitely see it more at 40 or less. Is there a good way to see what app might be causing this?
Install a different kernel. Stock is garbage
Sent from my Nexus 6 using Tapatalk
I don't think k I want to root again.
You don't need root to install a custom kernel. In fact you don't even need to install TWRP. Using ADB you can flash the custom kernel. Just make sure you have USB debugging enabled in Developer Options and make sure your bootloader is unlocked.
Strephon Alkhalikoi said:
You don't need root to install a custom kernel. In fact you don't even need to install TWRP. Using ADB you can flash the custom kernel. Just make sure you have USB debugging enabled in Developer Options and make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Same exact issue here. F*** Google for screwing up our stock phones and not fixing them. What would you suggest for a kernal and rom. It has been a long time since I was rooted with a custom rom but I can't take this for another day.
jspector said:
Same exact issue here. F*** Google for screwing up our stock phones and not fixing them. What would you suggest for a kernal and rom. It has been a long time since I was rooted with a custom rom but I can't take this for another day.
Click to expand...
Click to collapse
Hello... I think all ROMs perform the same in term of fluidity and speed. Some have different features and customization options. I run Pure Nexus on my N6, N6P and Pixel XL. All use ElementalX kernel. I like this configuration. But there is a lot of different possibilities.
I suggest you to look at the forum and read a little bit the first posts of the different ROMs/kernels and see what they have to offer. :good:
Good luck...
I've had this same exact issue. I thought about switching back to MM because I had great battery life on MM. I also thought about flashing Franco Kernel and go from there. It is one that has the option to hide that the bootloader is unlocked. I don't really want to have my bootloader unlocked, and I don't think I can make changes to the kernel easily without having it rooted, something else I also don't want to do. Maybe MM is the best option. Google is still sending out security updates for MM.
Well problem solved I should say. Used nexus root kit to root and install Pure nexus. Only issue I had was I had a gapps from 2015 that crashed everything so I reinstalled with a new gapps. Working great and the speed is back.
Then unless you wanted an old copy, you downloaded the wrong version of Pure Nexus. The latest version includes the Google apps in the ROM, eliminating the need to flash a GApps package.
Hello Guys, I would like to confront a problem I encountered during my time with this phone.
I bought it a week ago and I unlocked the bootloader right away and then rooted it via magisk.
The phone UI felt quite laggy since the first time I used it. I come from a Oneplus 3.
All the reviews state that the experience with this phone is snappy, but it is much slower than my (now dead) OP3, so I need to check in to know if it's a placebo effect or if it's true.
Scrolling through nova launcher drawer is slower, pulling up the notification shade often lags a lot, scrolling through reddit stutters.
I'm on the V9.6.10.0.ODIMIFE version.
I tried reinstalling everythin from scratch, by further unlocking the system with "fastboot flashing unlock_critical" and then using Mi Flash Tool to install the rom found in this OTA dump thread.
I tried doing an antutu benchmark that returned a value of 113000, instead of the expected 130000 or so.
I checked some parameters via kernel adiutor and it all seemed in order (frequencies, schedulers and such).
The phone is original (as confirmed by xiaomi's site).
Please tell me this is software related since this is a new device and that it will be solved.
Edit: better english, added some detail.
Flash again everything to stock, don't root...and don't do an restore backup that google will offer you when you first boot your newly fresh phone.
Install and setup everything again manually, and then test your phone for a day.
I think that you messed up something with root, I did the same, and only fresh new install with manual setup and install of apps step by step fixed the problem.
minnuss said:
Flash again everything to stock, don't root...and don't do an restore backup that google will offer you when you first boot your newly fresh phone.
Install and setup everything again manually, and then test your phone for a day.
I think that you messed up something with root, I did the same, and only fresh new install with manual setup and install of apps step by step fixed the problem.
Click to expand...
Click to collapse
Than you for your answer.
I should have probably mentioned that I chose the option " configure the phone as new", as I always do.
This leaves out the root part. Is it really that taxing? It never occurred to my with my previous phones.
I can try it and do without root for a day, but not much longer.
heavp said:
Than you for your answer.
I should have probably mentioned that I chose the option " configure the phone as new", as I always do.
This leaves out the root part. Is it really that taxing? It never occurred to my with my previous phones.
I can try it and do without root for a day, but not much longer.
Click to expand...
Click to collapse
It's fluid here with root so I doubt that changes anything
minnuss said:
I think that you messed up something with root
Click to expand...
Click to collapse
Just to clarify myself here, I did not meant that root can do something to phone it self, but the user when he is overplaying with the phone, like I did, and some app triggered something and made my phone buggy.
And, I don't use other launchers, I always use the default one that came with the phone itself, because I would always feel that "laggines" with custom launchers.
On Huawei for example, I would try google launcher, but it would lag, so I would get used to default one...
And yeah, here is also super fluid experiance so far with Mi A2.
minnuss said:
Just to clarify myself here, I did not meant that root can do something to phone it self, but the user when he is overplaying with the phone, like I did, and some app triggered something and made my phone buggy.
And, I don't use other launchers, I always use the default one that came with the phone itself, because I would always feel that "laggines" with custom launchers.
On Huawei for example, I would try google launcher, but it would lag, so I would get used to default one...
And yeah, here is also super fluid experiance so far with Mi A2.
Click to expand...
Click to collapse
I just tried flashing again with mi flash tool, I'm not rooted and I'm using the default launcher.
Pulling down the notification shade is still a pain.
I guess that I'll just wait for a working twrp and for custom ROMs.
heavp said:
I just tried flashing again with mi flash tool, I'm not rooted and I'm using the default launcher.
Pulling down the notification shade is still a pain.
I guess that I'll just wait for a working twrp and for custom ROMs.
Click to expand...
Click to collapse
It just follows my finger as fast as I can move them. Something is fishy on your device
Go to TWRP and erase dalvik, and try another source of stock ROM download, maybe something is wrong with that.
And flash all via fastboot like this
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
The stock rom, extract images...
http://en.miui.com/download-353.html
I've been an Android user for a long time and was into the rooting and custom ROM scene in the days of the DROID phones, Nexus, and early Pixel devices.
Once I got my Pixel 3 and then a Samsung S20 after that I didn't really have a reason to root any longer as I didn't want to mess with custom ROMs.
Now I'm using a Pixel 5 and while I still don't really want to root it seems to be the only way to hide the nav bar in conjunction with Fluid Navigation Gestures. This is a big deal for me as I have been using FNG for years now and really don't like Google's default gesture nav. I'm using 3-button nav for now but would love to get FNG back.
Anyways, I'm looking into rooting the Pixel 5 and the process seems much more involved then it used to be, and I see lots of people talking about not getting OTA updates (minor security patches, not even whole Android version updates).
From what I remember back when I was rooting phones ~5 years ago it was much simpler and did not preclude you from getting OTA updates. Especially on Nexus devices, and even early Pixels if I'm remembering correctly, rooting was simple and didn't break when you updated.
Amy I remembering this correctly? Is Google cracking down on rooting much more these days? I would just be so happy if I could get proper FNG back, this phone would be absolutely perfect for me if I could just do that without much fuss.
skytbest said:
I've been an Android user for a long time and was into the rooting and custom ROM scene in the days of the DROID phones, Nexus, and early Pixel devices.
Once I got my Pixel 3 and then a Samsung S20 after that I didn't really have a reason to root any longer as I didn't want to mess with custom ROMs.
Now I'm using a Pixel 5 and while I still don't really want to root it seems to be the only way to hide the nav bar in conjunction with Fluid Navigation Gestures. This is a big deal for me as I have been using FNG for years now and really don't like Google's default gesture nav. I'm using 3-button nav for now but would love to get FNG back.
Anyways, I'm looking into rooting the Pixel 5 and the process seems much more involved then it used to be, and I see lots of people talking about not getting OTA updates (minor security patches, not even whole Android version updates).
From what I remember back when I was rooting phones ~5 years ago it was much simpler and did not preclude you from getting OTA updates. Especially on Nexus devices, and even early Pixels if I'm remembering correctly, rooting was simple and didn't break when you updated.
Amy I remembering this correctly? Is Google cracking down on rooting much more these days? I would just be so happy if I could get proper FNG back, this phone would be absolutely perfect for me if I could just do that without much fuss.
Click to expand...
Click to collapse
I can't speak for the topjohnwu (Magisk "Magic" man) but for us end users, rooting is pretty easy for Pixel phones. Install Magisk manager, put copy of boot.img on phone, patch it through Magisk manager, put patched boot image on pc and flash it in fastboot. All after unlocking bootloader and enabling USB first.
I've always downloaded and installed my own updates so getting ota's is not an issue for me. I use FNG as well.
I had the original Samsung Nexus. First phone I ever rooted. I had so much fun with that phone. Seems like there was a limitless amount of custom roms. I was hooked.
It may seem that way as we do not have TWRP so you're doing different steps. They aren't necessarily harder steps, just different. I've only owned this phone for 1 update cycle but it took perhaps 10-15 minutes to upgrade, re-root and be back up and running as I was before.
Tulsadiver said:
had the original Samsung Nexus. First phone I ever rooted. I had so much fun with that phone. Seems like there was a limitless amount of custom roms. I was hooked.
Click to expand...
Click to collapse
Those wher the days! I just had mine in my hands a few hours ago, when i was rumaging in my old phones box...
Ducter said:
It may seem that way as we do not have TWRP so you're doing different steps. They aren't necessarily harder steps, just different. I've only owned this phone for 1 update cycle but it took perhaps 10-15 minutes to upgrade, re-root and be back up and running as I was before.
Click to expand...
Click to collapse
Thanks for the reply. When you rooted the phone originally did you have to do a factory reset? And when you update and re-root do you have to reinstall the magisk modules or does everything just start working again like it was before the update?
Tulsadiver said:
I can't speak for the topjohnwu (Magisk "Magic" man) but for us end users, rooting is pretty easy for Pixel phones. Install Magisk manager, put copy of boot.img on phone, patch it through Magisk manager, put patched boot image on pc and flash it in fastboot. All after unlocking bootloader and enabling USB first.
I've always downloaded and installed my own updates so getting ota's is not an issue for me. I use FNG as well.
I had the original Samsung Nexus. First phone I ever rooted. I had so much fun with that phone. Seems like there was a limitless amount of custom roms. I was hooked.
Click to expand...
Click to collapse
Thanks. Do you have to wipe the phone as part of the rooting process?
Also, when you do update do you have to re-enable 3-button nav so that when you are unrooted (after update) you can use the phone? Do all the magisk modules and other root-only things just come back on their own once the phone is rooted again?
skytbest said:
Thanks. Do you have to wipe the phone as part of the rooting process?
Also, when you do update do you have to re-enable 3-button nav so that when you are unrooted (after update) you can use the phone? Do all the magisk modules and other root-only things just come back on their own once the phone is rooted again?
Click to expand...
Click to collapse
Unlocking bootloader will wipe your phone. Most of your settings are remembered when applying new firmware as long as you remove the -w from the update-all.bat
It is recommended that you remove all modules before updates so that when you re-root you don't bootloop (in case the mods need updated to new firmware).