I rooted the phone before the ota update. I rebooted and where the Galaxy S4 used to be is now replaced with samsung, custom with a unlocked lock on the screen. I watched qbkings video and when he rebooted, his screen wasnt the same, can anybody tell me what has happened? I also installed the OTA update with root, would that be a problem?
There is no problem. That custom unlock screen just means that you rooted you device. Its not an issue at all. You can download supersu from the play store and update the binary then uninstall the superuser app to get rid of it. You might need to reboot twice.
tmac42 said:
I rooted the phone before the ota update. I rebooted and where the Galaxy S4 used to be is now replaced with samsung, custom with a unlocked lock on the screen. I watched qbkings video and when he rebooted, his screen wasnt the same, can anybody tell me what has happened? I also installed the OTA update with root, would that be a problem?
Click to expand...
Click to collapse
Please use the "search function". The answer to your question has been posted many times.
Related
So I had the S4 from Rogers which I believe is the i337m. I flashed the Virgin Rom which is a 4.3 Google Play Edition Rom (my phone also says that it is a i9505G in the settings now) and a few times now, I get a message in the notification shade that a system update has been downloaded and needs to be installed. It says that it is the 4.3 edition update (even though I'm already on a 4.3 ROM) but when I click to install it, it just boots into TWRP and does nothing. I'm wondering, if I remove TWRP and return to stock recovery, will my phone install the update that it keeps prompting me to install, and somehow make my phone react like a regular GPE phone with OTA updates?
LiquidPrince said:
So I had the S4 from Rogers which I believe is the i337m. I flashed the Virgin Rom which is a 4.3 Google Play Edition Rom (my phone also says that it is a i9505G in the settings now) and a few times now, I get a message in the notification shade that a system update has been downloaded and needs to be installed. It says that it is the 4.3 edition update (even though I'm already on a 4.3 ROM) but when I click to install it, it just boots into TWRP and does nothing. I'm wondering, if I remove TWRP and return to stock recovery, will my phone install the update that it keeps prompting me to install, and somehow make my phone react like a regular GPE phone with OTA updates?
Click to expand...
Click to collapse
No, even if you return to stock recovery. You still won't be able to apply the new update. It will fail.
Sent from my GT-I9505 using Tapatalk 4
I'm not sure about TWRP, but if they don't have the correct buildprops that are expected by the OTA zip, you wont be able to install it.
I had the official clockwork recovery installed on my i9505G. When it tried to install the official OTA, it downloaded and booted into CWM and tried to install, but since this recovery is built for i9505, the buildprops are wrong, so the OTA fails to install. I extracted CWM and changed the device build properties to match what are on the stock i9505G. Then I booted into that CWM and used "adb sideload ..." to install the update which is still saved in your /cache partition. Since the update will break superuser/su, i then used "adb sideload ..." again to install the zip for superuser again.
Tmobile S4 virgin rom
keep getting the ota update for 4.3 even though i'm already on 4.3 is there any way to stop this from happening have tried to install ota update but phone is not a original google play edition so requirements don't match up and installation fails. just want to stop this from popping up on notification bar. thanks for any help.
ChrisS4 said:
keep getting the ota update for 4.3 even though i'm already on 4.3 is there any way to stop this from happening have tried to install ota update but phone is not a original google play edition so requirements don't match up and installation fails. just want to stop this from popping up on notification bar. thanks for any help.
Click to expand...
Click to collapse
Just hide the notification by holding it, click App Info, then uncheck show notifications.
works great
Raiken_ said:
Just hide the notification by holding it, click App Info, then uncheck show notifications.
Click to expand...
Click to collapse
Thanks that works great.just hate seeing on ny phone.
hello,
I let my 9005 downloaded a OTA update accidentally but I don't want to install it, in case it update the boot loader and give me trouble when I want to go custom roms.
do you guys know where is the downloaded OTA update file? it bug me to install the update every 3 hours now.
I tried to clear the cache in recovery but it doesn't work. I am not rooted yet...
http://forum.xda-developers.com/showthread.php?t=1856632
seems I need root access for that, and I don't to root it until I am sure the hardware is all ok.
luckily the device is still new, I will do a factory reset.
thanks.
seems I need root access for that, and I don't to root it until I am sure the hardware is all ok.
luckily the device is still new, I will do a factory reset.
thanks.
Ive got a weird issue that I cant seem to get around and I wanted to see if anyone else has had this problem.
I got a replacement phone from Verizon last week. It came preinstalled with JB and since we have Towelroot now, I let it take the OTA update.
I rooted with Towelroot and when I went to install SuperSU, it tells me Knox is active and asks me to disable and I say yes. At that point, the phone just sits there and grinds on disabling Knox. Ive let it sit an hour and it still just sits there grinding on Knox. Its never finished disabling Knox the first time and Ive flashed the phone back to factory and re-rooted 4 times now, Everytime its the same.
If I reboot after that and re-run SuperSU, it gives me the Knox warning again and when I say Okay, it immediately says Knox is disabled.
Check root and it shows Im rooted and behaves as such.
Then the problems start. I start getting stuff FCing all over the place. Ive tried to do a Fix Permissions from within BusyBox and that didnt seem to help at all. I unrooted and the problems went away. I rooted again and they came back and then I got stuck on the SuperSU Binary Needs To Be Updated loop where every time I update, it fails and closes SuperSU.
Has anyone had this issue and if so, did you figure out a way around it?
I had Same errors installing Chainfire's SuperSu Pro
But all is working good now.
it Gives root to what ever I grant access to, so no complaints here.
I Have seen other posts with same issue so I am sure CF is aware and working on the issue.
Also, I have not had any FC's since rooting and installing SuperSu
Thanks for the reply.. I think the FCs are due to Knox not being disabled properly but Im not sure.
Did Knox disable okay for you?
The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/
well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
waterbottels said:
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
Click to expand...
Click to collapse
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
kinstre11 said:
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
Click to expand...
Click to collapse
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
waterbottels said:
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
Click to expand...
Click to collapse
There is an unroot option in SuperSU (although I've never done it so I don't know if it actually unroots or just cleans up things to allow a clean unroot. The other thing I'm not sure it does is restore Knox which is something that will be checked for by the manufacturer). If you're taking your phone back or sending it in under warranty you probably should make sure you uninstall anything you need root for prior to unrooting, but if you're on a custom rom or want to make sure everything is back to factory (including Knox) I would recommend doing what I suggested in my last post.
Same Problem
Same problem as OP. I had a Note 3 originally that I took the update to 4.4.2 and used Towelroot and everything was fine. I recently broke the bejesus out of my Note 3 and got a replacement under the warranty. I used Towelroot on the new Note 3 and I am getting random freezing and a weird line that appears across the screen once it freezes. Sometimes it will reboot others I need to pull the battery.
What is happening? I am now back to stock and want to root again. Anyone have a solution to this?