Updating after root - Galaxy S I9000 Q&A, Help & Troubleshooting

I rooted my gt-19300 about a week ago and now samsung have brought out the new firmware update. I'm unable to update. The new update downloads and asks for reboot. This take me to CWM where i hit the reboot option but the update fails.
Is there anyway round this? Or just a way to kill the annoying message that pop up every three hours reminding me to update haha
Thanks!!

You have lost your way, this is the i9000 forum
Sent from my GT-I9000 using xda premium

My bad
I'll just leave quietly haha

Related

[VZN] Update - How to stop it?

The latest Verizon update isn't doing me any favors. I'm a rabid baseball fan and it trashes MLB at Bat live game video and does some other rather unwanted stuff to Flash. It was easy enough to flash the original system back on and blow away the update so everything worked again but now the SGT insists on reminding me fairly often that there's an update I want nothing to do with. Any idea on how to shut it up?
Root your tab that'll stop ota updates.
Sent from my SCH-I800 using XDA App
Incorrect. Rooting will not stop it at all. Perhaps if you use root explorer and go into cashe file and remove it that might work for a bit. Not sure but rooting will not
Sent from my SCH-I800 using XDA App
Good luck with that. I deleted the 2 files in my cache folder using root explorer that had the correct size and date. It seemed to work..... untill I had to reboot my tab. After I rebooted, I got the notification again, and this time, there is no file with today's date or the correct size in the cache folder.
I was getting constant popups the first time around untill I deleted those files, after which, nothing untill I restarted. So those must have been the correct files. I don't understand where the new ones are now.
Sent from my SCH-I800 using Tapatalk
NomaSS said:
Root your tab that'll stop ota updates.
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
Rooting alone will not stop the ota. The developer of the custom rom generally removes the ota feature.
note I have not tried this since I already got the update....and if you brick something its not my fault...
you could try to change the ro.build.fingerprint so maybe the update service still think you already got the update. this method worked to stop a droid ota update.
in /system/build.prop file change it to:
ro.build.fingerprint=verizon/SCH-I800/SCH-I800/SCH-I800:2.2/FROYO/EC02:user/release-keys
Sent from my SCH-I800 using XDA App
In the past, people have renamed "Otacerts.zip" to "Otacerts.zip.bak" in /etc/security/ . You may also want to choose "Install Later" first, then delete the file in the cache folder on your SDcard. Then reboot.
You can use either Root explorer (easy option) or Terminal, though every time I try to install a Terminal emulator, it fails on my tab
I haven't tried this myself, but I will be doing it tonight.
my understanding with the cert rename is that the user will still get the download and the prompts to install....its just that it fails during install when the signature doesnt match
so you will be saved from accidently installing but will get a lot of notices that you need the update.
I could be wrong though.
Sent from my SCH-I800 using XDA App
This is bull****. Damn pop ups every 15 minutes, I feel like im trying to surf the web with AOL. My poor 4 year old was trying to watch a movie and I kept hearing her get upset, stupid update would interfere with the movie.
Im not going through all that bull**** just for an update I dont care about, there has got to be a way to kill this thing off.
Any progress on this? I read about editing the build.prop to EC02, but that didn't work for me either.
Sent from my SCH-I800 using Tapatalk
vwvapor said:
Any progress on this? I read about editing the build.prop to EC02, but that didn't work for me either.
Sent from my SCH-I800 using Tapatalk
Click to expand...
Click to collapse
What I did on my Droid Charge was back-up build.prop and then change every place where to referenced the old build number and change it to the new build number. Then I saved the file and then rebooted. I got one last warning about the OTA update and then it went away.

How to update Note after rooting and changing kernel

Hey guys,
I've always had HTC devices, and this is my first non-HTC phone.
I'm pretty familiar with HTC's RUU's, but I'm a bit confused with my Note.
I rooted my phone, and installed CWM and 3.0.15-franco.kernel... but stayed with Samsungs stock Android.
Now, this morning I received a mssg saying I had an update available, which I said yes to. After restarting, the phone told me that it was impossible to apply update.
Now I check for updates and there are no longer available.
I'm on 4.0.4.
When this happens again, how should I update? Why can't I see the update again?
D
That is just a notification..
After u flash a new rom u will get it..
Sent from my GT-N7000 using Tapatalk 2
It may.appear again after sometime
Reboot once
Sent from my GT-N7000 using xda premium

Received OTA, upgraded to 4.2.2 and DIDN'T LOSE ROOT!

