Related
A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
It looks like I need to reflash the stock recovery image. I believe I have that (as long as the stock recovery is the same for all moto x phones (verizon, sprint, tmo, att, etc).
The problem I am having now is that I don't know how to flash the stock recovery image. All the instructions that I find require the phone to be in fastboot mode, but I have a locked boot loader....so. ..wud am I supposed to do??
dzlvs8 said:
A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
Click to expand...
Click to collapse
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Click to expand...
Click to collapse
Well your phone is technically rooted when you boot normally, but you don't have write capabilities to /system which is why nothing is sticking. You need to boot the phone into recovery mode to make those changes, and then reboot normally to use them. To boot into the recovery mode with write protection off you need to power your phone down, and power it back up while holding volume down. That gets you into the bootloader and from there you choose recovery and then your phone will reboot with write protection off. It's kind of annoying to have to do it this way but blame Motorola for locking the phone down as well as they did.
To flash the stock recovery back, you need to put the recovery file in your adb folder and then the command is "fastboot flash recovery recovery.img" without the quotes, but if you are unfamiliar with adb I don't recommend doing it. You can just flash the whole stock image with RSDLite and start from square one. I've not personally used RSDLite but here is a video tutorial for you- http://forum.xda-developers.com/showthread.php?t=2446515
dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
Click to expand...
Click to collapse
also just a quick note:
"adb reboot recovery" will boot you into recovery/writeable system
"adb reboot bootloader" will boot you into fastboot for using rsdlite which is all described in the instructions given by metalhead
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
fellhound said:
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
Click to expand...
Click to collapse
Fastboot erase cache
shane1 said:
Fastboot erase cache
Click to expand...
Click to collapse
i tried to install stock but i can't with "adb reboot fastloader" beacuse it restarts every 10-20 seconds"
and according to http://forum.xda-developers.com/showthread.php?t=2444957
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
there is not a single drop of help with fastloader
edit: i managed to enable usb depuration by clicking several times on status/kernel version
i can run the command now, moto x responds and just Fast reboot, does not enter into fastloader
reached a dead end, now im desperated
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
flashallthetime said:
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
Click to expand...
Click to collapse
wow, finally, i was dying, now it does not reset itself.
How can i know if i have custom recovery? i though it was the normal one, wasn't aware pwnmymoto install custom recovery..
should i install stock rom anyways?
now i am downloading OTA again, now that i don't have root and pwnmymoto installed maybe it will work
will report results in 5 minutes
Thanks for the help guise
EDIT: lel no, after redownloading OTA update, it's still halfbricking with reboots.
I have recovered it again cleaning cache, but i wish to get OTA
Any ideas?
P.D all this trouble just to put 2 files into /system/ to enable Playstation mobile geez ;_;
fellhound said:
bump
Click to expand...
Click to collapse
I specifically know very little about pwnmymoto root method, my boot loader is unlocked, so I rooted the old fashion way. I know pwnmymoto hijacks the stick recovery. You may want to rsdlite back to stock, I believe there's a fxz with the latest update and root with jcases new method. Unless someone with more experience with pwnmymoto replies
Sent on my Moto X
You need to either flash the stock recovery and system through fastboot, or just RSD the whole thing (which deletes all your data). That's the only way you'll get it to accept the OTA update. Without the stock recovery, it will keep boot looping when you try to install the OTA.
Yes. Restore to stock. Threads galore. Once you boot you'll get an OTA prompt that'll work no problem.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/moto-x/general/moto-x-unbrick-ota-update-loader-v30-t3153725
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
grimzen said:
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. This is completely normal, you should have just rebooted the phone and been done I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. Again totally normal, thats the bootloader use the vol to move down and choose recovery and hit power this will boot you to TWRP I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Why ? Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. You should not have Sync installed only the drivers I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
Click to expand...
Click to collapse
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
grimzen said:
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
Click to expand...
Click to collapse
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
flash in recovery
use adb push UPDATE-SuperSU-v1.86.zip /data/media/0
to get the file on the phone
Reboot to bootloader / fastboot USB
and from command line on pc
fastboot erase cache
fastboot reboot
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
bihslk said:
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
Click to expand...
Click to collapse
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
grimzen said:
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
Click to expand...
Click to collapse
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
bihslk said:
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
Click to expand...
Click to collapse
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
grimzen said:
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
Click to expand...
Click to collapse
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
bihslk said:
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
Click to expand...
Click to collapse
I've tried a few different cords and all 3 ports I have still nothing but the HTC manager thing. It will recognize it but only for a split second while booting up but it says HTC BUTTERFLY as the drive and i'm not sure if that's a problem or not but it won't recognize it at all through fastboot.
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
bihslk said:
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
Click to expand...
Click to collapse
Ok will try that now. thanks so much for the help.
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
jpaulpra said:
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm not familiar with the red triangle screen is there a way to boot into it?
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
grimzen said:
I'm not familiar with the red triangle screen is there a way to boot into it?
Click to expand...
Click to collapse
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I think @jpaulpra was telling him to reflash stock recovery
then boot to it and do clear cache.. then reflash twrp
When I got into bootloader, I lost the Twrp recovery. So when I selected recovery I got the screen with a "triangle and exclamation mark". If you leave it will reboot the system after couple of minutes. But if the audio up key is pressed, it will show a system recovery screen, where cache can be wiped
Sent from my LT26i using Tapatalk
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Basically all I'm trying to do now it's find a way to get my computer to recognize my phone as a drive. When I go into viper settings and go to advance menu (with the short time I have before boot loop) there is an option to mount drive. When I select the option to do so it hands on splash screen and I have to hold power button to recycle back on. Once back in it's no longer selected. I've never seen a boot loop go pay the flash screen. Is this normal?
Pretty SOL with my son's Nabi2
I'm having a issue with my sons Nabi2 pretty similar. I messed up bigtime guys I rooted it and started messing aroung with the system files. Then didn't get a boot afterwards, wiped everything from twrps system, data, the whole shabang! Even lost my root! and access to on board flash cause I've been trying to recover using twrp with absolutley no luck. I still have the original stock unrooted backup saved to my pc from when I first installed twrp. Can someone please help me? I'm really out here trying to reach out for some help. didn't even know where to post this. Thank you guys. Note to moderators: If this is the wrong place to post this then please point me to the right direction and I apologize.
Are you not supposed to be able to encrypt the device when it is rooted? I tried but it just reboots, never doing anything.
You can encrypt a rooted phone, but I think you need the stock recovery for it to work (or it did with my Nexus phones, I haven't tried it on my Moto X 2014 yet). You could try flashing the stock recovery, encrypting then flashing TWRP/CWM back again.
Azarin said:
You can encrypt a rooted phone, but I think you need the stock recovery for it to work (or it did with my Nexus phones, I haven't tried it on my Moto X 2014 yet). You could try flashing the stock recovery, encrypting then flashing TWRP/CWM back again.
Click to expand...
Click to collapse
I'm on stock recovery
km8j said:
I'm on stock recovery
Click to expand...
Click to collapse
Sometimes Android can get confused and not encrypt your device - lots about it on googles issue tracker, but ensure your phone is fully charged, and plugged in at the time. Sometimes it takes people quite a few times, along with connecting/disconnecting the charger.
As a P.S. My moto x encrypted without issues, but it isn't rooted.
Azarin said:
Sometimes Android can get confused and not encrypt your device - lots about it on googles issue tracker, but ensure your phone is fully charged, and plugged in at the time. Sometimes it takes people quite a few times, along with connecting/disconnecting the charger.
As a P.S. My moto x encrypted without issues, but it isn't rooted.
Click to expand...
Click to collapse
I had a similar experience with my old phone - had to attempt encrypt multiple times, then it finally worked. Haven't encrypted this one yet, but I may have no choice for work.
What I did for my original Moto X was:
1) Unlock bootloader
2) Flash TWRP
3) Root the phone
4) Restore the phone to factory default but leaving the /data and /sdcard partitions in place
5) Encrypt the phone (you have no root at this point)
6) Flash TWRP
7) mount /sdcard and /data as tmpfs filesystems
8) Push the root.zip to one of the tmpfs using adb
9) TWRP can read the tmpfs /sdcard so I used root.
Step 9 fails to write files to the encrypted partition as /data is a tmpfs and the real /data is encrypted, but the files required are still there from the original rooting in Step 3. Now you have a rooted and encrypted phone. I forget the commands to do the tmpfs stuff and adb push, and I don't have an android phone at this time, but Google will help with those I'm sure.
This is a convoluted and annoying process, but it was the only way I could get root and encryption. I hope this helps.
I tried everything and still am not able to encrypt the phone with unlocked boot loader and root. I disabled supersu, rebooted into safe mode and turned on airplane mode.
edwardgtxy said:
I tried everything and still am not able to encrypt the phone with unlocked boot loader and root. I disabled supersu, rebooted into safe mode and turned on airplane mode.
Click to expand...
Click to collapse
Has anyone got some resolution on this? Rooted on the latest Lollipop build here. I've tried safe mode, fully charged, on the charger and every time it gets to the green android screen and then goes black on me.
I just did it yesterday. It didn't seem to be doing anything, but I left it alone and then suddenly it woke up to the encryption PIN entry screen. I'd say leave it alone longer than you think you should, and see what happens. I have stock recovery, BTW.
cbasse said:
I just did it yesterday. It didn't seem to be doing anything, but I left it alone and then suddenly it woke up to the encryption PIN entry screen. I'd say leave it alone longer than you think you should, and see what happens. I have stock recovery, BTW.
Click to expand...
Click to collapse
Any idea how long you left it alone (couple of minutes, 15-30 minutes, 1+ hours)? My device came with Lollipop; I unlocked the bootloader for my device using Motorola's instructions, then installed root according to this thread: http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154. I didn't install any custom recovery. I tried encrypting the phone multiple times, but each time it seems to get stuck at the black screen after shortly showing the android logo.
Edit: I finally got encryption to work; it looks like the device can't be encrypted with the rooting method that I used. In order to encrypt my phone, I flashed the stock ROM, did a factory reset, then encrypted it and installed root after that.
Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?
THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app
So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.
I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app
Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk
I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!
I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app
As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app