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.
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 just bought the droid razr maxx. there is supposed to be an OTA update to ICS soon. my question is, will i be able to switch back and forth from new rom and current rom? just wondering incase i dont like it. will it prompt me when the update is available, or will it do it automatically? also will it keep my current apps and settings after the update?
Once you upgrade thats IT, your stuck with the new, your apps should be fine if your stock and unrooted. The phone will inform you when an update is available, or you can check for updates to try to grab it sooner depending on the rollout schedule.
Could have done a search, there's approximately 1 billion ICS OTA threads already.......
Sent from my DROID RAZR using XDA
brons2 said:
Could have done a search, there's approximately 1 billion ICS OTA threads already.......
Click to expand...
Click to collapse
This was legit questions... this wasn't another "When is it" threads. Don't be too quick to jump.
BTW, Daniel, you mentioned that if you were stock, unrooted it would be fine. What if I'm rooted (still stock)?
RedRamage said:
This was legit questions... this wasn't another "When is it" threads. Don't be too quick to jump.
BTW, Daniel, you mentioned that if you were stock, unrooted it would be fine. What if I'm rooted (still stock)?
Click to expand...
Click to collapse
You will want to get the VooDoo OTA Root Keeper for free in the market.
Install, back up root.
When your update hits, go back into the app and select "temp un-root".
After the update, go back to the app and restore root.
Its been hit and miss for some ppl on the last OTA, has worked for me everytime tho.
stupidchicken03 said:
You will want to get the VooDoo OTA Root Keeper for free in the market.
Install, back up root.
When your update hits, go back into the app and select "temp un-root".
After the update, go back to the app and restore root.
Its been hit and miss for some ppl on the last OTA, has worked for me everytime tho.
Click to expand...
Click to collapse
Also don't freeze or delete any "bloat" as that can mess up your ability to update.
I appreciate the info guys!
Now, if we could just get the update...
daniel644 said:
Also don't freeze or delete any "bloat" as that can mess up your ability to update.
Click to expand...
Click to collapse
What about safestrap. If we are running sick rooted GB, OTA comes out, unfreeze all the boat, do I need to uninstall safestrap as well?
Many people have had trouble installing the leaks if they have SafeStrap and friends installed.
That doesn't mean an OTA update will fail though.
johnmagoo said:
What about safestrap. If we are running sick rooted GB, OTA comes out, unfreeze all the boat, do I need to uninstall safestrap as well?
Click to expand...
Click to collapse
When I restore the backup I made during the Safestrap install, it wipes out both root and Safestrap. But I made the backup as soon as possible before making modifications.
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Beartooth01 said:
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Click to expand...
Click to collapse
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Thanks - worked for a while - then popup returned
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
I did try that. The popup went away for several days and then came back. There must be at least one root-level app I haven't disabled.
Thanks for the help, but I'm afraid I still need a bit more.
Still having popups...
socal87 said:
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Click to expand...
Click to collapse
When I first got the phone, I disabled OTA, I ran the update - which failed, of course. It got rid of the popup, but I did not wipe the phone as I am a longtime Motorola Droid user and am not totally comfortable using Odin (This is my first Samsung and it's like going from Droid expert to Odin newbie). I have since restored nandroid and Titanium backups from the previous phone (this is a warranty refurb). The backups also included disabled OTA apps from my previous S4. Apparently, I missed one somewhere, as the behavior just recently returned. I'm going fishing on the root level again [sigh].
If anybody would be so kind as to list the exact .apks and their directories involved in OTA, I can make sure they are still disabled and run another failed update. This may be different from my Droids, since it is being referred to as a Samsung build update, and not an Android version update.
If anybody knows where the downloaded update is hiding, I can remove that as well.
Thanks in advance.
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Thanks also.
fxwrangler said:
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Click to expand...
Click to collapse
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
i just made a post about the same problem. I renamed them. so we will see what happens
To delete the OTA zip use a file explorer with root privileges like "ES File Explorer" navigate to /data/fota and delete update.zip
Beartooth01 said:
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
Click to expand...
Click to collapse
That link is dead. Can you please direct me to a good link for that? Thank you
re-rooting after MJ7 kernal pushed by google?
swolh said:
That link is dead. Can you please direct me to a good link for that? Thank you
Click to expand...
Click to collapse
Well - renaming SDM.apk and FWUpgrade.akp stopped the totally annoying push notification for google's new MJ7 build for the S4. But by renaming SDM.apk, my Verizon app visual voice mail stopped working. When I returned the SDM.apk file to it's original name, the visual voice mail works, but I get the annoying notification from google over and over.
I'm trying YouMail app for visual software and am waiting to hear from them about whether their app uses SDM.apk. If YouMail is like Verizon's visual voice mail and uses SDM.apk, then my next thought is to unroot the phone, let Google do their update to MJ7, then re-root. I'm wondering if anyone has done this.
My phone came with NG6. To root, I had to flash the NG5 stock kernal, then root using towelroot. Once rooted, I flashed the NG6 kernal. If I unroot and let google flash their new MJ7 kernal, will I be able to repeat the root process (flash NG5, the root, then flash MJ7)? If that route were possible, would I need to find a separate place to download the MJ7?
Is there any other way to stop google's annoying notificaton and pushing MJ7 at me? All help greatly appreciated.
---------- Post added at 09:58 PM ---------- Previous post was at 09:16 PM ----------
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
My apology. I missed this link first time thru this thread. That link to a thread titled "[HOW TO] Disable OTA Update Notifications!!!!!!!!!!!!!" is pretty helpful. We'll see in a day or two if the notification and push attempt continues, but I'm pretty optimistic following the instructions in that thread will stop it.
http://www.droid-life.com/2014/12/05/lg-g3-on-verizon-gets-advanced-calling-1-0-volte-in-update/
The update mainly brings Advanced Calling 1.0 and updates to some LG apps.
It looks like Advanced Calling also needs to be enabled on your account.
http://www.verizonwireless.com/supp...Turning Advanced Calling On/Off on Your Phone
Personally, I'd like to know if someone who is stock/rooted with no system files changed can accept the update and keep root. If anyone gets it and tests that, please report back. Also, include whether or not SuperSU is in survival mode.
With the previous update, I was stock/rooted with 1 system file that dealt with headphone volume changed. I had to restore the original version of that file, then the update completed and root was kept (without SuperSU survival mode being required).
I've done the check for updates on my phone, but nothing yet.
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
david_hume said:
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
Click to expand...
Click to collapse
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
lexluthor said:
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
Click to expand...
Click to collapse
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
I don't think survival mode is required. It wasn't went I went from 10C to 11C.
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
hawkswind1 said:
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
Click to expand...
Click to collapse
From what I read somewhere, I think you can turn it off if you don't like it. My update completed, it's optimizing apps now. Will post once I confirm I've kept root (or not).
I just updated mine. I upgraded from 11C and still have root. I put my SU in survival mode just in case, but I'm not sure if that was necessary or not.
Also, for those that are worried about being stuck on VoLTE. There's a new entry in the Settings menu that lets you turn the "Advanced Calling" on/off at will.
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
EDIT: nvm, got it.
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
xdabbeb said:
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
Click to expand...
Click to collapse
I 2nd this!
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Same thing here. I hope there is something else other than using LG Flashtool to download the stock firmware
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Here's another thing i'm noticing... before, I downloaded a couple UI themes to change the nav buttons at the bottom through g3 tweaksbox and after removing g3 tweaksbox, the buttons changed to stock on the home screen but if I go in to settings or any other app it still shows the "LG" logo as my "home" button... maybe some left behind changes that are preventing update?
lexluthor said:
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
I did this earlier, it shouldn't be difficult for you, assuming your admin isn't a jerk of course. It's a feature that needs to be checked on your account, but it's also a free feature, so I'm not sure what excuse they'd have for denying your request.
taihard said:
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Can't help you with your error code, but I can say that my rooted phone also reported as "modified" status before applying the OTA and it still does afterwards as well.
Please help
Phone is rooted and has oem rom ... and xposed framework for tweakbox philz recovery mode just keeps loading after i treid the update what can i do i cant get back into my phone at all please help
Also tried resotring a backup i made yesterday before any of this and its still doing the same thing please please please helpl
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
No. Xposed will block all OTA and removing system Apps will also.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
lexluthor said:
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
can one of you guys (or anyone else who took the update) use this code to pull the modem for us please?
(use terminal emulator)
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem-12B.img
Thanks!!
tech_head said:
No. Xposed will block all OTA and removing system Apps will also.
Click to expand...
Click to collapse
I had Xposed installed and it updated no problem. But I would think the system apps would make it fail though.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.