Back story: I recently rooted my Droid Razr (it was my first time rooting an Android phone) and completed it without a hitch. However, the update that was released after I rooted downloaded automatically and I became annoyed with the prompt to install now or later. So I unrooted and installed the update. No problems occurred. Fast forward to this morning. A new update is available (it's been available for about a week now, I'd say) and I go to install it. The phone turns back on and says, "Software update has failed!". I am not currently rooted, I've been too busy to re-root the phone. Now I'd like to install this update. Does anyone have any suggestions on how I'd go about doing this?
Thank you for any replies.
Edit: I apologize in advance if this isn't the appropriate section.
Edit 2: I have another question. Is it possible to update a phone's firmware when they are no longer associated with a carrier. I have an older Android phone I'd like to use as a Wifi only phone for apps and such. Am I able to install updates? It seems like the answer would be no, because the phone wouldn't know where to search for the updates. Perhaps a manual install is available?
Questions belong in Q&A
Related
Hi, appreciate this is my first post and thus my question will be regarded with a certain amount of skepticism.. am only posting cos I think my issue is unusual and have not been able to find a similar question/answer through my searches on this forum
Basically, the issue is I rooted my Galaxy S3 (GT-I9300) a month or so ago, installed clockwork mod and superuser etc,. however I held off flashing a ROM because I figured my OTA jellybean update was imminent and wanted to see what the touchwiz jellybean looked like before installing Cyanogen or another ROM. wasn't sure if the OTA would come thru once I shed the stock ROM
So I waited for weeks for the OTA (am on Orange, now Everything Everywhere, in the UK) and have not received it.. last week I went onto Kies and saw there was a new firmware update, so I updated thru Kies thinking that might be what was needed to receive the OTA JB update. updated the firmware but still no JB update - however, now when I check my root status on Root Checker, or try to use any app that requires root, I'm told that I don't have "proper" root access.
My question is updating the firmware over Kies, did that mess up my root access.. am I now unrooted? (this doesn't seem correct) It seems to me I am in a limbo of sorts - not properly rooted anymore, but not fully unrooted either. I want to root the thing again so I can install cyanogen or supernexus, and I would appreciate advice on what to do - should I do a factory reset and then root again as before, or will this cause issues.. was just gon soldier ahead and do it but aware that this may cause problems if my phone already has files from the previous attempt on there.. for example the SGS3 toolkit V.6.0.0 I'm using says not to proceed with its root operations on a phone "that's already rooted" so am hesitant to proceed. Any advice would be appreciated. cheers
You've lost root with the update, just root again and it's all good.
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
jbrookley said:
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
Click to expand...
Click to collapse
You can still root it if the update wasn't installed. As long as it says your on mdk and not on me7 under "about phone" in the settings you should have no problem rooting. After rooting use a app like titanium backup or my backup pro to freeze sdm and fwupgrade....in system apps.
jbrookley said:
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
Click to expand...
Click to collapse
If it only downloaded, and you did not install it, then you are good to root. I would delete the update.zip file from the cache to be safe though.
Please read forum rules before posting
Questions and Help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD
Hi all, I'm pretty new here. I've been a longtime iPhone/jailbreak user, switched to Android last month and really happy with the freedom of customization this device has afforded me. I've been reading and learning a lot, and I have some questions. I hope you'll be able to help.
I now have a Verizon Galaxy S4. I followed these excellent instructions, and am now rooted on 4.3 (MJ7) and am liking it quite a bit.
But as of yesterday I've started to see alerts about a "Software Update Ready to install."
I asked a friend who has the same phone and he said he updated, and went from 4.3... to 4.3. He couldn't tell what had changed (if anything.)
So here are my questions:
1) What is this new update all about? It seems like it's not 4.4 KitKat, it's just a small revision to 4.3 Jelly Bean. Is there any info out there about what it contains?
2) I know I shouldn't accept the update, as it would make me lose root. And I don't want to lose root, I need it for too many things. So, using Root Browser, I went into /cache/fota and moved "update.zip" to my SD card, thinking it would help. Then I rebooted. After a few minutes, the "Software update available" notification returned. How can I remove this? If I'm not supposed to accept this OTA update, I don't want to be nagged about it. I don't want to accidentally tap it.
3) Is there a way yet to accept this update, without losing root or bricking my device? If so, how?
Thanks for any answers, I appreciate it and am happy to be here.
Use Titanium Backup to freeze the "sdm.apk" and "fwupdate.apk" applications. Or rename those two apps with .bak.
People are reporting taking the update and not losing root here:
http://forum.xda-developers.com/showthread.php?t=2565430
Place SuperSU in "survival mode" before you update and you should still have root afterwards.
Excellent, thanks for then pointers! I will give it a go.
It took a few tries... and a few reboots... but finally, I got it to work. I just got the notification that the update was successful. Sweet! (And, more importantly, I checked with RootChecker and I still have root.) For anyone else following along, the paid version of SuperSU is required in order to be able to invoke "Survival Mode."
I am now running JSS15J.I545VRUEMK2 and I Googled to see these are the changes:
KEY DEVICE ENHANCEMENTS
• Email connectivity has been improved
• Consistent Data roaming in Canada and Mexico
• Device will ‘Power On’ after software update is completed
• Non-Samsung chargers will work correctly with the phone
• Improved data connections while using (enterprise) proxy servers
Click to expand...
Click to collapse
Now, in order to prevent future updates from interrupting me, I went into Titanium Backup and I froze "sdm.apk."
But I can't seem to find the "fwupdate.apk" application. Is there some other name for this?
Thanks very much!
Hey, I'm rooted and s-off, running (firmware, I think) 2.06.605.1 710RD. I've been ignoring the software update Verizon sent out a while ago by pressing the home button on my phone whenever the update popup appears, but I'd like to make it go away for good, and the best way to do that is to update.
The thing is, I'd like to do it without the hassle of unrooting and going back to s-on (if I even need to do that) to update, then getting s-off and root again. I heard it's possible if you flash a pre-rooted ROM of the update through a custom recovery, and I found a pre-rooted, updated rom a while ago on the forum, but now I can't find it. The update is called HTC6435LVW_2.07.605.1-2.06.605.1.
First of all, will this work?
Secondly, I'm going to keep searching for the 2.07 rom, but can anyone let me know if they have a link to the thread?
Thanks for your help.
Edit 2: To all who saw my first edit, I have confirmed that this is the TTY update, not the 4.2.2 update. However, I think the 4.2.2 update will be available after I flash the 2.07 update, so please let me know if flashing a pre-rooted rom still works for entire OS updates (and if there even is a pre-rooted rom for 4.2.2 yet).
Edit 3: Wow, I should have finished reading xda's article on the subject before I edited last time. Apparently there's already a pre-rooted rom for the 4.2.2 update, so that won't be a problem. Ok, that should be all.