Database Develop

Rooting 4.2.2 AFTER WP-=OFF what ami missing!

I hope its a simple mistake on my end of being blind, but i have not been able to locate ( if possible ) a way to root 4.2.2 with already running wpnomoto. I was hoping i could do that and get back on SS and run a ROM. Can someone point me in the right direction?
I was on 4.4 and went back to 4.2.2.....or am i out of luck and have to just settle for rooted stock 4.4?

With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.

matt99017d said:
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
Click to expand...
Click to collapse
i rooted mine then tried to put 4.4 update, and now it keeps rebooting.. won't stop. ideas?

xpsychox said:
i rooted mine then tried to put 4.4 update, and now it keeps rebooting.. won't stop. ideas?
Click to expand...
Click to collapse
Fastboot erase cache
Sent on my Moto X

flashallthetime said:
Fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
so after I do the root and click install 4.4, shoudl I go to fastboot and clear cache?

xpsychox said:
so after I do the root and click install 4.4, shoudl I go to fastboot and clear cache?
Click to expand...
Click to collapse
You can not flash the 4.4 ota with any form of custom recovery or root , it will bootloop as you found out. So to stop the bootloops you need to delete the ota in the cache folder. What method did you use to root?
Sent on my Moto X

flashallthetime said:
You can not flash the 4.4 ota with any form of custom recovery or root , it will bootloop as you found out. So to stop the bootloops you need to delete the ota in the cache folder. What method did you use to root?
Sent on my Moto X
Click to expand...
Click to collapse
rock my moto.. how do i delete the cache? and i didn't flash any 4.4.. i took the OTA like i was told. per the instructions.

xpsychox said:
rock my moto.. how do i delete the cache?
Click to expand...
Click to collapse
Fastboot erase cache, read the slapmymoto thread, I believe you need to be on 4.2 to root 4.4 kitkat
Sent on my Moto X

flashallthetime said:
Fastboot erase cache, read the slapmymoto thread, I believe you need to be on 4.2 to root 4.4 kitkat
Sent on my Moto X
Click to expand...
Click to collapse
yes, i was on 4.4 and put 4.2.2 back on and gained root access and then went to install 4.4 OTA like the rockmymoto instructions say, and then i get stuck in reboot..

xpsychox said:
yes, i was on 4.4 and put 4.2.2 back on and gained root access and then went to install 4.4 OTA like the rockmymoto instructions say, and then i get stuck in reboot..
Click to expand...
Click to collapse
Read slapmymoto, it says you need to install jar files and then you can take the ota
Try this thread http://forum.xda-developers.com/showthread.php?t=2573177
Sent on my Moto X

flashallthetime said:
Read slapmymoto, it says you need to install jar files and then you can take the ota
Try this thread http://forum.xda-developers.com/showthread.php?t=2573177
Sent on my Moto X
Click to expand...
Click to collapse
i did, i adb pushed rockmymoto, with su, and slapmymoto jar files... but then it says to take OTA 4.4 and that's when it reboots indefinitely...

xpsychox said:
i did, i adb pushed rockmymoto, with su, and slapmymoto jar files... but then it says to take OTA 4.4 and that's when it reboots indefinitely...
Click to expand...
Click to collapse
Wish I could help further but lucky me , I have a unlockable boot loader, ask in the thread that I linked in my previous post
Sent on my Moto X

flashallthetime said:
Wish I could help further but lucky me , I have a unlockable boot loader, ask in the thread that I linked in my previous post
Sent on my Moto X
Click to expand...
Click to collapse
i did, they're all offline.. *sad face* ...lol

matt99017d said:
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
Click to expand...
Click to collapse
Matt, I guess that was what you did:
1. You had a root 4.4.
2. You run MotoWpNoMo to turn off WP permenently (yes, it is permenent).
3. You flashed the unit back to 4.2.2 for a reason (but you should lost the root) .
4. With 4.2.2 and WP off, you wished you can run RockMyMoto to gain the root again (in 4.2.2).
5. But you found that RockMyMoto stopped at the Step 1 since the WP is off or "0". No more Step 2 and 3. So basically, you wasn't able to re-gain the root.
6. So you decided to reflash the unit back to 4.4.
7. Then you installed again the Safestrape.
8. And you found that SS was still working.
But, after you lost your root, how did you make the SS to work? Very interesting!

