Stock AT&T 4.4, not rooted. Still thinking about root.
I thought I've frozen update, Motorola OTA, and FOTA. But apparently I forgot.
Now I kept getting "New System Software Avaiable" notification.
Anyway to get rid of this notificaiton without applying the update?
I've tried to connect my device via USB to ADB but the computer does not seem to recognize it any more. Not even the camera / MTP connection works.
Thanks
How did you freeze those system apps without being rooted?
The update is downloaded to your cache. Go there and delete the update.
Oops just seen your not rooted so you can't access your cache I believe.
In Apps, you can disable an app. I just checked, updater and FOTA are disabled. But Motorola OTA does not allow disable right now
shane1 said:
The update is downloaded to your cache. Go there and delete the update.
Oops just seen your not rooted so you can't access your cache I believe.
Click to expand...
Click to collapse
Even with adb?
redhonker said:
Even with adb?
Click to expand...
Click to collapse
fastboot wipe cache
i think is the command to wipe it.
If I wipe the cache, do I lose anything? (by the name of cache, I should not, but want to be sure)
Also, can anyone confirm if an unrooted device can have the MotorolaOTA disabled to avoid downloading the system updates?
Thanks
redhonker said:
If I wipe the cache, do I lose anything? (by the name of cache, I should not, but want to be sure)
Also, can anyone confirm if an unrooted device can have the MotorolaOTA disabled to avoid downloading the system updates?
Thanks
Click to expand...
Click to collapse
You can wipe the cache in the recovery menu if you have stock recovery. Follow these steps posted on Motorola's website. but on step 7 don't factory reset, just reset the cache instead.
https://motorola-global-portal.cust..._detail/a_id/94936/p/30,6720,8696/action/auth
EDIT: You won't lost anything
EDIT AGAIN: You need root to disable Motorola OTA since it's a system app.
The other way to clear cache... IF you have a proper setup of ADB and the Android Platform Tools.. (and can run fastboot from a command prompt)...
With the phone powered off and unplugged from the PC...
1. press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
2. The device will display different BOOT OPTIONS. Just let it sit there.
3. Plug usb cable to PC
4. Open a command prompt and type...
fastboot erase cache
fastboot reboot
5. The phone should erase the cache, then reboot normally.
6. You may unplug the phone from the PC once the phone has started rebooting.
7. The first reboot after erasing the cache will take a little longer, and you may see messages like "updating applications" or such.
Your guys are right. After clearing cache, there is no way to disable Motorola OTA, even though updater and FOTA can be disabled.
If I update, is there a way to downgrade later?
Thanks
redhonker said:
If I update, is there a way to downgrade later?
Thanks
Click to expand...
Click to collapse
No. Not exactly. Due to changes in the bootloader included with 4.4.2, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2.
It certainly caused enough issues that those with locked bootloaders were told to NOT try and downgrade from 4.4.2 in order to attempt to obtain root via SlapMyMoto/MotoWpNoMo processes.
There was a thread fully discussing bricking the X when downgrading from 4.4.2 to older firmwares here on XDA but for some reason that has since disappeared. There is still this thread -> http://forums.androidcentral.com/mo...ta-if-you-have-rooted-modded-your-system.html which discusses it.
I've clicked on yes. So far nothing has happened and there is no pop-up. I wonder if the fact that updated and FOTA are disabled have anything to do with it.
drago10029 said:
You can wipe the cache in the recovery menu if you have stock recovery. Follow these steps posted on Motorola's website. but on step 7 don't factory reset, just reset the cache instead.
EDIT: You won't lost anything
EDIT AGAIN: You need root to disable Motorola OTA since it's a system app.
Click to expand...
Click to collapse
Tried this method but the phone still prompts to install the downloaded update, which I must continue to postpone. Within the cache directory I have not seen the 165.44.1 update. I accidentally hit download a few days back, I would love to delete the download and remove the notifications before I accidentally apply the stupid thing. I've tried disabling the update service within Google Services Framework but that hasn't done the trick either.
Obviously I am missing something, but I'm baffled as to where this stupid downloaded update even resides. I haven't been able to locate the file itself with adb or any other file exploration. I'm already rooted.
motomesh said:
Tried this method but the phone still prompts to install the downloaded update, which I must continue to postpone. Within the cache directory I have not seen the 165.44.1 update. I accidentally hit download a few days back, I would love to delete the download and remove the notifications before I accidentally apply the stupid thing. I've tried disabling the update service within Google Services Framework but that hasn't done the trick either.
Obviously I am missing something, but I'm baffled as to where this stupid downloaded update even resides. I haven't been able to locate the file itself with adb or any other file exploration. I'm already rooted.
Click to expand...
Click to collapse
As of today, I am still on 4.4. I've clicked on yes. But with the two services disabled, no update is applied.
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
I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?
if any files have changed in the system, any, and just one, then you can not update via ota.
simms22 said:
if any files have changed in the system, any, and just one, then you can not update via ota.
Click to expand...
Click to collapse
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...
RichCowell said:
I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?
Click to expand...
Click to collapse
Click the OTA link in my signature for some more information.
RichCowell said:
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...
Click to expand...
Click to collapse
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Agreed, factory image should get you back to Ota ready.
simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
for the future, if you are flashing a factory img, then yes.
RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Same thing. Everything has to be 100% stock.
No need to wipe if you don't relock your bootloader.
RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?
RichCowell said:
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?
Click to expand...
Click to collapse
if it booted fine, and your about phone says 5.1, then youre fine.
simms22 said:
if it booted fine, and your about phone says 5.1, then youre fine.
Click to expand...
Click to collapse
Awesome, thanks
Need to decide now whether to bother rooting to make future updates easier...
I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?
sarshadd said:
I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?
Click to expand...
Click to collapse
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.
rootSU said:
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.
Click to expand...
Click to collapse
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
What does it say when you sideload?
sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
After you put the boot loader in sideload mode, unplug and replug the USB cable, then run adb sideload.
Trying to recover data after XT1096 5.1 black screen bug
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
rushramia said:
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
Click to expand...
Click to collapse
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
I'm in the same boat except I'm on vacation with out my computer. Can I factory reset from fastboot?
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
AGISCI said:
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
Click to expand...
Click to collapse
Thanks Chris,
I appreciate the response. Do you know where I might find the stock signed images for xt1096? I've somehow hosed my system img so now I can't even get into recovery to do a factory reset (keeps complaining 'failed to validate system image'). I'm hoping to re-flash the stock system.img to fix this problem. Let me know.
Thanks!
Sure here it is:
download
Sent from my XT1095 using Tapatalk
AGISCI said:
Sure here it is:
Click to expand...
Click to collapse
Thanks!
That got me back to where I started. System is no longer 'invalid' and my phone boots up to a black screen. The notifications still work and I can boot into fastboot or recovery modes. I guess my only option now is to bite the bullet and factory reset now (and loose my data). :crying:
Thanks again for all your help!
AGISCI said:
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
weird. I go into fastboot and got the options: normal boot, recovery, factory and some others and i can cycle through with vol down. vol up is select but no matter what i select it just boots normally (still have black screen)
do i need to unlock something?
I need some more info. Are you on stock rom? What version(4.4.4, 5.0, or 5.1)? Have you unlocked your bootloader with sunshine? Have you rooted woth mofo or kingroot?
Sent from my XT1095 using Tapatalk
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
This is my backup phone so I don't care for the data that is on it and just want it working again. It was rooted before and I needed it unrooted in order to download an app that was blocked by root detection. I tried uninstalling the root using Super SU in its settings, when I restarted my phone it just freezes at the AT&T white screen.
I'm still able to go into the boot recovery menu, I tried putting on the I537UCUCOC7 (5.0.1) firmware found here (https://forum.xda-developers.com/showthread.php?t=2629093). I downloaded it, extracted the zip, and renamed the file "update.zip" and put the file on a microSD then in the recovery boot menu I went to install from external and selected the update.zip. It sorta kinda looked like it accepted it but I get a red error message about the sideloader and I'm still stuck at the white screen when it boots.
What else can I do from here?
P.S. I already tried wiping the cache and data/factory restore options and that didnt work.
Is there anything else that can be done?
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
RemixDeluxe said:
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Click to expand...
Click to collapse
alex4cta said:
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4-active/general/guide-update-to-i537-att-firmware-t2835481