We have 4 GS5s in the family. I towel rooted all, and have been diligent updating them through the stock firmware releases. 3 of the 4 were updated to NG3, but I forgot to update one of them (was on NE6). That phone received the Tmobile message to update, which I declined.
I have since updated that phone to NG3 using Mobile Odin Pro (still rooted). I figured I was good. This morning, it asked again to update.
My guess is the update file was downloaded and sitting in some directory on the device, and that's triggering the update notice.
Question: Where would I find this file on the device so I can delete it?
Thanks...
No, a new update just rolled out, its NG4. Supposed to fix audio issues and such. But updating may cause you to lose root.
ctaranto said:
We have 4 GS5s in the family. I towel rooted all, and have been diligent updating them through the stock firmware releases. 3 of the 4 were updated to NG3, but I forgot to update one of them (was on NE6). That phone received the Tmobile message to update, which I declined.
I have since updated that phone to NG3 using Mobile Odin Pro (still rooted). I figured I was good. This morning, it asked again to update.
My guess is the update file was downloaded and sitting in some directory on the device, and that's triggering the update notice.
Question: Where would I find this file on the device so I can delete it?
Thanks...
Click to expand...
Click to collapse
decimater said:
No, a new update just rolled out, its NG4. Supposed to fix audio issues and such. But updating may cause you to lose root.
Click to expand...
Click to collapse
What he said, but you can ALWAYS root this phone again with ODIN. Yes, you'll trip knox, but tmobile doesn't care.
ctaranto said:
We have 4 GS5s in the family. I towel rooted all, and have been diligent updating them through the stock firmware releases. 3 of the 4 were updated to NG3, but I forgot to update one of them (was on NE6). That phone received the Tmobile message to update, which I declined.
I have since updated that phone to NG3 using Mobile Odin Pro (still rooted). I figured I was good. This morning, it asked again to update.
My guess is the update file was downloaded and sitting in some directory on the device, and that's triggering the update notice.
Question: Where would I find this file on the device so I can delete it?
Thanks...
Click to expand...
Click to collapse
YOU CAN UPDATE WITH MOBILE ODIN PRO AND RETAIN ROOT. AFTER THAT YOU CAN UPDATE THE BOOTLOADER WITH PC ODIN BY FLASHING THE FIRMWARE ONLY FILE IN THE CP SLOT. ALL FILES ARE HERE http://forum.xda-developers.com/showthread.php?t=2761412 THIS WILL NOT TRIP KNOX
To answer my own question: /cache/fota contains the update zip file. I deleted it, rebooted, but was still prompted to update (though it didn't redownload the file).
I have since updated all phones with NG4 using Mobile Odin Pro and PC Odin. All worked swimmingly well and still have root.
There are two relevant system apps. The OTA update app and the OTA update notification app. Simply disable the latter or both as you wish. A simple search will confirm the exact app names for you, although they are pretty obvious if you just look with a file browser. Some carriers, notably Verizon and ATT do like to rename such apps, typically by appending a prefix to the app name.
.
Related
as the title says, after rooting, i am unable to check for any firmware updates. i realize it doesnt mater right now as there is noithing out right now, but i like to check often just in case tmobile releases something or samsung. when i go to check for updates by selecting settings>software update and then a warning message pops up: DM initalisation is not ready, Check network or SIM card
Any ideas would be greatly appreciated
I was about to ask this same question, and yes i am also rooted. Just wanted to post that you are not alone on this one.
thats good to know, i was beginning to wonder if i was the only one having this problem, for now i unrooted and flashed back to stock using odin, but i miss having root and some of the apps i was using. I am not willing to give up the ability to check for new firmware though as my source at work told me that updates are coming in the next 2 weeks and that we should be getting a text message about them in the next week or so. and just so people know, it wasnt a tmobile customer service rep, i work for deutsche telekom so we here things first usually.
I have this same issue, where I'm unable to check for firmware updates. I am not rooted though... I just bought the phone today and when I click the 'Software Updates' option it says 'No firmware' in a pop-up message. This problem is not only associated with rooted devices.
joshuapurcell said:
I have this same issue, where I'm unable to check for firmware updates. I am not rooted though... I just bought the phone today and when I click the 'Software Updates' option it says 'No firmware' in a pop-up message. This problem is not only associated with rooted devices.
Click to expand...
Click to collapse
Read the first post again... yours is the normal message that is displayed when no firmware update is available...
Also, I'm rooted and the update seems to be working fine.
I'm rooted and it pops no firmware.
Sent from my SGH-T959 using XDA App
If I flash back to stock it works fine when I use odin to go back to stock, but if I reroot it says the same thing. Nothing ever stops it from saying what I posted in the OP. I need some help funding a fix or ok won't be able to get the froyo update when it releases.
Sent from my SGH-T959 using XDA App
If I use oclf to root and apply the fix, then unroot using oclf, will the factory ota not work?
Sent from my SGH-T959 using XDA App
Duuude don't worry about it. People will post ROM clockwork backups of the froyo release / stock odin flashes of it / etc.
Anyone will be able to update, however they do so... And just wait til you hear about it THEN unroot and update
yep i'm rooted to and it checks for filmware just fine .
im rooted and get the no firmware message
r0me0ne said:
im rooted and get the no firmware message
Click to expand...
Click to collapse
... *sigh* Because there isn't a UPDATE for the Vibrant.
IF I ROOT, WILL I GET OTA UPDATES?
Yes. Rooting will not prevent this, unless you flash a custom ROM that will block receiving the OTA update. If you do receive and download the OTA update, you will lose root. Typically within hours of the OTA becoming available, thanks to some fine XDA folks you can get the update WITH root. You would simply need to download and flash the update like a normal ROM.
Click to expand...
Click to collapse
Rooting doesn't mess with your OTA updates, when you update with the OTA it will remove your ROOT. The only way to interfere with OTA's are flashing custom ROMs.
But you cannot get the ota update when it releases if the check for update option under settings is not working. All I want to know is why the firmware update option is broken and how to fix it.
Sent from my SGH-T959 using XDA App
When I first got my phone I got the message Check network or SIM card. I rooted the phone and still got that same message. I restored to origanal and got the message'No firmware'. Now again I am getting Check network or SIM card.
tpreludesh said:
But you cannot get the ota update when it releases if the check for update option under settings is not working. All I want to know is why the firmware update option is broken and how to fix it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It seems like your phone was more than just rooted. What method did you use to root?
Note: Yeah, the "No Firmware" message is the normal message you get if there's no update available, aka, your phone is searching for and/or receiving OTA updates just fine.
Leoslick said:
If I use oclf to root and apply the fix, then unroot using oclf, will the factory ota not work?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This was my plan. Although, I'm reading posts that imply that even though a phone is rooted, if the user hasn't flashed a custom ROM, they'll still get the OTA update, and getting the OTA update will unroot the phone.
When this happens, root-necessary apps like ryanza's lag fix, titanium backup and android system info won't work anymore right? Will they need to be uninstalled and reinstalled? Or will I just need to re-root?
Sorry, I'm new to Android and don't know the typical process stock ROM root users go through with OTA updates.
Genuinely, thanks for any feedback.
Yes I wanna know this too. I'm holding off on getting apps for root only because I think they might mess something up. Also I thought I read set cpu spook might mess up the vibrant running oclf. Anyone?
Sent from my SGH-T959 using XDA App
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,
I could only find people asking for rooting 14.1.B.2.257, but no statement if root is kept if I simply update an already rooted device.
Do I need Rootkeeper, will it just stay rooted without me taking additional steps or is it currently not possible to keep root?
Regards,
Hidden
Yes, as long as you update OTA (Over The Air) and not through PC Companion. Change the CDA to a country that has received the OTA.
Alright. I don't need to change the CDA (whatever this is), my phone is already telling me to update for a few days.
Am I doing something wrong? The Update always fails after a few seconds. I rooted using vRoot and the only change I made was switching the boot animation which I already tried to replace with the original one.
I too have the same problem with OTA update. i'm rooted nothing else it downloads then goes into installation but it doesn't and it tells me that I couldn't install. any idea guys. is vroot working on .257 yet..?
jaime4272 said:
I too have the same problem with OTA update. i'm rooted nothing else it downloads then goes into installation but it doesn't and it tells me that I couldn't install. any idea guys. is vroot working on .257 yet..?
Click to expand...
Click to collapse
Hi,
There seems to be the same conversation over a few similar threads...
Anyway, I also am in the same situation.
I received the OTA, so I installed Voodoo OTA keeper and tried to install the update.
C6802, originally HK, changed buildprop to Vietnam over 2 months ago.. updated a few times and have been using this .532 for a while now.
As you describe, after download of update, start the update procedure, phone reboots in update mode, but after about 5 seconds, it reboots again into the normal boot mode and sequences, failing the update.
I know connecting it to the PC Companion and upgrading it would solve the update error, but my main interest, as yours probably is too, is to keep the root, so that there is no hassle of having to unlock the bootloader and flashing backwards and forwards...
My .532 Vietnam firmware is too good (with root) to think about updating, because short of this update bringing increased battery life that is purely amazing, it will not bring any benefits to me. I am one of those lucky ones with no screen issues what so ever..
jewelkobayashi said:
Hi,
There seems to be the same conversation over a few similar threads...
Anyway, I also am in the same situation.
I received the OTA, so I installed Voodoo OTA keeper and tried to install the update.
C6802, originally HK, changed buildprop to Vietnam over 2 months ago.. updated a few times and have been using this .532 for a while now.
As you describe, after download of update, start the update procedure, phone reboots in update mode, but after about 5 seconds, it reboots again into the normal boot mode and sequences, failing the update.
I know connecting it to the PC Companion and upgrading it would solve the update error, but my main interest, as yours probably is too, is to keep the root, so that there is no hassle of having to unlock the bootloader and flashing backwards and forwards...
My .532 Vietnam firmware is too good (with root) to think about updating, because short of this update bringing increased battery life that is purely amazing, it will not bring any benefits to me. I am one of those lucky ones with no screen issues what so ever..
Click to expand...
Click to collapse
I also have what you describe, but even updating via the PC Companion did not help. But it seems keeping root is a little tricky and I have no screen issues either, so I think I will just hold off on this update...
I also have the same problem (failed ota update)
Sent from my GT-P5100 using XDA Premium 4 mobile app
I have the same problem. v14.1.B.1.510 but the OTA downloads, switches off the phone, tries to install but fails. I've used vRoot to get rooted as soon as I unboxed this phone. so does this mean I can't update, ever??
Sent from my C6833 using Tapatalk
I can't guarantee this will work but try to temporarily un-root the phone with Voodoo OTA Rootkeeper.
Unroot with voodoo didn't work
Sent from my C6833 using Tapatalk
keratos said:
Unroot with voodoo didn't work
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Try to unroot from the SuperSU app.
Unroot with superSU didn't work either. the Unroot worked but not in the way this OTA needs, it appears
Sent from my C6833 using Tapatalk
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
reckert said:
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
Click to expand...
Click to collapse
It's just small bug fixes for bluetooth connectivity and updates for KNOX 2.0.
Oh noze! Search is borken again.
How do you stop the ota updates
siouxhockey11 said:
How do you stop the ota updates
Click to expand...
Click to collapse
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
BrianLayman said:
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
Click to expand...
Click to collapse
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Fadtydawg said:
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Click to expand...
Click to collapse
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
michaely123 said:
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
Click to expand...
Click to collapse
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
wulto said:
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
Click to expand...
Click to collapse
Will this work for non-rooted phones?
dwmartin6341 said:
Will this work for non-rooted phones?
Click to expand...
Click to collapse
No u need a rooted phone.
Fadtydawg said:
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
Click to expand...
Click to collapse
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
stuartv said:
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
Click to expand...
Click to collapse
It will just keep bugging you with the prompt everyday unless you root and freeze the apps.
With my wife's phone I went in to settings, application manager scrolled over to all & found SDM app & forced stopped it. Notification is now gone.
She IS NOT rooted.
I also have it auto hibernate using greenify so it does not come back.
Sent from my SCH-I545 using Tapatalk 2
So is this update buggy for those who were unrooted? Or just for those who were rooted and took the update?
I wonder if we were to unroot, take the update, then follow the root instructions if many of the problems go away?
Sent from my SCH-I545 using XDA Free mobile app
My wife's S4 is totally stock and she's had zero problems with the update. Took it earlier today.
After playing around with the update for a while, it looks like we have finally lost write access to the SD card like we were supposed to since the first Kit Kat update. I cannot write to the SD card (unrooted) with any file explorer, and my SMS backup app fails at writing to the SD card.
Zelmo88 said:
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
Click to expand...
Click to collapse
I read your post..updated for the heck of it..FDR'd it...random rebooted after a a few minutes.
Its been 2 days so far, and the thing reboots 3-4 times a day.
I noticed that sometimes before it reboots, I'll unlock it, and it wont even register my security swipe..Then it reboots..Sometimes, if it does let me in, tapping on an icon does nothing...then it reboots...Other times, like this morning, it was just sitting on the end table, and it rebooted. Boy, you weren't kidding about the reboots.
BTW..All stock.
Here's what I did, worked.
I used the towel root method posted here (and other places I'm sure):
Ok...Forum won't let me post a link because I'm new. So Google "Root Verizon Galaxy S4 SCH-I545 on I545VRUFNG6 Firmware" and it will be the top choice from droid views.
Read the comments section too I posted the issue I was having then reinstalled super SU, flashed the NG6 Kernal and I've been good to go.
Hope it works out for you, I'm on NG6 with root, no errors, no reboots.
Okay here's my tale of woe..
I rooted my phone last year - but at some point - took an update and lost root.
Though the phone still displays the "custom" boot screen with the padlock.
I tried to take the Lollipop update through the OTA but it fails and I get the "laying on his back" failed Android dude...
The phone DID take the first update.
I have: wiped cache in recovery, wiped data and cache in download manager.
No luck.
I have tried loading the NC5 kernel back on (via Odin 3.09) - but that makes the phone 100% unstable...reboots every 3 minutes..no access to apps - they lock and reboot etc etc.
Loaded the NG6 kernel back on to re-stabilize the phone and tried to Kies the update.
Kies downloads the update then when it tries to apply it the phone boots into "download mode"
I have been advised to:
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Click to expand...
Click to collapse
and - of course that doesn't work. NC5 won't let the phone run long enough to take an update..
It has been said:
Try to flash the OC1 with the pit file
Click to expand...
Click to collapse
But I haven't found the stock OC1 file anywhere to even try and begin to get it loaded.
Honestly - I'm not even really concerned about rooting right now. I'd really just like to get the phone back to a stock configuration and kernel and lollipop.
Developer mode is enabled. Obviously both Kies and Odin talk to the phone with no problems.
Any ideas ?
Thanks, Dan
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Yes.
Maybe I need to clarify.
I do not care about root at this point. I just want to get the phone back to a stock state and take the Lollipop update.
I'm curious as to why I will never be able to update beyond Lollipop.
Doesn't matter I guess - the phone will have been replaced by then - but still...why ?
Thanks, Dan
CyrusKhane said:
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Click to expand...
Click to collapse
I've downloaded (3) different 4.4.2 Firmwares.
FNK1
FNC5 (No Wipe)
FNG6 (No Wipe)
Any opinion on which one is best ?
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
I would use the ng6. That's what I was running.
Rip Syntaxx said:
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Manually - from these (XDA) forums.
danielzink said:
Manually - from these (XDA) forums.
Click to expand...
Click to collapse
Hmm... I'm not sure if it makes a difference to download OTA instead of manually. I would think it's worth a shot flashing NC5 (if it will let you downgrade) and using the software update feature to update OTA the rest of the way.
Sent from my SCH-I545 using XDA Free mobile app
Got it finally !
started out by flashing (FNG6 (No Wipe)) in Odin 3.09
That got me to regular boots with no "custom" screen showing the lock symbol.
Then I had to take OTA updates to FNK1 then the OTA preliminary Lollipop update then (OTA) finally Lollipop itself.
No root - but that's OK.
It took about an hour and a couple shutdowns to get things running smoothly but it's all good now.
Thanks everyone for their help.