Hello.
I booted my Galaxy S 4G (rooted but not flashed) last week and a t-mobile update started. It did not finished though, and since then I get periodic warnings that the device manager can not boot. There is a cancel button. I press the cancel and it tries again. After 2-3 times, the phone operates as expected. Another warning has just recently appeared having to do with a Google Service not connecting properly. This too goes away rather quickly.
Should I un-root and look for an update, then re-root?
Thanks for any advice.
I was having the same issue! It was freaking annoyin. What i just end up doing which really solved all the issues. Was to flash the doexed ((sry if i spelled it wrong)) that its post on the development section of the sgs4g by whitehawkx. And i flashed it through odin. It was just simple, easy and worth it.
Sent from my SGH-T959V using XDA Premium App
Being rooted (or not) should have nothing to do with whether or not you get the update. The update removes root anyway, so that doesn't matter.
You should try manually updating via Mini Kies. Here are the instructions.
Related
Does anyone know how to prevent a software update on a rooted Samsung Galaxy Tab 2 7.0? *
My tablet auto updated to the new Jelly Bean about 3 wks ago and I hated it. *I have since restored my wonderful tablet back to the ICS 4.0 it came with and rooted it. *But 2 days ago it auto downloaded the software update again and will only allow me to postpone the update rather than completely refuse it.
I do not want to have to go through the whole process again. *Does anyone know how I can prevent the update from happening? *TY!
Freeze updater.apk with titanium backup.
Posted from my Fascinate using XDA Premium
Big thank you!
MultipleMonomials said:
Freeze updater.apk with titanium backup.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Hooray - it seems to have worked! I wasn't able to find the specific file name you mentioned, but I did freeze 2 "system update" files and that has removed the update notification from my notify list and also doesn't open the update postponed window any longer from the about/software update settings either. Thank you so much, MultipleMonomials, ty, ty!
Still having problems...
Well, it seems I spoke too soon regarding my last post. All seemed to work well after freezing two "system update" files using ROM Toolbox Pro. However, after shutting my tablet down that night and turning it back on in the morning, I have since been locked up at the Samsung logo screen. I've spent the past few days trying to research my options, did the fix permissions, reset to factory default, tried restoring backups (which I didn't have), all that stuff, and I am having no luck whatsoever.
I can boot into CWM6 Recovery mode and also boot into download mode, but otherwise, I cannot get it to load past the Samsung logo and I'm officially stumped now.
Can anyone offer some suggestions as to what I should try next?
Flash a stock-based ROM without wiping data. Make a backup first.
Posted from my Fascinate using XDA Premium
It worked...
MultipleMonomials said:
Flash a stock-based ROM without wiping data. Make a backup first.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
I'm back up and running and with the ICS that I wanted. I'm one happy camper! :victory:
Hello guys, I have a Samsung S3 that was purchased "unlocked" to work on T-Mobiles network. After that failed attempt, we switched over to Verizon. 3 weeks later the phone read a message "System Software not authorized". I tried the steps detailed: http://forum.xda-developers.com/showthread.php?t=1840030&highlight=system+software+not+authorized with no errors. However, the phone will not boot. I get infinite boot loop. Honestly, I dont know where to go next. The phone still shows a "unlocked" icon when booted also. All I want to do is get the phone back to its original VZW supported state. Thoughts?
.
Interesting enough, after another wipe of the cache the phone booted up. How can I remove the 'custom' icon and lock this phone back up? I don't want to be denied service at VZW in the future if possible.
You could flash a stock ICS ROM and then update using OTA and it would remove the root, unless its not activated on Verizon. If not, I'll help from there. Let me ask some people to see if my method would work first though.
Sent from my SCH-I535 using xda app-developers app
I have the Samsung Galaxy S3 sch-i535 d2vzw. Currently stock unrooted 4.1.2 for some tests. When I odin'ed back to 4.0.4, I went to settings, about phone, system updates: check for updates and it popped up per usual saying I had an update. I said yes and it preceeded to download. When it had finished it asked another pop up asked to update with the freshly downloaded software. Where does that downloaded software get stored? I wanted to download the new 4.3 system update so I could copy it to my computer and get to investigating but after I download it, I do NOT want to update my phone with it. Wary of anything to do with it because it has locked down and bricked a lot of peoples devices now. Thanks ahead of time.
Sent from my SCH-I535 using XDA Premium 4 mobile app
So, today I received an update. 4.4.3.
I downloaded (from Android). After that, I needed to reboot to install ...
But It didn't install anything! It just rebooted ... and now, after 20-30 seconds, the system is rebooting itself!
What happened? What can I do?
(Rooted phone)
You can't do OTA updates on a rooted phone. The only solution I would suggest would be to manually flash the stock .IMG Zip and Radio files
Sent from my Nexus 5 using XDA Premium 4 mobile app
Unfathomable said:
You can't do OTA updates on a rooted phone. The only solution I would suggest would be to manually flash the stock .IMG Zip and Radio files
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What you mean I can't?
I shouldn't receive or If I update, it'll crash?
Generally speaking when doing a OTA update on a rooted device it will either unroot the device and push the update, not push the update through because a custom recovery is installed, or not boot at all or softbrick with a bootloop.
Sent from my Nexus 5 using XDA Premium 4 mobile app
@Unfathomable .... Be careful with the advice you give posters in the forum. What you claim about rooted Moto G phones being unable to take OTA updates is total rubbish.
My XT1034 was fully rooted, all I did was replace the custom recovery with the stock recovery and then the OTA downloaded and updated my device to 4.4.3. The phone was still rooted with read/write access to all folders, files and apps and all I had to do was flash back my custom recovery.
Maybe you are quoting what happened to your device which wasn't a Moto G ....In which case you shouldn't be quoting it in this forum.
I was speaking in a general term. I'm very familiar with the moto g in fact and from the situation If the device will not boot the only solution would be to revert to stock.
I quickly deleted the cache folder ... and "it worked". Not rebooting anymore.
Well I apologize that neither of our responses were helpful lol I was under the impression you were running a custom recovery. I'm glad you fixed it though!
Marcos Schroer said:
So, today I received an update. 4.4.3.
I downloaded (from Android). After that, I needed to reboot to install ...
But It didn't install anything! It just rebooted ... and now, after 20-30 seconds, the system is rebooting itself!
What happened? What can I do?
(Rooted phone)
Click to expand...
Click to collapse
This is why XDA practically begs you to search the forum before posting a problem. Several things you all should know:
- The phone was rebooting because the recovery could not update and the phone sees the update files in /cache when it finally boots, and of course it restarts to apply the update...and will keep doing so until the update is complete. We've treated why this happens just a few days ago so I won't bother. Look it up in General.
- Moto G can receive OTA updates whether unlocked, rooted, whatever, so long as the stock ROM is running. Applying the update, well.....
- The stock recovery is actually not the best choice if you've tweaked your stock ROM. It will always cause the constant reboots if it sees something wrong without telling you why.
Look up the ANDROID 4.4.3 IS OUT post (or something like that). Read through, educate yourselves, then try out what has been suggested. It's easy...
Hey guys,
Hoping someone here might be able to help me get rid of the bane of my existence right now. I've been reading all over and using various methods other people seem to have had success with but nothing is working for me.
I have a Samsung Galaxy Victory 4G from Virgin Mobile. I'm also responsible for 2 others that are having the same issue.
A while back I had rooted all our devices and put TWRP on them but have total stock rom.
A few weeks ago we all started getting this system update prompt that lets you install now or later. If we tried to install it with TWRP it just boots into TWRP. So I put the stock recovery back on and took the prompt and let it reboot. It begins installing but halfway through I get a red yield sign and it stops and reboots the phone. If we go this route the prompt usually doesn't show up again for days.
So I went and tried custom recovery and custom rom next. Didn't get the update on the custom rom until the next morning when I woke up. Went and got a perfect custom recovery/rom package for the phone and went total stock. Same issue as before where it gets halfway through and fails.
I've tried navigating to the root/cache folder as another thread suggested and renaming the update stored there but the update has never shown up in that directory.
Basically now, periodically this prompt continues to pop up, sometimes very frequently on the foreground of whatever you're doing on the phone and constantly reminds/annoys the hell out of us.
I'd take a screenshot but it hasn't reappeared in 2 days since I last took the update and it failed.
Appreciate any help from anyone!
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had not thought to try going stock with no root. That is the only thing I haven't tried. Will report back. Thank you