I had a rooted photon and after numerous OTA updates to MR7 I decided to stock reset and tried flashing the CM5 release. I kept getting the snowy screen issue, so I wiped the phone with Android Recovery and managed to get to a working install. My problem is that the phone is on 45.2.5 and every time I manually push for an update, I am told the phone is up to date.
Are there any ways of manually applying the update, or flashing back to an older release and perhaps trying again? atm I have an unrooted 2.5 version.
EDIT: btw I am running Linux.
ota issues
I'm getting that same problem. I was rooted and unlocked then I re-locked my phone back to stock to get the ota but it keeps telling me I'm update. I'm trying to update to 4.5.7 but it want push the ota to my phone.
Related
I am on my second Atrix. I updated the first OTA to .91. I didn't initially care for it, but only tried it for a day or so. Exchanged phone for another problem under 30 day return. New phone downloaded OTA. Rooted to pull off OTA zip to stop update reminders.
I've searched the numerous threads about updating various .91 builds and betas. However, I'm not sure if I can just flash the ATT OTA that i've pulled off in a way that doesn't lock the bootloader to make it difficult to go back to .83. I would think the official .91 would not have problems like i've been hearing with the other builds and betas, or having to go through the trouble of applying a bunch of fixes and patches.
Basically I want to try .91 again without a lot of fuss with the ability to go back to the stock .83 if I really don't like it.
Hi, there are probably numerous questions similar to mine, but I couldn't find the right thread for me.
I recently unlocked my atrix's bootloader, and tried to update to the gingerbread update. Ultimately, I wanted to flash the Alien rom, but the gingerbread update (not the OTA one), caused my phone to be stuck on the Moto logo, so I flashed the 1.2.6 sbf on my phone.
Now, I'm not sure what I should do to update my phone to gingerbread since I read that if I update directly from 1.2.6, I will hard break my phone. What should I do?
By the way, I have been having troubles with an update to 1.8.3 via sbf. It keeps saying that the phone did not enumerate.
Thanks for all the help!!
phillyf8n said:
Hi, there are probably numerous questions similar to mine, but I couldn't find the right thread for me.
I recently unlocked my atrix's bootloader, and tried to update to the gingerbread update. Ultimately, I wanted to flash the Alien rom, but the gingerbread update (not the OTA one), caused my phone to be stuck on the Moto logo, so I flashed the 1.2.6 sbf on my phone.
Now, I'm not sure what I should do to update my phone to gingerbread since I read that if I update directly from 1.2.6, I will hard break my phone. What should I do?
By the way, I have been having troubles with an update to 1.8.3 via sbf. It keeps saying that the phone did not enumerate.
Thanks for all the help!!
Click to expand...
Click to collapse
I'm surprised you aren't already hardbricked.. Use the OTA updates until 1.8.3 (RSD shouldn't be used at all really) and then re-root and unlock whatever using: http://forum.xda-developers.com/showthread.php?t=1182871.
If it did not reenumerate, then all you should do is boot back into RSD and see whether that fixes it.
http://forum.xda-developers.com/showthread.php?t=1163342
this gives stock 2.3.4 without touching bootloader
Hey guys,
I was gone for a bit and came tonight in the hopes of rooting my phone finally. I was pretty disappointed when I realized that because Im on MI1 I cant really do much (I guess you could maybe flash to Me7 and then flash a rom). I had rooted my phone a while back but then with the OTA updates I had to reroot a few weeks ago. One thing I have noticed is lately my phone keeps downloading and attempting to install an update from Verizon or Samsung but then just says an error occured and nothing was done to my phone. Does anyone know what this is or how I could stop it from occuring every night? Each time it fails it asks me to set a new time to try again.
*Edit*
It fails updating the software from Mi1 to mj7
Chris
If you want to stop OTA update notifications, use Titanium Backup and freeze FWUpdate and SDM. Just remember you'll need to unfreeze them if you want to manually check for software updates.
Hi, I have a short question for a weird situation.
I was running Android 4.4, rooted and CWM installed. Got a notification for 4.4.2 update being ready (like, a week after upgrading to 4.4), and tapped it. Phone reboots into debug mode to install it, but then CWM starts yelling at me saying this zip I'm trying to install is unsigned.
So I stop the upgrade. Phone reboots back into Android 4.4 and I don't get the update notification icon again.
Two questions:
- will I get the update prompt again? if not, can I do it manually while keeping all my stuff like happened on the 4.4 upgrade?
- is the Android 4.4.2 update really unsigned? is there a danger in accepting it?
I'm not sure what to do now since I didn't have CWM flashed when I did the upgrade to 4.4, which went completely smooth.
OK so I got the upgrade notification again today. I updated and everything's fine. So yes, the Android 4.4.2 update was unsigned (or CWM couldn't verify it) and yes, your device will get the update again if you refuse it.
Now to reflash CWM so I can reroot it...
Running latest Pixel Experience w/ root right now and was wondering about OTAs.
When updating, is there anything I need to do with root or can I just run the OTA normally and update?
Last time I ran an OTA update w/ root, my phone would restart randomly sometimes during usage and I couldn't figure out why so I reflashed everything and it hasn't happened since.
Leads me to asking whether updating while still rooted messed with the phone in some way. So yeah, do I need to unroot before running the OTA or do I unroot and then OTA and then reroot?
(Also, if I need to unroot, how do I do that? Have only ever rooted phones, never had to unroot one.)
thevietmonk said:
Running latest Pixel Experience w/ root right now and was wondering about OTAs.
When updating, is there anything I need to do with root or can I just run the OTA normally and update?
Last time I ran an OTA update w/ root, my phone would restart randomly sometimes during usage and I couldn't figure out why so I reflashed everything and it hasn't happened since.
Leads me to asking whether updating while still rooted messed with the phone in some way. So yeah, do I need to unroot before running the OTA or do I unroot and then OTA and then reroot?
(Also, if I need to unroot, how do I do that? Have only ever rooted phones, never had to unroot one.)
Click to expand...
Click to collapse
disable magisk modules, reboot then try.
better to just n download the rom and dirty flash imho