I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
hondaboi20002 said:
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
Click to expand...
Click to collapse
From what I have read the answer is NO. I think you are SOL until a new root method is found.
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
I believe that is your only option, yes. To my knowledge, there is no way to revert back and you're stuck. Unless you'd like to just keep your current phone and wait until someone roots the new update, but your only other option would be to exchange it.
In your opinion, do you think the devs will find a way to crack this update and obtain root?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
Correct. That is *IF* the new phone doesn't already have the update installed, or the sales rep doesn't install the update while activating it and getting it ready for you.
Rumor has it that they already have root, but aren't releasing how until they can find a way to also unlock/patch the boot loader. They are said to be afraid of having Samsung/Verizon block this root method before they can use it to unlock the boot loader. Will they ever get it? Will they ever release the root method? That is anyone's guess.
So for now, it looks like the 16gig DEV edition direct from Samsung, without warranty, is the only option if you definitely want to root and flash custom roms now and "forever". But is it still available? or did they sell out yet?
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
You can block the OTA updater with titanium backup. I'm not on a stock ROM, so I don't remember the updater app name.
Sent from my SCH-I545 using Tapatalk 4 Beta
SDM
That sucks. You gotta keep your eye on those reps :cyclops:
i never let any sales person set up, activate or even power up any phone i buy. if they chose to do so i cancel the order and buy on line where it comes sealed. i always tell them i'm in a rush and i'll take care of activating it afterwards. only one has ever refused and i told him to cancel the sale since he decided to open a product i purchase without my consent. he did get me a new one after that.
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
That is assuming the new phone you get isn't updated b4 u turn it on...
Sent from my SCH-I545 using xda app-developers app
Ok, got a new S4 and this worked !!
Ok, everyone I got a new S4 and activated at Verizon which it immediately started download pretty much as soon as it was turned on. I immediately disabled mobile data, turned it off and then took out the sim card. Once I got home, I hooked this baby up to my PC and rooted...success, finally! I used the I545 all-in-one-root tool which includes OUDS clockwork. http://www.droid-life.com/2013/05/30/all-in-one-root-tool-released-for-verizon-galaxy-s4/
My questions is I have installed ROM Manager so that I could do a backup, but when I first open ROM manager, it says I need to install a custom recovery even though I have OUDS clockwork built in. Do I need to install clockwork from within the ROM manager app? I can reboot into recovery, but its the OUDS "generic" recovery, for lack of a better word. Is that recovery good to go for backing up, flashing another ROM or do I need to use the ROM manager to install CWM from with the app itself? Hope this makes sense. Thanks everyone!!
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
dopediculous said:
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Since I have been doing smartphones, I have NEVER updated, I wait until someone has tried it. and even then, I wait for a dev to cook it up. And everyone better hope you do not have to do any replacements thru the carrier, you WILL get a bootloader locked device with the newest release, NO bootloader fix.
Need to find alternatives.
k1mu said:
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Click to expand...
Click to collapse
That's great news to hear! Unfortunately my location was dead yesterday and I didn't sell any S4's. Just stupid idonts to bubblegum chewing pop tarts and grandparents. Ugh *face palm
Sent from my SCH-I545 using xda premium
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
Yeah, I ordered my S4 online, and it let me defer the update. It downloaded, then said ready to install would you like to install now or later? I set the timer to 12 hours, rooted, installed recovery, flashed AOKP, and bam, no worrying about OTA updates.
Sent from my SCH-I545 using Tapatalk 4 Beta
hondaboi20002 said:
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
Click to expand...
Click to collapse
What I suggest is what I did.
Do not place the sim into the phone.
My phone came from Wirefly.com without the sim card installed.
Power up without sim card, boot directly to download mode, connect to pc usb port, run Odin, follow rooting procedure.
Only after you freeze SDM using titanium backup, should you consider inserting the sim card.
Also while on wifi samsung will ask to install update, say no.
P. S. I installed samsung drivers, and Odin. I did not install kies which I have read also tries to install the update.
Related
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
So, currently I am running Stock with root injected and the bootloader is unlocked, and the only real tweak i have going with the device is Google Wallet. I'm at work and suddenly my phone starts asking me to preform an OTA update...I went a head an deferred the update for a few days to determine the best way to go through with this.
1)I assume this is going to break my root when i do it and it will relock my bootloader, am i correct about this?
2)If it does, then Google Wallet will stop working also, right?
3) If it will do the above, how can i put a stop to this OTA
4) If its not possible to stop this update and i will loose all my features, do i need to go a head and de-activate google wallet on my device?
5) has anyone with a rooted device gone through with this update yet, i know it just popped up in the last hour or so, but i am looking for any advice i can get because ideally i want to keep my root, unlocked bootloader and GWallet working.
My update failed
I'm rooted running stock with a few little tweaks (nothing I can't live without). The initial update failed. I saved root using Voodoo, unrooted, and ran the update again. It failed the second time. I'm not inclined to go to much more trouble until I find out if the update is worth it and if I can maintain root... I'm not willing to give that up just yet
Definitely do not accept the update, even if it asks you every 5 mins
There has already been a reported brick and I know it has a new boot loader in it. So its safe to assume that Google wallet will not work lol. The best course of action is to wait for a beast dev to find a way to help.
Sent from my SCH-I605 using xda app-developers app
I will buy N2 off contract by next week from bestbuy because I have buy back on my Galaxy Nexus and I like Geek Squad protection.
Anyway, my GN is rooted and has CM10.1 installed. What are your advices about first things to do with the N2??
I am not asking about accessories or covers...etc I am asking about rooting access, unlocking bootloader and OTA updates. Usually when I get new device, I like to use it as it comes from the manufacture for about couple of weeks. Then, I would do root, unlock bootloader, install recovery and try different ROMs for fun, but not a lot. Is there anyway to reject the OTA update permanent even though I don't have root on N2? So whenever I decide to install ROMs, I can do it. I hate to be unable to have unlock bootloader and root forever because of stupid update
Do not let the store update it. You turn it on, don't let them. Reject the update. Get it home and root it and freeze sdm 1.0
As long as the update hasn't been applied, rooting and unlocking the bootloader is a snap thanks to Adam Outler's process. Find that thread and follow the steps...there is even a video to walk you through it. 10 minutes and you will have TWRP custom recovery and can flash ROMs. For Verizon there are two primary daily drivers out there, Beans and clean. Both are touchwiz based so the s-pen works. There are some aosp roms out there in alpha, but I don't think s-pen works with them.
Sent from my SCH-I605 using Tapatalk 2
Yea I should have been me clear. As long as the update doesn't hit this phone is wide open.
TonikJDK said:
Do not let the store update it. You turn it on, don't let them. Reject the update. Get it home and root it and freeze sdm 1.0
Click to expand...
Click to collapse
Can I just root it to freeze sdm 1.0 without unlock the bootloader? so that I unlock whenever I want to try different roms.
I guess this is more of a question then anything but any chance the radio update (that came with the new bootloader) will be required for continue functioning of the phone on verizon network? I.e, can you avoid updating hte radio indefinitely or do you have to manually apply that portion of the update ?
bassil2022 said:
Can I just root it to freeze sdm 1.0 without unlock the bootloader? so that I unlock whenever I want to try different roms.
Click to expand...
Click to collapse
Yes
TonikJDK said:
Yes
Click to expand...
Click to collapse
Thanks
I just found the one click root called ExynosAbuse APK on xda. I am thinking to do it and then freeze sdm 1.0 in order to stop the update coming to my phone. Then, I will unlock the bootloader and try different roms whenever I get board with stock.
Yes
Just don't use that app to 'fix' the exploit. That seems to be causing people issues. The are two options in that app....root... And patch the exploit. Don't patch the exploit., just root it.
Bottom line is as long as you freeze sdm the worst you will have to do is flash back to stock. Which will be no problem since you didn't take the update.
Please post Questions in Q&A'
Thread moved
Friendly Neighborhood Moderator
I just received my Note 2 yesterday.. What is the release number for the new upgrade?
When the Samsung Galaxy Note 2 came out on Verizon I got it immediately and obtained root with odin, I think, it's been a while... Anyhow, a few months back the handset began downloading the OTA from Verizon, but it would never install, it would just fail every time. But now, because the OTA is trying to install, that stupid reminder pops up every single day (I always reset the time for the middle of the night so I dont have to deal with it during the day). That doesn't fix the problem, it just prolongs what really needs to be done, To get rid of it I think, I'm not 100% tho, but I think I would have to unroot, go back to stock, except the OTA, and then root again.
I am running with:
Android version 4.1.1
Build number JRO03C.I605VRALJB
Baseband version is I605VRALJB
I never unlocked the bootloader...
Based on that information, what would you say I should do 1st?
I read a lot of guides on this forum but it seems like everyone is rooted on newer versions than me. I don't want to screw things up so I thought I would ask the pros first.
Thanks for whatever help you can offer...
I would unlock, then Judy flash one of the zips of the new ota. Or if you're happy where you're at freeze the sdm app and the popup will go away
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
I would unlock, then Judy flash one of the zips of the new ota. Or if you're happy where you're at freeze the sdm app and the popup will go away
Click to expand...
Click to collapse
Sounds easy but it fails when I try and install the pit and bootloader...
If I am already rooted can I skip to casual?
It's because of these type of issues that I thought that going back to stock and re-rooting would be best, but to do that seems confusing and I don't know where to begin
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.