Database Users

A Second Update This Morning (6/28)?

OK, this is a little weird. I did the OTA update this morning and all was fine, but then just for grins, I did a manual check for updates again and goit new download!! This one is named OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip. What the heck is this one? I will go ahead and install and see what happens.
Edit: maybe it just downloaded the same update again...not sure....but it's asking if I want to install it. Should I and/or shouldn't the phone know if the update has already been applied and not ask this again?

if you can get them both on your computer run a md5 sum against the files.

nenn said:
if you can get them both on your computer run a md5 sum against the files.
Click to expand...
Click to collapse
The first OTA was removed after it installed (I think because I cant find it) and the one mentioned above has also disappeared after downloading but before I installed it). If anyone knows where these zip files are saved, let me know and I'll take a look.

did someone wake-and-bake this morning?

Update help
I have a rooted phone. The update downloads then when installing it starts to install, but stops and I get the screen with the red question mark. The phone then reboots and when I go check for the update its as if I never downloaded it.
Anyone have any thoughts?

DO NOT install the 2nd update. there are reposrts of users (on Android Forums) bricking their EVOs on the second update. just and FYI

Yeah some are saying it may brick your phone ... after updating and checking for a new update it states there is one.
Don't really have the time to try and see ... or else I wouldn't anyways ...

Rooted gingerbread keeps trying to download verizon update

Hey all,
I looked through the posts and wasn't able to find the answer so I am leaving this. Basically I upgraded my X from a rooted froyo to GB using the 2 files provided by P3Droid to go from the SBF froyo to GB rooted. It works great and I am having no freezing issues however the phone keeps trying to update and download the GB over the air update. I don't know how to stop this from happening or if I did something wrong. I have deleted a few of the Verizon apps that should stop any update from taking place anyway. I thank you in advance for your help.

I downloaded the "rooted gingerbread .596" from p3droid and my Droid X has never asked to update.

the only other thing I can think of is that I accidentally hit check for update on my phone but I don't think that it should have even found the gingerbread once I had installed it myself...

I just went into my settings and into "about phone". I also checked for a update and it says that it is up to date no update is necessary. So I have no idea what is going on. Only thing I can suggest is if it continues, is to SBF back to Froyo and reinstall p3Droid's rooted .596 again. Sorry I couldn't be more helpful.

You could let the update happen, it would go partially, fail and reboot and you're all set

Same problem with Sprint EVO 4g
I have also just installed "4.22.651.2 Rooted & De-Odexed" after accidentally dl the OTA update last week. I just hoped that installing the new ROM would eliminate the notifications to install the update but unfortunately it did not.
I did try to let it install so as to let it fail and rebooted, and the notification is still there.
Is there maybe a way to manually remove the update file?

Tecrekka said:
I have also just installed "4.22.651.2 Rooted & De-Odexed" after accidentally dl the OTA update last week. I just hoped that installing the new ROM would eliminate the notifications to install the update but unfortunately it did not.
I did try to let it install so as to let it fail and rebooted, and the notification is still there.
Is there maybe a way to manually remove the update file?
Click to expand...
Click to collapse
this is the Droid X sub-forum. You will get the proper help if you post in the Evo section.

Sorry I just didn't find anything even closely related to this issue here and thought it would be best to not start a new thread. Isn't this a software issue and therefore somewhat universal?

Tecrekka said:
Sorry I just didn't find anything even closely related to this issue here and thought it would be best to not start a new thread. Isn't this a software issue and therefore somewhat universal?
Click to expand...
Click to collapse
here a link to the thread for your 4.22.651.2 Rooted & De-Odexed rom in the EVO section... and there's discussion in there about your exact problem http://forum.xda-developers.com/showthread.php?t=1110733

Thank you very much!

I'm having the same problem. It comes and goes with no ability to clear. It always pops up after a reboot. It never actually downloads, at least that I've seen....
Does anyone know which package to freeze so the updater stops flagging?

Stop OTA Updates
Freeze the application called "Updater 2.3.3".

[How-To] Install OTA Update on after Root/Custom Recovery

*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.

jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.

trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.

Thank you for the info! Does sound like an awful lot of work though

jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.

I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.

shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.

jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english

Does sound like an awful lot of work though

greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.

How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium

I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.

trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...

With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.

sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.

Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!

I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.

jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app

deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.

I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?

OTA update fail?

I am running a newly stock, factory restored s4 running 4.2.2. 3 times now I download and attempt to install , but it keeps stopping, rebooting and saying the update failed. What gives?
Any alternate method to update?.

HeDsh0t said:
I am running a newly stock, factory restored s4 running 4.2.2. 3 times now I download and attempt to install , but it keeps stopping, rebooting and saying the update failed. What gives?
Any alternate method to update?.
Click to expand...
Click to collapse
I get the same thing with the wife's S4. I downloaded the update 3 times now in the last month. Each time it shows installed but when verifying the OS and number its the same. So, got on chat with an ATT tech. Seems there is another "hold" on the update, they contacted Samsung tech and the deal is this according to Samsung.
The update comes from Google as an Android update,its up to the carriers to approve the update. Att says it comes from Samsung and its there responsibility to do the update. So where does this go? The usual pass the buck so and so says this. ATT says its Samsung, Samsung says its Google, Google says its ATT. As for the update. Its there but it don't install because ATT stops it with another hold on it.

leesumm said:
I get the same thing with the wife's S4. I downloaded the update 3 times now in the last month. Each time it shows installed but when verifying the OS and number its the same. So, got on chat with an ATT tech. Seems there is another "hold" on the update, they contacted Samsung tech and the deal is this according to Samsung.
The update comes from Google as an Android update,its up to the carriers to approve the update. Att says it comes from Samsung and its there responsibility to do the update. So where does this go? The usual pass the buck so and so says this. ATT says its Samsung, Samsung says its Google, Google says its ATT. As for the update. Its there but it don't install because ATT stops it with another hold on it.
Click to expand...
Click to collapse
Really? Hmm, didn't know they stopped it again. Would I be able to side load it using abd? I heard that works. (I know very little about it, but read the thread here)

HeDsh0t said:
Really? Hmm, didn't know they stopped it again. Would I be able to side load it using abd? I heard that works. (I know very little about it, but read the thread here)
Click to expand...
Click to collapse
You can't load something that isn't there. I have yet to find an OTA update to load but keep looking. Att says it will put it out when it gets ready. Only other option you have is to root and go custom. Mine is rooted with TWRP recovery, but as of yet I don't have a custom rom. It's my wife's phone and she isn't into the techy things as I am so I have let it go and when it happens it happens on the GS4. The HTC one I have is all dolled up with unlocked bootloader, S-Off , TWRP, and converted to a GPE model then running a custom rom.

leesumm said:
You can't load something that isn't there. I have yet to find an OTA update to load but keep looking. Att says it will put it out when it gets ready. Only other option you have is to root and go custom. Mine is rooted with TWRP recovery, but as of yet I don't have a custom rom. It's my wife's phone and she isn't into the techy things as I am so I have let it go and when it happens it happens on the GS4. The HTC one I have is all dolled up with unlocked bootloader, S-Off , TWRP, and converted to a GPE model then running a custom rom.
Click to expand...
Click to collapse
Grab the file from post 694 in this thread http://forum.xda-developers.com/showthread.php?t=2498897&page=70, change it to .zip and then sideload using the instructions from this thread http://forum.xda-developers.com/showthread.php?t=2529759

dwanhala said:
Grab the file from post 694 in this thread http://forum.xda-developers.com/showthread.php?t=2498897&page=70, change it to .zip and then sideload using the instructions from this thread http://forum.xda-developers.com/showthread.php?t=2529759
Click to expand...
Click to collapse
I didn't know there was a download of the OTA anywhere. I have been googleing and looking on the XDA for it for a while and come up empty handed in all searches. Now my question , rather than go thru the ADB stuff would it be possible to just copy the file to a folder such as roms , downloads etc. on the internal SD then use TWRP (if installed) to flash the zip ?

leesumm said:
I didn't know there was a download of the OTA anywhere. I have been googleing and looking on the XDA for it for a while and come up empty handed in all searches. Now my question , rather than go thru the ADB stuff would it be possible to just copy the file to a folder such as roms , downloads etc. on the internal SD then use TWRP (if installed) to flash the zip ?
Click to expand...
Click to collapse
Some people have flashed it from stock recovery from their external sd card, but this does do a full wipe I believe, where the ADB sideload doesn't wipe. Haven't heard of anyone flashing it thru TWRP, you may want to find a version without the bootloaders so that you don't lose the rom flashing ability. I'd imagine that your on MDL?