About 10 days ago I received the OTA update to 4.2.2...
For your information... My Nexus is rooted using SuperSU and ClockworkMod 6.0.2.3
After reading about people losing root etc and having to redo everything, flashing SuperSU and stuff I decided to postpone the update.
I was working at an exhibition and had no desire to flash SU and redo the worx...
This morning I sat down, connected my phone to my PC (USB debugging appeared) and my phone connected as a Media Drive...
I initiated the update and rebooted the phone and guess what... My phone is still rooted... Everything is working fine...
Am I the only one or is this normal and did I overlook a topic here?
Anyway and for what it's worth, I thought this info might be useful.
That's because CWM can keep root for you.
Sent from my Nexus 4
steviewevie said:
That's because CWM can keep root for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
And so will TWRP
Sent from my Nexus 4
steviewevie said:
That's because CWM can keep root for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
Great, didn't knew this...
Guess my discovery wasn't such a discovery after all
This is great news i didnt even know this lol so tell me guys is there anything i have to do or just root it and thats it im good for updates?
AW: Received OTA, upgraded to 4.2.2 and DIDN'T LOSE ROOT!
I thought that with a custom recovery or with root you don't get the OTA update offered at all.
Sent from my Nexus 4 using xda app-developers app
I received the update, rooted and on CM... Kept everything else stock though and the update just came in... and stayed there for 10 days, couldn’t wipe the notification away. Anyway, I'm really happy it all went so smooth... Never expected it.
Cheers guys
Sent from my Nexus 4 using Tapatalk 2

[Q] cmw v6.0.3.5 non-touch warning on reboot

I just flashed CWM 6.0.3.5, seemed to be working perfectly. On the next recovery boot I got this warning.
Root can possibly be lost. Fix?
This can not be undone
no 7 times in a row (vertically)
yes - fix root (/system/xbin/su)
no 3 more times
I selected fix root from the 11 choices, and my ROM booted just fine. So i restarted in recovery, and again the same warning message.
Another thing I noticed was on the main screen of CWM at the bottom it says
cmw v6.0.3.5
warning no file_contexts
As i said AIOP mod is working fine, just don't like the warning message every time I assess recovery.
Any ideas?
You shouldn't be getting that message every time. But your recovery is outdated. Try the newest cwm in the open of the kit kat rom it's 6.0.4.5. I haven't had any problems with it.
Sent from my SGH-T679 using xda app-developers app
Damn, I wish I remembered how I fixed that problem when it happened to me.
Did you lose root permissions?
My guess would be either SuperSU binaries need to be updated or shouldnt have been updated, causing CWM not reading root properly. Dont quote me on this, its just my guess, haha. probably go with Dvarl's answer.
If you find a fix, please post how, so I can use it for future reference.
I'll check out that update and post what I find out.
Thanks for the help guys.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
You shouldn't be getting that message every time. But your recovery is outdated. Try the newest cwm in the open of the kit kat rom it's 6.0.4.5. I haven't had any problems with it.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Thanks for pointing me in the right direction! The updated CMW totally fixed the problem I was having. Flashed the Kit Kat Rom, working perfectly so far. The integration of Hangouts as your SMS is a little strange, but easy enough to get going.
BTW, fail for the new kit Kat ROM. Everything was great until my first reboot, then the ROM hung at the Galaxy screen. Had to pull the battery.
Sent from my SGH-T679 using xda app-developers app

Galaxy s5 update fail

Hey guys I had a update menu pop up. Went into recovery and got to 25%. After that phone rebooted and it said update failed to install. I checked the update screen again and it says im up to date. Dis a factory reset and says ita up to dat. Was it a fluke? I have provided a screen sgot to show my latest firmware to see if you guys know if its up to date. Thanks guys.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
jonathan413 said:
Hey guys I had a update menu pop up. Went into recovery and got to 25%. After that phone rebooted and it said update failed to install. I checked the update screen again and it says im up to date. Dis a factory reset and says ita up to dat. Was it a fluke? I have provided a screen sgot to show my latest firmware to see if you guys know if its up to date. Thanks guys.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Since your build number is saying nce i'd say no, theres some odin flashable ng3 files in the general section if you want to give that a shot, i personally dont think im very qualified to give suggestions as far as that goes though, so i'd wait for further instruction from someone who knows more than me.
Sent from my SM-G900A using Tapatalk
Yeah, kernel and build number don't look up to date. I'd think you could follow the guide to odin back to the nc3 completely and try the ota again, or use the ng3 stock rooted firmware available to odin everything up to current (but with root). I looked for stock unrooted ng3 and couldn't find it, although it may be available too.
jonathan413 said:
Hey guys I had a update menu pop up. Went into recovery and got to 25%. After that phone rebooted and it said update failed to install. I checked the update screen again and it says im up to date. Dis a factory reset and says ita up to dat. Was it a fluke? I have provided a screen sgot to show my latest firmware to see if you guys know if its up to date. Thanks guys.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Go to this thread and download the NG3 update and save it to your ex sd card then go to stock recovery and select install from ex sd card and you'll be good to go
http://forum.xda-developers.com/showthread.php?t=2862299
It's in the notes section #3
I've tried to side load and odin flashing but no dice...I got the s5 active btw...odin stops at initializing and the side load goes through but system stays in ne4
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Categories

Resources