So I used the confirmed working KitKat OTA update on here for my Droid Maxx and it worked but it's running like crap now. This would be the original soak test OTA that was pulled and I'm assuming they pulled it because of this reason. Does anyone have the more stable release in an update.zip yet? Thanks for your help!
the sbf is available here http://sbf.droid-developers.org/
I appreciate that but this erases the previous files and I only wanted to overwrite the bad files, the update.zip would do as such, correct? I'd hate to lose everything on my phone.
i dont think the update.zip would work if you are already on kitkat. you can use the sbf file i posted with a program called house of moto to flash and not have to wipe data.
The second update is the same as the first. They pulled the first update because there was something wrong with flashing recovery on some phones. The actual KitKat build is exactly the same. I wouldn't waste your time trying to reinstall anything. If you're having problems, the best idea is to back everything up and do a factory data reset.
Oh really? I thought there was more to it than that. I'll give a factory reset a go. Thanks a lot!
Factory reset is for apps and data only it does nothing for system issues. I would let it settle in for a few days if it doesn't fix it fxz is your only choice
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Factory reset is for apps and data only it does nothing for system issues. I would let it settle in for a few days if it doesn't fix it fxz is your only choice
Click to expand...
Click to collapse
"Running like crap" could just be app issues from the upgrade. Again, with an Android point release upgrade, it's not a bad idea to try a factory reset if you are having problems after the update before trying something as radical as reflashing from fxz. It may end up fixing any issues.
Related
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..
I have a droid maxx running stock rooted 4.4, and need to factory reset it or something similar, to totally reset everything. Does anyone know of a way to do this while keeping root? Thanks!
I've factory reset my rooted 4.4 Mini using Settings->Backup & reset. Reinstalled SuperSu after, still rooted.
jjlangen said:
I've factory reset my rooted 4.4 Mini using Settings->Backup & reset. Reinstalled SuperSu after, still rooted.
Click to expand...
Click to collapse
Thank you so so much!!! You just saved me countless hours of extreme frustration and possibly even buying a new phone..
Hope it fixes your issue. Not as good as reflashing the system, but that will definitely make you lose root.
kuz142 said:
I have a droid maxx running stock rooted 4.4, and need to factory reset it or something similar, to totally reset everything. Does anyone know of a way to do this while keeping root? Thanks!
Click to expand...
Click to collapse
Sorry to say if it is an issue with the system factory reset does nothing except delete user data like apps etc. If its a system app it may fix the problem other than that it wont do jack to fix the problem. Thats why root persists only reason to FDR is if an app is acting up and you can't fix it. That is why we need the fxz to fix a system issue.
bigv5150 said:
we need the fxz to fix a system issue.
Click to expand...
Click to collapse
Any way to keep root with fxz?
Not yet, unfortunately.
kuz142 said:
Any way to keep root with fxz?
Click to expand...
Click to collapse
That sucks cause last night night xposed framework threw me in loop. I had to fxz 4.4.2 from my rooted, write protect off state. Now I lost root. Any way to get it back? If not damn, I'm in pain from a mistake.
Sent from my XT1080 using Tapatalk
So I've been noticing my GPS takes a while to connect and when it does get a signal it constantly loses it and connects again.
Causing my GPS to think I'm turning down streets that I'm physically not, facing different directions and thinking I'm 5 blocks away from where my actual position is.
All my toggles are in the on position for GPS and I have the High Accuracy option selected.
Don't know what else it could be other then maybe the hardware going out? :'-(
Anyone else have this problem on stock XT926 kitkat?
Sent from my DROID RAZR HD using Tapatalk
DireWolfZero said:
So I've been noticing my GPS takes a while to connect and when it does get a signal it constantly loses it and connects again.
Causing my GPS to think I'm turning down streets that I'm physically not, facing different directions and thinking I'm 5 blocks away from where my actual position is.
All my toggles are in the on position for GPS and I have the High Accuracy option selected.
Don't know what else it could be other then maybe the hardware going out? :'-(
Anyone else have this problem on stock XT926 kitkat?
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
When you took the OTA to KitKat, did you just upgrade your existing configuration? You might want to look at wiping dalvik and cache first. If that doesn't work, then you might have to resort to a Factory Data Reset, which will wipe out all your settings, and see if that works. Usually, an issue like this points to stale files/settings/cache sitting around and if wiping cache/dalvik doesn't fix it, then usually an FDR fixes it. If the FDR doesn't fix it, then I would assume hardware issues or a bad OTA.
With the official FXD out now (http://sbf.droid-developers.org/phone.php?device=5), you could try flashing that to your phone via RSDLite or SamuriHL's House of Moto tool to see if a fresh flash of the official Kit Kat image will fix it.
If after that, the issue still persists, then I would definitely say it's a hardware issue. I haven't had any issues with the GPS on my phone.
iBolski said:
When you took the OTA to KitKat, did you just upgrade your existing configuration? You might want to look at wiping dalvik and cache first. If that doesn't work, then you might have to resort to a Factory Data Reset, which will wipe out all your settings, and see if that works. Usually, an issue like this points to stale files/settings/cache sitting around and if wiping cache/dalvik doesn't fix it, then usually an FDR fixes it. If the FDR doesn't fix it, then I would assume hardware issues or a bad OTA.
With the official FXD out now (http://sbf.droid-developers.org/phone.php?device=5), you could try flashing that to your phone via RSDLite or SamuriHL's House of Moto tool to see if a fresh flash of the official Kit Kat image will fix it.
If after that, the issue still persists, then I would definitely say it's a hardware issue. I haven't had any issues with the GPS on my phone.
Click to expand...
Click to collapse
Thank you for the reply. see when I upgraded i did a fresh flash. Completely wiped the phone and system and used the 183.46.10 fxz file and flashed it with RSDlite.
I'll try the other steps, wiping cache and dalvik. If that doesn't work I'll try flashing the fxz file again.
The thing I didn't do when I flashed the fxz file was regenerate the script with RSD script generator. I figured i just wanted to just save my data on my internal memory (photos, music etc) so I edited the original script my self and took out the (erase user data line)
Everything flashed over fine with no errors. now I'm wondering since I did that if it delete specific files.
I did format everything with twrp before the kitkat fxz update.
I'll try everything you mentioned before ruling out hardware though.
Sent from my DROID RAZR HD using Tapatalk
DireWolfZero said:
Thank you for the reply. see when I upgraded i did a fresh flash. Completely wiped the phone and system and used the 183.46.10 fxz file and flashed it with RSDlite.
I'll try the other steps, wiping cache and dalvik. If that doesn't work I'll try flashing the fxz file again.
The thing I didn't do when I flashed the fxz file was regenerate the script with RSD script generator. I figured i just wanted to just save my data on my internal memory (photos, music etc) so I edited the original script my self and took out the (erase user data line)
Everything flashed over fine with no errors. now I'm wondering since I did that if it delete specific files.
I did format everything with twrp before the kitkat fxz update.
I'll try everything you mentioned before ruling out hardware though.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
No, that should work if you wanted to save data, but I do know that sometimes, that can cause issues and a full wipe is necessary.
When I upgrade from JB to KK, I had issues with not being able to use blue-toot and wifi together. I did a factory data reset (wipes everything, including user data and internal storage as well as the internal sd card) and things cleared up since then.
I back up my applications and their data weekly with Titanium Backup and then I push those to my Google Drive, so whenever I wipe my phone clean, I can restore it back to where it was with the exception of any downloaded data files that are needed (such as offline maps for my GPS app, etc). So, doing an FDR for me is not an issue and it definitely helps with performance.
If you have a way of backing up your application data (and if you need to, your text messages), I would suggest doing that and then doing an FDR before trying to FXZ again. I know FDR sucks in that it wipes everything out and you have to set things back up again (Google account, etc), but it seems to be the one thing that fixes a lot of the issues people see after upgrading to KK.
Good luck!
iBolski said:
No, that should work if you wanted to save data, but I do know that sometimes, that can cause issues and a full wipe is necessary.
When I upgrade from JB to KK, I had issues with not being able to use blue-toot and wifi together. I did a factory data reset (wipes everything, including user data and internal storage as well as the internal sd card) and things cleared up since then.
I back up my applications and their data weekly with Titanium Backup and then I push those to my Google Drive, so whenever I wipe my phone clean, I can restore it back to where it was with the exception of any downloaded data files that are needed (such as offline maps for my GPS app, etc). So, doing an FDR for me is not an issue and it definitely helps with performance.
If you have a way of backing up your application data (and if you need to, your text messages), I would suggest doing that and then doing an FDR before trying to FXZ again. I know FDR sucks in that it wipes everything out and you have to set things back up again (Google account, etc), but it seems to be the one thing that fixes a lot of the issues people see after upgrading to KK.
Good luck!
Click to expand...
Click to collapse
Just wanted to thank you for the help and suggestions.
Backed up my internal memory, flashed the fxz file again (this time I left in the erase user data line), booted up and did a factory reset, restored my apps with titanium, restored my important files to my internal memory and like magic the GPS is working again.
Took a drive around the city for a bit testing it. I also turned it on and off and it's still finding the signal.
Thank you very much
Sent from my DROID RAZR HD using Tapatalk
DireWolfZero said:
Just wanted to thank you for the help and suggestions.
Backed up my internal memory, flashed the fxz file again (this time I left in the erase user data line), booted up and did a factory reset, restored my apps with titanium, restored my important files to my internal memory and like magic the GPS is working again.
Took a drive around the city for a bit testing it. I also turned it on and off and it's still finding the signal.
Thank you very much
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
Glad that fixed it for you. Usually, if nothing else works, FDR is my final resort and it hasn't failed me yet when things like this occur after updating.
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
simms22 said:
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
Click to expand...
Click to collapse
But this is showing up after rebooting, and I haven't used the camera for a few days. I also don't have any apps like skype that may be accesing it. Maybe I'm just being paranoid though.
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
rootSU said:
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
iJimaniac said:
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
Click to expand...
Click to collapse
Yeah you can use helium.
Sent from my Nexus 5 using Tapatalk
No issues here
iJimaniac said:
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
Click to expand...
Click to collapse
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
movielover76 said:
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
Click to expand...
Click to collapse
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Modified system
iJimaniac said:
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Click to expand...
Click to collapse
If your not stock your right, the OTA will likely fail. You can get away with being rooted, you'll just lose root.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
It's part of the price that comes with tinkering with your device.
movielover76 said:
If your not stock your right, the OTA will likely fail.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
Click to expand...
Click to collapse
Alright, good deal! Now I know for next time, thanks
Hello,
I'm a Canadian user (6045i) that installed the US firmware (7SR4-UE40) a while ago. I'm rooted (flashed SuperSU in Recovery mode).
Today, I finally decided that I wanted to get the latest firmware update (5.0.2-7SRA-UEA2). I did a full unroot with SuperSU, rebooted, checked that the phone was indeed without root access and tried to get the OTA update. Every time I try, it says my system is up to date. Why is that? What can I do to get the update?
Thanks.
So, I'm the only one with that problem?
Download UEA2 and install it like you did with UE40? That's what I've done to get the latest US firmware. We're not going to see the US OTA updates through a Canadian carrier. We have to install these ourselves, manually, just as you did with UE40.
Muskoka said:
Download UEA2 and install it like you did with UE40? That's what I've done to get the latest US firmware. We're not going to see the US OTA updates through a Canadian carrier. We have to install these ourselves, manually, just as you did with UE40.
Click to expand...
Click to collapse
I thought of doing that, but if I recall well, someone mentioned that doing this, you were missing some of the stuff that was installing while doing it with the OTA. Can someone confirm this?
Did you notice some improvement with your phone since you installed the latest update? As for me, the double tap never really works well (well maybe i out of 4 times), this is something I'd like to see improved...
metaleloi666 said:
I thought of doing that, but if I recall well, someone mentioned that doing this, you were missing some of the stuff that was installing while doing it with the OTA. Can someone confirm this?
Did you notice some improvement with your phone since you installed the latest update? As for me, the double tap never really works well (well maybe i out of 4 times), this is something I'd like to see improved...
Click to expand...
Click to collapse
As far as I know the firmware's posted here by users are the "exact" image you would get if you did a OTA update yourself. Improvement, a bit I guess. The double tap can still be an issue once and a while. I find a reboot solves the issue, but only for a while. The Chinese rom was the best performing firmware all around, but changed too much internally (files system) for my liking, so I went back to stock UEA2, with root.
Muskoka said:
As far as I know the firmware's posted here by users are the "exact" image you would get if you did a OTA update yourself. Improvement, a bit I guess. The double tap can still be an issue once and a while. I find a reboot solves the issue, but only for a while. The Chinese rom was the best performing firmware all around, but changed too much internally (files system) for my liking, so I went back to stock UEA2, with root.
Click to expand...
Click to collapse
So, no need to unroot to flash this firmware?
Do you have a link to download it? I can't find it at the moment... Thanks.
metaleloi666 said:
So, no need to unroot to flash this firmware?
Do you have a link to download it? I can't find it at the moment... Thanks.
Click to expand...
Click to collapse
Here's the post I followed (for others that might read this)....instructions are in the first post. I'm pretty sure you need to un-root, I did anyways.
http://forum.xda-developers.com/idol-3/general/convert-canadian-6045i-to-6045i-updates-t3177979
See the 3rd post of this thread for all the user submitted firmwares, UEA2 is at the top of the US firmwares, submitted by Brian117. As famewolf has stated in that thread, these are "out of the box".
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Hope that helps.....
Thanks! If I were doing this as an OTA, I won't have to wipe my device and start all over with the apps. Is there a need to wipe everything with this update? I did wipe everything when I installed the US firmware (from the Canadian) the 1st time, but I'm not too crazy to start all over again...
Try without wiping apps/data, should work fine. If not, you'll have to wipe everything. As your rooted you should have Titanium Backup installed, and doing routine backups of your apps/data. I have my apps/data backed up every night on a automatic schedule at 2 in the morning. It's always there on my external sd card should I have a issue. Makes swapping roms / firmwares a non issue.
Sent from my 6045I using XDA Premium HD app
Muskoka said:
Try without wiping apps/data, should work fine. If not, you'll have to wipe everything. As your rooted you should have Titanium Backup installed, and doing routine backups of your apps/data. I have my apps/data backed up every night on a automatic schedule at 2 in the morning. It's always there on my external sd card should I have a issue. Makes swapping roms / firmwares a non issue.
Sent from my 6045I using XDA Premium HD app
Click to expand...
Click to collapse
I do have Titanium. So, yes, I'll be able to come back to where I was quickly if I have to wipe everything. I was not rooted when I installed the US firmware at first, so I had to reinstall everything. Didn't think of Titanium before asking this time....
Thanks again!