danhe said:
Matt, I guess that was what you did:
1. You had a root 4.4.
2. You run MotoWpNoMo to turn off WP permenently (yes, it is permenent).
3. You flashed the unit back to 4.2.2 for a reason (but you should lost the root) .
4. With 4.2.2 and WP off, you wished you can run RockMyMoto to gain the root again (in 4.2.2).
5. But you found that RockMyMoto stopped at the Step 1 since the WP is off or "0". No more Step 2 and 3. So basically, you wasn't able to re-gain the root.
6. So you decided to reflash the unit back to 4.4.
7. Then you installed again the Safestrape.
8. And you found that SS was still working.
But, after you lost your root, how did you make the SS to work? Very interesting!
Click to expand...
Click to collapse
Update. SS is sketchy. I tried to use it and its rough around the edges. I think I flashed my phone via RSD today around 6 times..... I ended up back on rooted 4.4
I though I read somewhere that someone had altered the program so it'll root 4.2.2.......
FYI I was able to obtain root on just 4.2.2 using slapmymoto and NOT taking the OTA. I did every step and I was able to install super su and get root access.
That means I have tried SS ON 4.2.2 AND 4.4 I got the same result on both stock Roms. The only thing I tried to flash was ECLIPSE ROM. Maybe that ROM was what was being finiky and NOT SS......MAKE SENSE?
Sent from my XT1058 using XDA Premium 4 mobile app

matt99017d said:
Update. SS is sketchy. I tried to use it and its rough around the edges. I think I flashed my phone via RSD today around 6 times..... I ended up back on rooted 4.4
I though I read somewhere that someone had altered the program so it'll root 4.2.2.......
FYI I was able to obtain root on just 4.2.2 using slapmymoto and NOT taking the OTA. I did every step and I was able to install super su and get root access.
That means I have tried SS ON 4.2.2 AND 4.4 I got the same result on both stock Roms. The only thing I tried to flash was ECLIPSE ROM. Maybe that ROM was what was being finiky and NOT SS......MAKE SENSE?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Matt, thanks for your quick response. I found that I wasn't able to gain the root for a WP-Off unit with 4.2.2 by the "old" SlapMyMoto. jcase released a new version that works perfectly for a WP-Off unit. Thanks, jcase!

[Q] (AT&T) Best path to 4.4.2 from 4.4?

My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.

Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)

...
Sent from my XT1058 using XDA Premium 4 mobile app

kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .

Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.

NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.

I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app

Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse

NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)

Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app

Is this for real?

I was just Google searching hoping for some good news... And came across this posted yesterday...
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
... Any truth to that? And is it for any carrier, i.e att?
Sent from my XT1058 using Tapatalk

Links to a thread on here.

Yea I saw that, but they are not the same...
Sent from my XT1058 using Tapatalk

They want you to dl this http://www.cydiaimpactor.com/
Anyone know what it is?

Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

kj2112 said:
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?

jbaumert said:
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
Click to expand...
Click to collapse
There's other threads where this stuff gets talked about, but im pretty sure for things like that it would probably work. But any actual changes to anything would get reversed.
I've always been unlocked....so I don't have firsthand experience though.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.

KidJoe said:
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
Click to expand...
Click to collapse
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?

Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
Please see my response to you in the 4.2.2 to 4.4.2 thread.

kj2112 said:
Please see my response to you in the 4.2.2 to 4.4.2 thread.
Click to expand...
Click to collapse
Thanks, didn't realize until afterward it was the same voice in both threads.

Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.

Jumnhy said:
Thanks, didn't realize until afterward it was the same voice in both threads.
Click to expand...
Click to collapse
Where you found another same threads ?

