Related
Moto E 2015 LTE
I have to open a new thread, after everything went ok considering the camera for many hours, it again stopped working after restore.
What happened? I made a backup with TWRM and rebooted my phone, a message from SuperSu appeared that the binaries have to be updated, but this message disappeared as fast as it appeared. So I could not do anything. A hint was shown at the display to DOWNgrade! the google playstore. I installed a very early version of playstore 3.1 and rebooted. But the camera continued to stop working...is busy etc... I do not want the get rid of root access, all the rest of the apps are working without problems. Do we have to wait for another version of SU? A total unroot gives back the full functionality of the cam. But certainly I do not want to do this. It seems to be a problem with android 5.0.2 hxxps://play.google.com/store/apps/details?id=com.motorola.camera&hl=de or even motorola. But why does it work without SU?
Camera is working again after deleting cache, stopping the programm, wiping the dalvik (I did it but I am not really sure if it is necessary, have a try) and rebooting. So it is definitely not an hardware issue. So we have to wait for an update working with Android 5.0.2 as they have had several problems with their camera app before regarding other smartphones . Thanks Motorola
Greets
RioGrandeBlood said:
Moto E 2015 LTE
I have to open a new thread, after everything went ok considering the camera for many hours, it again stopped working after restore.
What happened? I made a backup with TWRM and rebooted my phone, a message from SuperSu appeared that the binaries have to be updated, but this message disappeared as fast as it appeared. So I could not do anything. A hint was shown at the display to DOWNgrade! the google playstore. I installed a very early version of playstore 3.1 and rebooted. But the camera continued to stop working...is busy etc... I do not want the get rid of root access, all the rest of the apps are working without problems. Do we have to wait for another version of SU? A total unroot gives back the full functionality of the cam. But certainly I do not want to do this. It seems to be a problem with android 5.0.2 hxxps://play.google.com/store/apps/details?id=com.motorola.camera&hl=de or even motorola. But why does it work without SU?
Camera is working again after deleting cache, stopping the programm, wiping the dalvik (I did it but I am not really sure if it is necessary, have a try) and rebooting. So it is definitely not an hardware issue. So we have to wait for an update working with Android 5.0.2 as they have had several problems with their camera app before regarding other smartphones . Thanks Motorola
Greets
Click to expand...
Click to collapse
this is already a known issue when you flash twrp and root. its kinda hit and miss for users.
fix-this! said:
this is already a known issue when you flash twrp and root. its kinda hit and miss for users.
Click to expand...
Click to collapse
I did not know this. Extracted the recovery img from stock rom and the camera is working.
Would you please give me a hint if any cwm working for moto g g2 and x should be working on our phone?
RioGrandeBlood said:
I did not know this. Extracted the recovery img from stock rom and the camera is working.
Would you please give me a hint if any cwm working for moto g g2 and x should be working on our phone?
Click to expand...
Click to collapse
No idea if there is a cm recovery yet. So maybe its twrp that messes up the cam.
There is no clockwork recovery, hopefully a dev can port it.
Is the camera breaking a stock camera thing, or all cameras? Like if the stock doesn't work would downloading the Google camera from the Play Store work?
bobbyphoenix said:
Is the camera breaking a stock camera thing, or all cameras? Like if the stock doesn't work would downloading the Google camera from the Play Store work?
Click to expand...
Click to collapse
Did you try? I have not, because now stock camera works, after update after rebooting. I wonder how long will it work and what happens next...
RioGrandeBlood said:
Did you try? I have not, because now stock camera works, after update after rebooting. I wonder how long will it work and what happens next...
Click to expand...
Click to collapse
Not yet. I haven't rooted yet because of this bug. That's why I asked if anyone has tried a Play Store camera while the stock one doesn't work.
Sent from my MotoE2(4G-LTE)
bobbyphoenix said:
Not yet. I haven't rooted yet because of this bug. That's why I asked if anyone has tried a Play Store camera while the stock one doesn't work.
Sent from my MotoE2(4G-LTE)
Click to expand...
Click to collapse
Thats broke to, any camera will be. To fix it download root explorer, go to system/app/supersu and rename the apk to .bak. Reboot, your not totally unrooted and the camera will work.
A perm fix will be when moto releases our kernel source and we can compile a kernel with selinux set to off or permissive.
Whatever I do, delete SuperSU or not, delete TWRP or not, after any reboot the camera starts working, then after the next reboot it stopps working, after the next reboot it is working again. Even with working and not renamed SuperSU
What the hell is this?
Renaming does not work better or less.
Could you post the output of running this after you try to use your camera and it doesn't work:
Code:
adb shell su -c dmesg | grep denied
This may help identify the cause of problems if SELinux is to blame. Tonight, I will build and post a kernel with SELinux disabled to see if that fixes anything.
Alright, I built a kernel with SELinux disabled. Apart from that, the source code is straight from the Motorola GitHub.
This is for Styx LTE (surnia) only! Flash at your own risk. I am not responsible for bricking your device, causing damage, bodily harm yada yada.
http://filebin.ca/1v4FfHSxMtX3/surnia_boot_noselinux.img
To install it, go into fastboot and run
Code:
fastboot flash boot surnia_boot_noselinux.img
This kernel is probably missing a bunch of stuff, and it breaks Bluetooth and WiFi. The camera should work though. Try it out and see if it changes the behaviour of the camera. Once you're done with it, you can return to the stock kernel by flashing the stock boot.img.
adb shell su -c dmesg | grep denied
Thanks, I will try, but time is the problem right now.
I was a bit too fast, camera seems to work after renaming SU.apk into bat.
squid2 said:
Could you post the output of running this after you try to use your camera and it doesn't work:
Code:
adb shell su -c dmesg | grep denied
This may help identify the cause of problems if SELinux is to blame. Tonight, I will build and post a kernel with SELinux disabled to see if that fixes anything.
Click to expand...
Click to collapse
Not sure you can modify the kernel since we have no source yet.
fix-this! said:
Not sure you can modify the kernel since we have no source yet.
Click to expand...
Click to collapse
We do have the source. It's on Motorola's GitHub. It was posted right when the phone was released. Yesterday, I built a kernel with SELinux disabled and posted it two posts above yours.
EDIT: Kernel source link
After renaming SU into bak I later renamed it into the original apk. version to see what will happen. And in fact nothing happens. . Camera is working for days now after several rebootings. TWRP is working great and has no issue on the camera. Thank you fix-this!
squid2 said:
Alright, I built a kernel with SELinux disabled. Apart from that, the source code is straight from the Motorola GitHub.
This is for Styx LTE (surnia) only! Flash at your own risk. I am not responsible for bricking your device, causing damage, bodily harm yada yada.
http://filebin.ca/1v4FfHSxMtX3/surnia_boot_noselinux.img
To install it, go into fastboot and run
Code:
fastboot flash boot surnia_boot_noselinux.img
This kernel is probably missing a bunch of stuff, and it breaks Bluetooth and WiFi. The camera should work though. Try it out and see if it changes the behaviour of the camera. Once you're done with it, you can return to the stock kernel by flashing the stock boot.img.
Click to expand...
Click to collapse
tried to flash on my lte model us based gsm. just kept booting back into fastboot until i flashed my stock boot.img. you may wanna talk to chainfire to see if it would be better to make it set to permissive instead of fully disabling selinux.
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
squid2 said:
We do have the source. It's on Motorola's GitHub. It was posted right when the phone was released. Yesterday, I built a kernel with SELinux disabled and posted it two posts above yours.
EDIT: Kernel source link
Click to expand...
Click to collapse
i didn't know that.
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
RioGrandeBlood said:
After renaming SU into bak I later renamed it into the original apk. version to see what will happen. And in fact nothing happens. . Camera is working for days now after several rebootings. TWRP is working great and has no issue on the camera. Thank you fix-this!
Click to expand...
Click to collapse
its hit or miss for me. sometimes the cam works sometimes it doesn't.
fix-this! said:
tried to flash on my lte model us based gsm. just kept booting back into fastboot until i flashed my stock boot.img. you may wanna talk to chainfire to see if it would be better to make it set to permissive instead of fully disabling selinux.
Click to expand...
Click to collapse
Thanks for trying it. I'm not surprised that it didn't work. The quick hack of a boot image I posted is missing the device tree, and it will also fail to load all kernel modules due to a version mismatch. I had tested it on the unit I had at hand, and was shocked that it was able to boot and function without a device tree image, but the hardware I used is a bit different than what you have. I've ordered a production device, and it will hopefully arrive this week. Then I will be able to test properly.
I've been working on setting up proper build infrastructure to build working kernels for surnia (complete with compatible driver modules, device tree images etc). I'm hoping to publish an initial release of my kernel for surnia over the next week or two. My initial release would probably be largely the same as the stock kernel, and then I'll start adding improvements from there.
I think you can make SELinux permissive from boot without recompiling the kernel by simply adding androidboot.selinux=permissive to the kernel command line arguments in boot.img. If anyone wants, I can make such an image using the stock kernel. I don't have a suitable device to test with at the moment though.
squid2 said:
Thanks for trying it. I'm not surprised that it didn't work. The quick hack of a boot image I posted is missing the device tree, and it will also fail to load all kernel modules due to a version mismatch. I had tested it on the unit I had at hand, and was shocked that it was able to boot and function without a device tree image, but the hardware I used is a bit different than what you have. I've ordered a production device, and it will hopefully arrive this week. Then I will be able to test properly.
I've been working on setting up proper build infrastructure to build working kernels for surnia (complete with compatible driver modules, device tree images etc). I'm hoping to publish an initial release of my kernel for surnia over the next week or two. My initial release would probably be largely the same as the stock kernel, and then I'll start adding improvements from there.
I think you can make SELinux permissive from boot without recompiling the kernel by simply adding androidboot.selinux=permissive to the kernel command line arguments in boot.img. If anyone wants, I can make such an image using the stock kernel. I don't have a suitable device to test with at the moment though.
Click to expand...
Click to collapse
Yes fix-this, my camera stopped from working again after using a root cleaner (fixed permissions here-is this the problem?) and rebooted the device. But as squid2 wrote/suggested, the problems (permissive) do not seem to be too severe and could be solved in the near future. It seems to be just a matter of time. At this point I strongly recommend the installation of TWRP. I got a functioning camera back and it helps while working on our handy, TWRP does not seem to be the problem so better install it and keep it working. It helped me a lot. Greets
squid2:adb shell su -c dmesg | grep denied
I did it, but got the message grep written wrong/not found
Hi guys,
I need a Nandroid backup of a moto e 2015 3G variant(XT1506).
On restoring my nandroid backup, my device gets stuck on boot screen (bootloader unlocked warning screen).
Thanking you guys in advance...
Hmm... have you been using a recovery from a different model (Moto G or the old Moto E)? The partition maps are different, and you shouldn't be using recoveries for other models. This could cause the issue you are having.
Is your phone able to boot at all? Can you boot into Android? Can you boot into recovery?
squid2 said:
Hmm... have you been using a recovery from a different model (Moto G or the old Moto E)? The partition maps are different, and you shouldn't be using recoveries for other models. This could cause the issue you are having.
Is your phone able to boot at all? Can you boot into Android? Can you boot into recovery?
Click to expand...
Click to collapse
HI
hey i am going to buy a moto e 2015 3g model. The question i wanted to ask is
1. Can i unlock my boot loader without bricking.
2. Is there any method to root the 3g varient without bricking.
3. Is custom recovery available for 3g varient without bricking.
4.If custom recovery is not available then can i install custom rom ( CM12) without recovery.
I searched a lot and it seems all support is for the LTE version. I dont want to brick my device. Please help.
Ravx said:
HI
hey i am going to buy a moto e 2015 3g model. The question i wanted to ask is
1. Can i unlock my boot loader without bricking.
2. Is there any method to root the 3g varient without bricking.
3. Is custom recovery available for 3g varient without bricking.
4.If custom recovery is not available then can i install custom rom ( CM12) without recovery.
I searched a lot and it seems all support is for the LTE version. I dont want to brick my device. Please help.
Click to expand...
Click to collapse
1. Yes
2. Some people have had success using recoveries from other devices to flash SuperSU, but I don't recommend doing this.
3. None are available yet for the 3G model. One will probably appear soon enough.
4. CM12 is not yet available for this device (too new)
squid2 said:
1. Yes
2. Some people have had success using recoveries from other devices to flash SuperSU, but I don't recommend doing this.
3. None are available yet for the 3G model. One will probably appear soon enough.
4. CM12 is not yet available for this device (too new)
Click to expand...
Click to collapse
So i guess i wont be rooting it now. May be someday devs will support this varient.
So is there any thread belonging to 3g varient , or all threads in moto e forum are for LTE
squid2 said:
Hmm... have you been using a recovery from a different model (Moto G or the old Moto E)? The partition maps are different, and you shouldn't be using recoveries for other models. This could cause the issue you are having.
Is your phone able to boot at all? Can you boot into Android? Can you boot into recovery?
Click to expand...
Click to collapse
I googled for the recovery, and I boot into TWRP for 4G version.
I am able to boot the device into CM12 for condor, that is Moto E 1st gen after I decrypted my device.
I was not happy with CM12 condor, as I was not able to make calls and System UI crashed every 6 minutes or so.
Hence, when I actually Wiped my device and flashed my Nandroid backup, I am stuck in bootloader unlocked screen.
My nandroid backup did not include data, could that be the problem? or is it because I decrypted my phone?
Thanks in advance.
I've built a TWRP recovery for the 2015 Moto E 3G. This model is also known as Styx 3G, and has the codename otus.
3G model only! If you have the LTE model, use my LTE recovery instead.
Downloads are available on the downloads tab. In case you encounter any issues, I've also posted the stock recovery for otus on the downloads tab.
To try it out without flashing, run:
Code:
fastboot boot twrp.img
To flash it:
Code:
fastboot flash recovery twrp.img
Try at your own risk. I expect everything to work, but I make no guarantees.
I would like to thank cybojenix for creating the first-gen Moto E recovery. I used his device tree as a reference when creating mine.
Device Tree: https://github.com/sultanqasim/android_device_motorola_otus/tree/twrp
Kernel: https://github.com/sultanqasim/android_kernel_motorola_otus/tree/twrp
XDA:DevDB Information
TWRP for Moto E 3G (2015), Tool/Utility for the Moto E 2015
Contributors
squid2, cybojenix
Source Code: https://github.com/sultanqasim/android_device_motorola_otus
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2015-04-17
Last Updated 2018-08-16
Reserved
My initial test release is up. Try it at your own risk, I don't know what works and what doesn't. All I know is that it can boot and see the on board storage. Thanks to @Ravx and @Hakkinukai for initial testing. If you want to stay safe, don't flash anything with it until I'm able to confirm that it works properly. I'm still waiting on my test unit to arrive.
For the adventurous, try it out and let me know what works and what doesn't. Be careful though, it's untested and could mess up your device. I'm not responsible for any problems it may cause you.
squid2 said:
My initial test release is up. Try it at your own risk, I don't know what works and what doesn't. All I know is that it can boot and see the on board storage. Thanks to @Ravx and @Hakkinukai for initial testing. If you want to stay safe, don't flash anything with it until I'm able to confirm that it works properly. I'm still waiting on my test unit to arrive.
For the adventurous, try it out and let me know what works and what doesn't. Be careful though, it's untested and could mess up your device. I'm not responsible for any problems it may cause you.
Click to expand...
Click to collapse
Further test results:
1.) Was able to succesfully backup my system with the recovery.
2.) wiping data gave error ( error code 255 i think ) but the data was still gone and the device got factory reset.
3.) Succesfully restored the data from the created backup.
will try to flash SuperSu now.:good::good:
Edit: The device is Successfuly rooted.
Here is the Screenshot of Successful Root.:good::good::good::good:
Bro i have created a saperate Guide for rooting. I hope you dont mind.
Glad to hear that it is mostly working. I'll look into the data wiping error when I get my test device.
Thank you very much squid
i try this command 'fastboot boot twrp-otus-2.8.6-test3.img'
and in first attempt , i got TEAMWIN screen on successful boot MOTO E 2nd Generation.
and from install option ,i install SuperSU from my internal memory.
and my device rooted successfully.
you are :angel:
:victory:
I've posted a new version (2.8.6-test4). This new version solves a problem that prevented my recovery from booting from flash storage. It's also smaller. Thanks to @Hakkinukai for testing.
You can safely flash this recovery to your device by doing
Code:
fastboot flash recovery twrp-otus-2.8.6-test4.img
I make no promises about reliability, but I'd expect most things to work. Use this at your own risk, I'm not responsible for bricking your device. I haven't tested this myself.
To avoid confusion, I've removed the old version (2.8.6-test3) from the downloads tab.
Thank you very much, I could finally rooting my moto E,
#Off topic could please make a version updated for the moto E first generation, the current version is 2.7.1.0 and the latest versions have many bugs,
squid2 said:
I've posted a new version (2.8.6-test4). This new version solves a problem that prevented my recovery from booting from flash storage. It's also smaller. Thanks to @Hakkinukai for testing.
You can safely flash this recovery to your device by doing
Code:
fastboot flash recovery twrp-otus-2.8.6-test4.img
I make no promises about reliability, but I'd expect most things to work. Use this at your own risk, I'm not responsible for bricking your device. I haven't tested this myself.
To avoid confusion, I've removed the old version (2.8.6-test3) from the downloads tab.
Click to expand...
Click to collapse
Thanks bro. I will flash and report back :good::good:
Is flashing the new recovery working for you guys. If yes I will update the rooting thread so that the method becomes more easy.
great work man
Ravx said:
Is flashing the new recovery working for you guys. If yes I will update the rooting thread so that the method becomes more easy.
Click to expand...
Click to collapse
The new recovery is working just fine for me, but i cant boot into recovery mode manually, i have to use a third party app either quick boot or apm+.
other than that everything works good.
raghavarora1997 said:
The new recovery is working just fine for me, but i cant boot into recovery mode manually, i have to use a third party app either quick boot or apm+.
other than that everything works good.
Click to expand...
Click to collapse
By booting manually, I presume you mean selecting it from the bootloader menu with the volume keys. What happens when you try that? I've had others report that it works.
squid2 said:
By booting manually, I presume you mean selecting it from the bootloader menu with the volume keys. What happens when you try that? I've had others report that it works.
Click to expand...
Click to collapse
After selecting recovery from the bootloader black screen comes and nothing happens. I've tried it many times with no success.
Sent from my MotoE2 using XDA Free mobile app
raghavarora1997 said:
After selecting recovery from the bootloader black screen comes and nothing happens. I've tried it many times with no success.
Sent from my MotoE2 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm, so it goes black right away and doesn't show the boot logo or unlocked boot loader warning. Strange.
Are you sure that you flashed it correctly? Is anyone else having this issue?
squid2 said:
Hmm, so it goes black right away and doesn't show the boot logo or unlocked boot loader warning. Strange.
Are you sure that you flashed it correctly? Is anyone else having this issue?
Click to expand...
Click to collapse
Yeah I'm sure I've flashed it correctly.
And yes it goes back right away. Still I will flash or again, just to be sure and then report back.
UPDATE: After flashing again I can boot into recovery manually.
Sent from my MotoE2 using XDA Free mobile app
The utterly incompetent Canada Post decided to lose my Moto E 3G. Their customer service was very unhelpful and just told me to contact the sender, and ask them to start a trace with the USPS. Traces take 3 weeks and often get nowhere. This is the fifth package to me that Canada Post has lost in the past two years. On average, I've found that 1 in 5 packages sent to me via Canada Post get lost. That is quite ridiculous, but they are a taxpayer funded government monopoly with no sense of customer service.
In addition to contacting the sender, as a last resort, I've taped a notice inside my mailbox to ask the mailman/woman if they know what they did to my parcel. God knows if I'll ever get it.
Anyway, enough of a rant for now. I'm furious that they lost a package that I spent $200 on (with taxes, shipping, markup etc.)
Due to you, this tut was possible @ http://androidmtk.com/root-motorola-moto-e-3g-2015
Good news! My Moto E was delivered to the wrong address by Canada Post, but the people who received it brought it to me yesterday. I've started looking into porting CM12.1 to otus, though it will probably be a week or so before I have something to show.
I Find some bugs:
1) The USB-OTG don't work (don't mounts)
2) adb sideload don't work (don't finds device)
3) strong button vibration (the default is 80, but 20 is ideal)
General info:
There will be a lot of discussion, do not follow untested tuts in this thread. It could cause you to brick your phone into a Cool paperweight.
AS OF 9/1/2015
XT1528-Surnia_Verizon
Board- MSM8916
Bootloader-NOT UNLOCKABLE!- EVEN IF YOU GO THROUGH MOTO'S WEBSITE (Verizon Locked it, not moto. & verizon cant unlock it) Viewable by booting into recovery & reading the screen.
Android 5.0.2-armv7l-240 DPI
Updated to 5.1
200MHz-1.21GHz quad core-Qualcomm Snapdragon 400/410
Root- No Write/full access-Cant seem to uninstall system apps on Android 5.0?/5.1
Screenshot: Attached at bottom of KINGROOT APK(4.5) via One click root method working on my updated 5.1 lolipop xt1528.
KingRoot does not root your device, just allows for removal of pre installed software via kinguser.After uninstalling, it crashed my Google launcher app & was fixed via rebooting which caused my system to have to re-optimize all apps which took 5 minuets. Root access is denied. Autostart manager works
Unrootable, Locked bootloader, but excellent capability. I love 5.1 better. I wouldnt recommend this device for anonymous browsing (I like to use Tor as a VPN), torrenting, or sharing. But I love the battery (lasts all day without heavy gaming use), phone calls & txts, Browsing the web is good too. I love being able to take out my phone and say "Ok Google" to vocally search or open things (like cortana) and my phone talk back. As well as the easy-to Use feeling comes if you've expierienced 5.0 before, a little confusing if you've been stuck on <4.0.I feel comfortable with it & it fits in my pocket pretty well. I don't know how much radiation it throws off... I say 7/10 overall. No xposed, if your lucky to rebuild the APK & patch it you can do it.. 4g is awesome! & I'm happy I didn't go with a free phone. Although, i'll be getting one soon to play with.
Thank you, Thanks for reading, & Have a wonderful day! (ALL Useful info & credits to who said it will be added via a reserved spot below.)
LATEST Answers :SU-ME didnt work for me on 5.0, and even though KingRoot said i had root access, It wouldnt give it to anything or allow write access.... Also, I attempted to root 5.1 off the v4.1 apk. It said root strategy available-Gave me (nothing past words)root access-But caused a bunch of apps to continuously crash. (I'll try it again once i go through my dev settings, i also factory wiped it earlier). It said i could remove system apps, It couldnt though. I used the auto-start manager too (we'll see if that stuck). (pics below) Also, Anyone who provides any testing will get thanked & a name below.
_______________________________________
| RESERVED |
| Thank you, kmani.k78 |
| Whoareyou |
| DBlake1 |
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
The hardest part is unlocking the bootloader. Without that, it's impossible to root.
I wish I had seen this thread before I picked up this phone today. :/
As I did pick one up as something to play with and not necessarily just for custom roms, I'm not immediately returning it, but it's a strong possibility.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
When I try installing twrp via fastboot I receive a preflash error. I have yet been able to boot into recovery., I just get a red triangle and "no command" . What am I doing incorrect?
I don't understand the recovery mode for this phone, I'm used to 4.0.4 lol. I'm not sure either. I thought I broke my system when I tried to adb flash twrp & found out you can't shut your phone off when its in recovery mode. (Also, you can't flash without unlocking the bootloader) DUH right?
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
You can't flash without an unlocked bootloader. The XT1528 isn't supported by Motorola for unlocking because its a Verizon phone. Verizon doesn't like giving out codes, and wouldn't even if you asked. I think unless someone can Dev the crap outta it, We're screwed XT1528 wise. But, I don't know much about anything lol. I'm still learning.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
this is not possible on verizon version xt1528. bootloader is unlockable. will need an android 5 vulnerability to gain root which is the best the verizon version will ever get.
Most likely way to root this phone would be to use an app that has a Lollipop exploit, but they're getting harder according to this article:
http://www.androidpolice.com/2014/1...ew-modified-kernels-may-become-a-requirement/
Okay so now I have gone and picked up the AT&T XT 1527 version. I now have a XT 1528 I can test with. Question, should I go ahead and root the XT 1527? I am thinking about wiping everything off Verizon phone and installing Fedora on it, but if there are other suggesting, I now have a test sled that can be used. I am open to suggestions with the verizon phone, let me know what you all think.
XT1528 can be rooted by "Kingroot" method - a closed source app!
kmani.k78 said:
XT1528 can be rooted by "Kingroot" method - a closed source app!
Click to expand...
Click to collapse
Have you tried it yourself?
Sent from my XT1528
Ace42 said:
Have you tried it yourself?
Sent from my XT1528
Click to expand...
Click to collapse
Yes I have already rooted my xt1528.
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Can somebody please confirm?
Thanks!
Just run on XT 1528 android 5.1..... not rooted according to root check
Harish_Kumar said:
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
Click to expand...
Click to collapse
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
How did you root your XT1528? Link?
Whyzor said:
How did you root your XT1528? Link?
Click to expand...
Click to collapse
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
kmani.k78 said:
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
Click to expand...
Click to collapse
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
Thanks for reporting root worked on your moto e, this is fairly new, Im waiting to see if others can repeat it, and whether it really does work. Have you tried some other apps that require root to see if they actually work with root?
For your specific /system/build.prop issue, some roms write that file from another location, /etc/build.prop or some other similar paths, so maybe need to find that file. Also you have to remount /system as read-write, assuming this worked otherwise there would be an error right away.
Usually I edit /system/build.prop files manually with terminal emulator app, then type these commands:
su (proper root needed)
mount -o rw,remount /system/build.prop
vi /system/build.prop ( may need to install busybox app)
Stock Pixel/PixelXL Kernel + SafetyNet Patch
Current version: android-msm-marlin-3.18-nougat-mr1
Suitable for build: NMF26U
Security patch level: January 5, 2017
I compiled the stock kernel for the Pixel/PixelXL (they both use the same kernel) and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
I posted this over in the Pixel thread (as I have the regular Pixel), but thought I'd share it over here as well.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the stock builds, except with the addition of the SafetyNet patch.
Installation:
- Download attached .zip and unzip into a folder
- Reboot device into bootloader (power down device, then Power + Volume down)
- Connect device to computer
- Verify connection by typing 'fastboot devices'. Your device should show up (check serial number)
- Enter command: fastboot flash kernel <kernel_image>
- Once flashing is complete, enter command: fastboot reboot
- Disconnect device and wait for reboot sequence to complete.
- You now have a stock Pixel with an unlocked bootloader that can use Android Pay
**WARNING**
If flashing this kernel for whatever reason ruins your device, please don't hold me accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future (am running a Verizon Pixel). I will try to maintain this kernel with each new release until I lose interest
Downloads:
NMF26U
All versions
Not sure why no ones replied here yet! - it's no use to me but thank you very much
Just downloaded and tried to install using fastboot but my device is stuck in a bootloop My bootloader is unlocked and I had previously rooted using twrp but I was using the stock recovery. I was on version NMF26O. I'm going to try re-rooting again and see if that fixes it.
I don't know how this will interact with rooted devices. I'm personally not rooted and I don't have any issues with this kernel. Try being fully stock first before flashing this.
Sakete said:
I don't know how this will interact with rooted devices. I'm personally not rooted and I don't have any issues with this kernel. Try being fully stock first before flashing this.
Click to expand...
Click to collapse
I might try out a few things later and try different versions of root and post if anything works Thanks mate
THANK YOU! I've been looking for a completely stock kernel that would let me use Android Pay with an unlocked bootloader! Any plans to do this for other Nexus phones, like the 5X?
iissmart said:
THANK YOU! I've been looking for a completely stock kernel that would let me use Android Pay with an unlocked bootloader! Any plans to do this for other Nexus phones, like the 5X?
Click to expand...
Click to collapse
I'll only do it for the Pixel as that's the only phone I have. It's not super difficult to do this yourself though, if you're somewhat technical it's pretty straightforward to do.
I have TWRP updated, newest build F260 and followed the steps but still unable to use Android Pay. Says it cant verify the device or software.
EDIT:Im dumb didn't read that it wasn't compatible with root.. just unlocked bootloader.
ghostENVY said:
I have TWRP updated, newest build F260 and followed the steps but still unable to use Android Pay. Says it cant verify the device or software.
EDIT:Im dumb didn't read that it wasn't compatible with root.. just unlocked bootloader.
Click to expand...
Click to collapse
Yeah, if you're rooted, Android Pay will not work. There is a workaround however. You can add cards to Android Pay before you're rooted. If you root after that, Android Pay should work with the cards you've added. You just won't be able to add new cards.
Thanks for the kernel, just want to ask one question:
I have unlocked bootloader + systemless root, when I power up my phone, there is a yellow warning on the boot screen, if I use this patched kernel, will the yellow waning be gone as well ?
churchmice said:
Thanks for the kernel, just want to ask one question:
I have unlocked bootloader + systemless root, when I power up my phone, there is a yellow warning on the boot screen, if I use this patched kernel, will the yellow waning be gone as well ?
Click to expand...
Click to collapse
You mean the orange warning? That's because unlocked bootloader. Only with locked bootloader the warning disappears.
Tylog said:
You mean the orange warning? That's because unlocked bootloader. Only with locked bootloader the warning disappears.
Click to expand...
Click to collapse
I see, thanks for your explanation. AP is actually not available in my country ( China ), what a pity.
Sakete said:
Yeah, if you're rooted, Android Pay will not work. There is a workaround however. You can add cards to Android Pay before you're rooted. If you root after that, Android Pay should work with the cards you've added. You just won't be able to add new cards.
Click to expand...
Click to collapse
Holy **** thanks for the advice I went ahead and unistalled SuperSU and I added my cards! Thanks!
EDIT: I went to my local McDonalds and tried to pay it said "it couldn't authenticate the device" after adding my cards. This is with root just fyi maybe systemless root will have success.
anybody managed to get AP working with root?
nbhadusia said:
anybody managed to get AP working with root?
Click to expand...
Click to collapse
Not going to happen! Maybe when/if Xposed comes out but until then I don't imagine so
Sent from my Google Pixel XL using XDA Labs
DaveHTC200 said:
Not going to happen! Maybe when/if Xposed comes out but until then I don't imagine so
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I believe a clue of posts up in this thread, someone posted that if you add the cards before you root, Android pay will work for those cards.
Sent from my Pixel using XDA-Developers mobile app
Protibus said:
I believe a clue of posts up in this thread, someone posted that if you add the cards before you root, Android pay will work for those cards.
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Correct, try adding cards before rooting. Once cards are added, root your phone and Android Pay should still work for making payments, you just can't add new cards to it (you'll have to unroot first for that).
ghostENVY said:
EDIT: I went to my local McDonalds and tried to pay it said "it couldn't authenticate the device" after adding my cards. This is with root just fyi maybe systemless root will have success.
Click to expand...
Click to collapse
Oh weird, maybe it doesn't work then? Or it could be another issue. I got this idea from someone else who said it works for him. I myself am not rooted so can't verify otherwise.
Hello, will this still get OTA's and install them / or be able to sideload them???