dwanhala said:
Some people have flashed it from stock recovery from their external sd card, but this does do a full wipe I believe, where the ADB sideload doesn't wipe. Haven't heard of anyone flashing it thru TWRP, you may want to find a version without the bootloaders so that you don't lose the rom flashing ability. I'd imagine that your on MDL?
Click to expand...
Click to collapse
Yeh, I finished reading the posts then found out it wipes the card , sorry my bad . But still can't get it to sideload successfully keeps saying failed.

leesumm said:
Yeh, I finished reading the posts then found out it wipes the card , sorry my bad . But still can't get it to sideload successfully keeps saying failed.
Click to expand...
Click to collapse
You'll either have to Odin back to stock and do the update, or research the error codes and see what you can do from there.

dwanhala said:
You'll either have to Odin back to stock and do the update, or research the error codes and see what you can do from there.
Click to expand...
Click to collapse
Samsung and rooting is not one of my favorite phones. This is my wife's phone but I rooted it a long time ago , just never did any thing with it so I know very little about it. The sideload failed with no error codes, it wont install from anywhere. From what I am reading any way, I just maybe should leave it alone till ATT gets it together if they do and comes down with a good download. Even the tech on chat yesterday said they pulled the download because of issues but failed to know it was still up for a download.

OTA push

OK, I must have inadvertantly started OTA and got the must install / delay screen pop up. I froze the smaller update system app to rid the pop up, and removed the update.zip package.
So far 2 weeks of reboots and use age no OTA package installer pop ups.

Is that for your I467 model and are you blocking the KitKat update, or a different model?

On both types... I am not dissabling OTA, as I may want to install 4.4.2 later. Just keeping the blasted install update notice from popping up every so often. It does not effect downloads or app installs, just keeps the notice from being a pain in the arse.

Do you happen to still have the 4.4.2 update.zip file?
@muniz_ri is trying to help us get root on 4.4.2 but he needs the 4.4.2 update.zip file for the i467.
If you have the file would you be willing to post a link so we can download it and work on rooting it?

dandroid7 said:
Do you happen to still have the 4.4.2 update.zip file?
@muniz_ri is trying to help us get root on 4.4.2 but he needs the 4.4.2 update.zip file for the i467.
If you have the file would you be willing to post a link so we can download it and work on rooting it?
Click to expand...
Click to collapse
Not for the i467 as I never connected with AT&T, just rooted and unlocked to use Virgin UK. Though I froze the software update to mirror my GT-N5110 settings.

OK thanks for the response

dandroid7 said:
OK thanks for the response
Click to expand...
Click to collapse
Sent you a message

gooberdude said:
On both types... , just keeps the notice from being a pain in the arse.
Click to expand...
Click to collapse
I thought I had read somewhere that you had both models, it was a pain.
I just couldn't remember how I stopped my pop-up, thanks you.
Quote godzulu
If you have the file would you be willing to post a link so we can download it and work on rooting it?
I'm sure that I have yet to complete a download of the OTA for I467. For years I'd preferred a custom Rom or kernel vs a carrier update - with that being said, how can I Download it & then STOP the installation (i do not want the update without root) & next, locate the zip to get it to you?
I would already guess that you and others have already tried.
***********************
It looks like someone had passed the file along & maybe Da_G is attempting a a workaround, yea!

OK, I realized that I had changed the option in about device to set auto update. If you go into app manager, and clear cache and data in both software update apps, you will reset parameters for FOTA. The nice thing about doing so on the GT-N5110, is that you can select world ROMs. UK GB is what I use, as it has 13 channel WIfI already set.
If you choose automatic, you will get a notice and will ask to install once the download iscompleted. if you do it manually, it will download when you select download.... but you can cancel.
The Firmware is located in System/cache/update, and the fle is update.zip.
If you like to mess with a library of ROMs, you can download as many as you like after renaming and moving them to SD.
As for rooting... Saferoot.zip works fine. there are a few topics that have it downloadable. just search in the Note 8.0 general and Q&A sections.