DANIEL AMBRUSO said:
Where you found another same threads ?
Click to expand...
Click to collapse
It was just kj2112 explaining a similar issue to me. Check it out, but essentially my understanding is that there's no root for 4.4.2 if the phone never had root previously (ie, if you naively took the OTA like me without thnking about implications for root.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
KidJoe said:
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Click to expand...
Click to collapse
Solid, thanks for the concise summary. I'd read jcase's posts a while back about a potential exploit--something about using it in a teaching session at BlackHat? He even says though, that the exploit he has will probably never be useful for the average user insofar as it would be too hard to implement and n00bz like myself would end up bricking our phones. So I'm not holding my breath on that one. Ugh. Sad I missed the window for the Chinese connection. Should have jumped on it.

The Tallest said:
Links to a thread on here.
Click to expand...
Click to collapse
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.

glarepate said:
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
Click to expand...
Click to collapse
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).

KidJoe said:
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
Click to expand...
Click to collapse
Yes, if you have already gone to 4.4.2 you are out of luck.
I'm using the T-Mobile SafeStrap Recovery with my RW Moto X. This was done by a Franken-ROM process that uses the 4.4.2 ROM without using the 4.4.2 bootloader and using the SS recovery to flash a zip file with some components of the 4.4.2 ROM and then flashing SuperSU. Whether or not it should be working, it is. Nothing I can, or want to, do about that.
But I am sure you are right that this resultant ROM would not work on phones from other carriers. Versions for other carriers are being developed though. It may simply be a matter of time and interest by motivated individuals until this is available for just about everyone.

root, lollipop, xposed questions

first, sorry if this has been asked b4, xda/google saeearch didn't find anything.
I need xposed, and I also need root. ( both, root for other things besides xposed.)
just got my moto g2, 4.4.4., and I wanted to know, should I root now, or wait till the 5.0 update and then root? or should I root now and install xposed and not update to 5.0 when it comes out? I read online that there probably will not be xposed fully working on lollipop.
advice anyone?

Root it now, you can aways install the update on your phone, rooted or not.

Hakkinan said:
Root it now, you can aways install the update on your phone, rooted or not.
Click to expand...
Click to collapse
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?

Kobro said:
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Click to expand...
Click to collapse
You can be rooted and still be fully stock.

Kobro said:
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Click to expand...
Click to collapse
Only if you want to receive it by OTA, besides that, it doesn't matter if you are fully stock or not.

There are some known issues relocking bootloader and returning to stock at all. In most of all cases it works without problems but not in all. If you can´t get back to stock there still will be future options to get lollipop,by sideloading as a zip though recovery for example,ota is not the only way.
I am still on stock 4.4.4 and will wait for the ota,then relock bootloader and root.The Moto G is the first phone I didn´t root at once because it works really good and has farly not as much crapware as others, so I´m able to wait. But I don´t need xposed desperatly, I badly need Adway,Titanium and some others more.
It´s still not clear if xposed will work under lollipop.
So it´s your choice, it´s up to you. You can stay on Kitkat,root and install xposed. And you can update to lollipop later,when/if xposed is running.
Or you can stay stock,wait for ota and root later wich is my way.

Coming from 2 nexus devices, i can't imagine to have a phone without unlocked bootloader, root, custom rom and kernel, that's the point of android for me, customization

Thanks all for your responses! Much appreciated! Now all i have to do is find some way of rooting the thing, vroot failed- first time ever for me

To root Moto G 4.4.4 you have to unlock the bootloader,install custom recovery and flash superSU.zip.
Just follow this guide: http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245
But use the CWM-recovery from here: http://forum.xda-developers.com/moto-g-2014/development/recovery-cwm-philz-touch-6-moto-g-2014-t2896586
or TWRP from here: http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165

xposed not working
Kobro said:
first, sorry if this has been asked b4, xda/google saeearch didn't find anything.
I need xposed, and I also need root. ( both, root for other things besides xposed.)
just got my moto g2, 4.4.4., and I wanted to know, should I root now, or wait till the 5.0 update and then root? or should I root now and install xposed and not update to 5.0 when it comes out? I read online that there probably will not be xposed fully working on lollipop.
advice anyone?
Click to expand...
Click to collapse
plz send a link where i can download xposed for moto g 2014 tx

najm555 said:
plz send a link where i can download xposed for moto g 2014 tx
Click to expand...
Click to collapse
One post above yours.......
http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1

Phone Stuck In Recovery

Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.

Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.

ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.

Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse

ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.

Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.

Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.

ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.

Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...