I'm s-off with a custom rom installed. I ran the zip to remove the OTA from this thread, but it did not work (the notification is still present). The update will allegedly force itself onto my phone today. Will this potentially brick my device? Any help would be greatly appreciated.
Use this one http://forum.xda-developers.com/showthread.php?t=2169022
Sent from my HTC6435LVW using Tapatalk 2
You can't take the ota if you have a custom recovery. So don't worry.
And if you are on viper, are you sure it's not the roms ota, as opposed to vzws
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
You can't take the ota if you have a custom recovery. So don't worry.
And if you are on viper, are you sure it's not the roms ota, as opposed to vzws
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
When you say "You can't", do you mean the process will cancel itself and not install anything when it tries to run?
I am on Viper, but I'm not sure if it's their OTA. The persistent notification just says "System update is available, Tap to download the system update". It occurs to me now that the verizon OTA may not even show up outside of the stock ROM (though I'm not sure how that works)
morph2k4 said:
When you say "You can't", do you mean the process will cancel itself and not install anything when it tries to run?
Click to expand...
Click to collapse
Yep, it'll download the ota and boot into recovery and just sit there.
morph2k4 said:
I am on Viper, but I'm not sure if it's their OTA. The persistent notification just says "System update is available, Tap to download the system update". It occurs to me now that the verizon OTA may not even show up outside of the stock ROM (though I'm not sure how that works)
Click to expand...
Click to collapse
tap the notification. There's a good chance it's the Viper ota if you haven't already installed. And the newest viper version has the Verizon ota stuff removed so you don't have to worry.
Sent from my HTC6435LVW using xda app-developers app
What version of Viper are you running? The latest is 1.1.3.
That's Viper's OTA. Verizon's just begins downloading, it doesn't ask you. Definitely accept it. If you're using TWRP recovery it'll install itself. If you're using ClockworkMod recovery you'll need to select the zip from the sdcard once it's downloaded and say yes when it asks to accept the unsigned zip.
If you're running an older version then you'll get a few in a row (as in after you update to 1.1.1, it'll tell you there's an upgrade to 1.1.2 available, etc.). They're only 16MB each and go pretty quick. DON'T WIPE, it's just an update.
Related
I'm running the stock ROM, rooted. When the next OTA drops, whether it be GB or just the removal of Free Hotspot, obviously I'm not going to be wanting it to auto-download/install. Aside from editing the build.prop file (which I never messed with) that I noticed mentioned in a thread from a few months ago, are there any options (other than flashing a different ROM) to stop the update from pushing to my TB? Will it disable OTA updates if I freeze Updater 2.2 with Titanium Backup?
Sent from my ADR6400L using XDA App
You won't automatically get the OTA and have it installed. You have to accept it and allow it to be downloaded and installed. But I believe the build.prop is where you have to make the change (device ID??) so that it won't get to you.
Most roms that have you flash standalone gapps packages use FOTAKill to kill ota updates.
Absolute_Zero said:
Most roms that have you flash standalone gapps packages use FOTAKill to kill ota updates.
Click to expand...
Click to collapse
I know, I said in the OP, other than flashing a different ROM.
Sent from my ADR6400L using XDA App
razor2006 said:
I know, I said in the OP, other than flashing a different ROM.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Flashing fotakill is not flashing a rom...but ok...didn't realize that was implied.
I was just sharing...but I will bite my tongue in the future.
My mistake, I thought you were implying that flashing a ROM would remedy the situation because they're already including FOTA Kill (which it would.) I didn't realize you were referring to just flashing FOTA Kill standalone. Is that even possible on a stock rooted TB?
Sent from my ADR6400L using XDA App
lol dont know if anyone saw or not but if your rooted the update wont come to you period so no need to worry about it. As long as you s off you wont be receiving OTA update unless u go and check for them ur self.
razor2006 said:
My mistake, I thought you were implying that flashing a ROM would remedy the situation because they're already including FOTA Kill (which it would.) I didn't realize you were referring to just flashing FOTA Kill standalone. Is that even possible on a stock rooted TB?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I'm not exactly sure the detail of it other than running a service that prevents ota. I would have thought it could be applied to stock assuming the same service is receiving the ota but I could be wrong. Ask Zinx.
sparta31 said:
lol dont know if anyone saw or not but if your rooted the update wont come to you period so no need to worry about it. As long as you s off you wont be receiving OTA update unless u go and check for them ur self.
Click to expand...
Click to collapse
As far as I was aware, you'd still get the notification and the update since the service is still checking. It will just fail when it tries to install. Perhaps I am wrong though.
sparta31 said:
lol dont know if anyone saw or not but if your rooted the update wont come to you period so no need to worry about it. As long as you s off you wont be receiving OTA update unless u go and check for them ur self.
Click to expand...
Click to collapse
Unless the TB is different than the DINC in that respect, that's not correct. On the DINC, if you're running the stock ROM, rooted or not, you'll still receive the OTA notifications. They won't install properly and/or brick the phone if you have S-OFF.
Hi All,
I still haven't seen the OTA update notice. If I go in manually to "check new" it says its searching for a couple seconds then just closes. Then when I check the status, all I see is:
Source:Verizon Wireless
Name:
Status:
Code: 0
Date:
Time:
Description:
I have only ever temp rooted. I haven't unlocked the bootloader, and I have only removed bloat using CleanTool 2.1.1
I have tried re-enabling all the bloat, rebooted to lose temp root, and removed superuser. I verified that I can't su in a terminal anymore, so root is definitely gone. As i said above, I have added all the bloat back as there are no slightly greyed out applications under "manage applications".
I have now just tried a full factory reset, wiping internal, and SD memory and still nothing.
I was wondering if anyone else has encountered this issue, or have any other suggestions?
My phone is completely stock and I haven't seen the OTA. I have not done the "check for update" thing as I keep hearing reports that the update breaks more than it fixes.
Egnix said:
My phone is completely stock and I haven't seen the OTA. I have not done the "check for update" thing as I keep hearing reports that the update breaks more than it fixes.
Click to expand...
Click to collapse
Same here. I kept checking for it until I started seeing all the comments about it breaking things. I think I'll wait for a bit instead.
murhaava1 said:
Hi All,
I still haven't seen the OTA update notice. If I go in manually to "check new" it says its searching for a couple seconds then just closes. Then when I check the status, all I see is:
Source:Verizon Wireless
Name:
Status:
Code: 0
Date:
Time:
Description:
I have only ever temp rooted. I haven't unlocked the bootloader, and I have only removed bloat using CleanTool 2.1.1
I have tried re-enabling all the bloat, rebooted to lose temp root, and removed superuser. I verified that I can't su in a terminal anymore, so root is definitely gone. As i said above, I have added all the bloat back as there are no slightly greyed out applications under "manage applications".
I have now just tried a full factory reset, wiping internal, and SD memory and still nothing.
I was wondering if anyone else has encountered this issue, or have any other suggestions?
Click to expand...
Click to collapse
I'm in the same boat =( I was wondering if there maybe was a way to flash it manually?
I've heard good things about it. Some people are saying that it improves signal and battery life drastically
SkizzMcNizz said:
Some people are saying that it improves signal and battery life drastically
Click to expand...
Click to collapse
And I've heard it reduces battery life drastically.
Egnix said:
And I've heard it reduces battery life drastically.
Click to expand...
Click to collapse
lol I wanna try cleanrom 1.6 but I don't want to do any of that mainver stuff to be able to flash the OTA. I guess I'll just stick with the pre mainver update roms for now
Egnix said:
And I've heard it reduces battery life drastically.
Click to expand...
Click to collapse
LOL, I've read that a few places myself.........
SkizzMcNizz said:
lol I wanna try cleanrom 1.6 but I don't want to do any of that mainver stuff to be able to flash the OTA. I guess I'll just stick with the pre mainver update roms for now
Click to expand...
Click to collapse
You don't need to do that Mainver stuff unless you already have a problem flashing updates via the PH98IMG.zip method.
if you have recovery, just download cons ota rom and flash it.
a.mcdear said:
You don't need to do that Mainver stuff unless you already have a problem flashing updates via the PH98IMG.zip method.
Click to expand...
Click to collapse
Right but if I want the update I won't be able to go to stock ruu
remmy5r said:
if you have recovery, just download cons ota rom and flash it.
Click to expand...
Click to collapse
Will that give me the radios and fixes?
Sent from my ADR6425LVW using XDA App
SkizzMcNizz said:
Will that give me the radios and fixes?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
By the way, the new RUU is up on vigor collection that is the new OTA one, so you can now flash that if you run into trouble later on once your Mainver is updated. Yes, Con's stock rooted rom will give you the new radios and fixes.
mjh68 said:
By the way, the new RUU is up on vigor collection that is the new OTA one, so you can now flash that if you run into trouble later on once your Mainver is updated. Yes, Con's stock rooted rom will give you the new radios and fixes.
Click to expand...
Click to collapse
I read the thread for that rom and it says they there is no firmware in it just a rooted rom based on the ota
Nevermind sorry I read the wrong thread
Sent from my ADR6425LVW using XDA App
What would you suggest? Using the ruu or his rom? Is there any benefits using one over the other? I'm thinking I might use the ruu from HTC so that I know they're won't be any problems but I'd rather not unlock and do all that.
Sent from my ADR6425LVW using XDA App
I'm gonna give the ruu a shot. I'll post my outcome
Sent from my 2.0GHz Quad Core G1
SkizzMcNizz said:
What would you suggest? Using the ruu or his rom? Is there any benefits using one over the other? I'm thinking I might use the ruu from HTC so that I know they're won't be any problems but I'd rather not unlock and do all that.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Whether you do RUU or con's ROM you still have to relock and then unlock the phone. Well you don't have to unlock it again unless you want root and custom ROM.
Here's a post I just made for someone else in case it helps:
feralicious said:
You can relock and then run the RUU to get you there and then accept the OTA and it should work. Then just unlock again and flash Amon Ra, and then either run stock or restore a nand or flash a new ROM. If you go with an older ROM without the new kernel and you want to use the new kernel you might need to update that. You can do that by following this thread:
http://forum.xda-developers.com/showthread.php?t=1467793
ATERNATIVE METHOD:
You can also use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
Check in Settings > About phone > Software info > More to see that you got all the new stuff.
Click to expand...
Click to collapse
I had a replacement phone sent to me and I received the ota but on my previous phone I wasn't able to get it yet
Sent from my ADR6425LVW using XDA App
Hmm, yeah I'm still waiting on the update. I figure with some of the bugs that people are reporting maybe it's for the best. But Ill give it maybe a week more before I ask a rep. Anyone else still waiting for an update when they are stock, temp rooted only?
murhaava1 said:
Hmm, yeah I'm still waiting on the update. I figure with some of the bugs that people are reporting maybe it's for the best. But Ill give it maybe a week more before I ask a rep. Anyone else still waiting for an update when they are stock, temp rooted only?
Click to expand...
Click to collapse
I had talked to a rep and he said that some phones may take longer to get the ota because they don't send it to every phone at once, or something like that
Sent from my ADR6425LVW using XDA App
SkizzMcNizz said:
I had talked to a rep and he said that some phones may take longer to get the ota because they don't send it to every phone at once, or something like that
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Well I called tech support last night and they are sending me a "certified like new" refurb. I am kindof nervous that the new phone might have any number of the problems in the post created by jdmba. It seems that the update should have gone to everybody by now and since my phone would just close the "check new" window without reporting if there was or wasn't an update they instantly said they would send me a new phone to resolve the problem with no charge. So for anyone else that hasn't gotten the update that wants it you might want to call verizon. When it gets in on friday I will check all the known issues to see if the new one has a worse problem and if i just want to unlock the old phones bootloader to manually install the updates that I want in the future.
Hey guys,
Is there a CWM Zip file out yet for the latest OTA update 4.5.145?
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
I posted one in a thread in the dev section a few days ago
http://forum.xda-developers.com/showthread.php?p=37763672
Sent from my MB860 using xda premium
Thanks, I searched but nothing came up before asking.
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
The OTA update zip will flash just fine thru CWM recovery.
I moved the zip from /cache to the internal sdcard /rom folder. Then ran opened ROM manager, Install from Sd Card, reboot into recovery.
Install went fine, CWM showed no errors, root and custom recovery remained untouched. When the phone reboots the first time the OTA update system will fuss that the update failed but About Phone shows you are updated 4.5.145.
See fixed my own stuff....
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
is 4.5.145 worth the install? I made the mistake of searching for updates, now i keep getting the reminder, so its either update or turn the reminder off. I just dont want to lose my root/unlock/webtop2sd
nicholetech said:
The OTA update zip will flash just fine thru CWM recovery.
I moved the zip from /cache to the internal sdcard /rom folder. Then ran opened ROM manager, Install from Sd Card, reboot into recovery.
Install went fine, CWM showed no errors, root and custom recovery remained untouched. When the phone reboots the first time the OTA update system will fuss that the update failed but About Phone shows you are updated 4.5.145.
See fixed my own stuff....
Sent from Nexxie 7. Own your devices don't let them own you.
Unlock, root, and hack...
Click to expand...
Click to collapse
uisgdlyast said:
is 4.5.145 worth the install? I made the mistake of searching for updates, now i keep getting the reminder, so its either update or turn the reminder off. I just dont want to lose my root/unlock/webtop2sd
Click to expand...
Click to collapse
If someone know how to stop the "spam" about the update, I will be very thankful.
Sent from my MB860 using xda app-developers app
uisgdlyast said:
is 4.5.145 worth the install? I made the mistake of searching for updates, now i keep getting the reminder, so its either update or turn the reminder off. I just dont want to lose my root/unlock/webtop2sd
Click to expand...
Click to collapse
The update changes the radio from 37p to 38p, giving a better signal, improved GPS with Maps (possibly overall GPS improvement), kernel version remains the same, however it appears to be a different build, and a few security updates. See images for status changes
Note: I did flash the 38p radio separately before cwm flashing the update. Upon update, go ahead and get into root explorer and delete the google preloaded apps that appear in play store so you can free up room in /system. Then update superuser binaries, and redownload google preloaded apps from play store.
Sent from my MB860 using xda app-developers app
Sent from my ADR6425LVW using xda app-developers app
I have an s-off'd custom rom with AmonRa recovery... offered update??
I just want to have it ignore the update.
Apparently, the software doesn't know the
recovery system is not stock ... so it tries
and fails. I wonder if there is a way to extract
the new fingerprint to trick the update process
into thinking the updates already applied?
Or is there a way to just suppress it all together?
Well I'm pretty much chicken so I'm basically stock but rooted but the ota update keeps falling. I tried unrooting so the update could work but it still failed. Not sure why...
Sent from my ADR6425LVW using xda app-developers app
Same here
I am having the same issue, as well. Rooted, debloated stock sense. Recovery is Amon-Ra.
So I read another thread that made it seem like I needed to re-lock the bootloader so I did that and now when I try to update it goes into the bootloader menu instead of starting the update. Do I need to unroot or do another step for this to work?
Sent from my ADR6425LVW using xda app-developers app
Did you debloat at all? I was stock+root (no debloating) and the install went fine.
Sent from my ADR6425LVW using xda premium
Well, when the ota update downloads and you press the button to update, the updater immediately begins to check the system utilizing a checksum system for any modification, such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure all system/apps are still there and untouched and all the binaries are still kosher. If it detects something is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using Root Explorer or something similar, go to system/app and add bak to the end of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
I have an s-off'd custom rom with AmonRa recovery... offered update??
wildstang83 said:
Well, when the ota update downloads and you press the button to update,
the updater immediately begins to check the system utilizing a checksum system for any modification,
such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure
all system/apps are still there and untouched and all the binaries are still kosher. If it detects something
is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the
update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using
Root Explorer or something similar, go to system/app and add bak to the en
d of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
Click to expand...
Click to collapse
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
fuzzynco said:
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
Click to expand...
Click to collapse
Not to be a PIA, but why freeze if you can just add bak to the end of the file name and you will achieve the same thing? If you ever want to go back you just delete the bak?
So for me it sounds like I need to get back to a stock recovery to be able to successfully perform the update?
Sent from my ADR6425LVW using xda app-developers app
Gee thanx for the help people...
Sent from my ADR6425LVW using xda app-developers app
You must be on the stock recovery to take an OTA. The stock recovery performs the update. So flash the stock recovery and then do the update or deal with no update.
Is there a way to flash the stock recovery without it wiping my phone?
Sent from my ADR6425LVW using xda app-developers app
Unless you're running a completely stock rom (with nothing removed), you won't be able to install the update anyway...
If you want to stop it from trying to come down, delete or rename /system/etc/security/otacerts.zip.
As for re-installing the stock recovery, you probably would need to RUU your phone unless it's s-off.
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
If you are on a stock rom you should be able to flash the stock recovery from fastboot without wiping the phone. Just find the recovery.IMG from the 605.12 ruu and flash it in fast boot to your phone. Then take the update and when complete flash your custom recovery in fast boot again and flash su zip.
Sent from my Nexus 7 using Tapatalk HD
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
A restore would not overwrite any of the firmware on the phone, just the rom.
As dottat pointed out, you can download the latest RUU, extract the recovery image from it and flash that via fastboot. I'd still back up your rom with your custom recovery first in case the rom pieces in the update bork something...
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Check androidpolice.com, it's over there, should be able to search for it...
Need a copy of the stock recovery
I am S-On and unlocked. I need to reflash the stock recovery to apply the OTA firmware update, right? I cannot find a copy of it anywhere. Anyone know where I can get this? I downloaded the stock RUU and tried to pull it out, but I cannot unzip the file. I would be grateful for any help. Thanks.
Okay I am deployed over seas. I am bone stock mk2. I would like to take the update to play around with it but I have my phone in global mode using a different sim card. Every time I check for update it says update unavailable at this time. Thanks for any help.
Sent from my SCH-I545 using xda app-developers app
You have to go to back to full stock mk2 to be able to update. If you want to keep root you can use the guide in the general section on how to keep root and update. The guide works for the leaked KitKat build we got, nc2, but I'm not sure if it works for the official nc5 update, you can check the thread for that.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Nopi45 said:
Okay I am deployed over seas. I am bone stock mk2. I would like to take the update to play around with it but I have my phone in global mode using a different sim card. Every time I check for update it says update unavailable at this time. Thanks for any help.
Click to expand...
Click to collapse
Since you're not on the Verizon network, you won't be offered the update via OTA. I'd wait until someone grabs the NC5 update
Since you're factory stock, you could install the OTA by downloading it to your internal SD card as an update.zip and booting into stock recovery to install it.
Note that you can't "play around" with it. You'll have NC5, no root, and very likely no way to go back.
k1mu said:
Since you're not on the Verizon network, you won't be offered the update via OTA. I'd wait until someone grabs the NC5 update
Since you're factory stock, you could install the OTA by downloading it to your internal SD card as an update.zip and booting into stock recovery to install it.
Note that you can't "play around" with it. You'll have NC5, no root, and very likely no way to go back.
Click to expand...
Click to collapse
I had an idea not being on the network may be the reason behind it. I will give going through the stock recovery a shot. Also, I am very sad to say this is my first phone I have not messed around with.
Sent from my SCH-I545 using xda app-developers app
Nopi45 said:
I had an idea not being on the network may be the reason behind it. I will give going through the stock recovery a shot. Also, I am very sad to say this is my first phone I have not messed around with.
Click to expand...
Click to collapse
The update comes from VZ over their network. If you're not on their network, the update servers aren't reachable.
Oh - another thing you can try is to use Kies to check for updates. I don't think that VZ has made the update available there yet, so have patience.
k1mu said:
The update comes from VZ over their network. If you're not on their network, the update servers aren't reachable.
Oh - another thing you can try is to use Kies to check for updates. I don't think that VZ has made the update available there yet, so have patience.
Click to expand...
Click to collapse
Thanks for the help! I will check out Kies too. I have nothing but time on my hands so patience comes easy.
Sent from my SCH-I545 using xda app-developers app