Related
Just got prompted for a new update here is the link
https://android.clients.google.com/packages/incrediblec/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip
Instructions?
if you want to install this you just downlaod it put it on the root of your sd card, than rename it to update.zip than rebbot to rcovery than select apply update.zip.
Im not saying its ok to install this, as for me i am going to wait for a bot till i can look into more.
Mirror Here
Anybody without a corp account try flashing this yet?
i flashed it today and I do NOT have the CorpEmail account. I really hope this doesn't stop me from getting root.
Gimpeh said:
Anybody without a corp account try flashing this yet?
Click to expand...
Click to collapse
i have, no differences at all. battery life will tell in a day or two
So are we safe letting update go thru? Or should we hold off if we want root?
I wouldn't flash it yet. It contains a recovery image and I don't know if anyone knows for certain what's different about the image.
Would this have the correct test keys?
I flashed. Not noticing anything unexpected. Im getting my incredible replaced anyway. Sounds like I'm listening to people talk underwater.
I doubt you'd notice anything different; I'm just afraid that they've closed a useful hole.
Now if this thing would just stop asking me every 20-30 minutes ... grrrr.
The update fixes the email client for business users.
The meat of the update they don't tell you about, however, is there is a new recovery image in the updater. So yeah, maybe a hole was closed.
I held down volume down button and hit power, booted into the prompt, selected "recovery mode," and all I got was a red triangle and exclamation point.
I downloaded the zip, renamed it update.zip, and put it on /sdcard using Astro.
Am I doing something wrong?
I have the exact same problem.
dont do it
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
This whole subject was coverd in another thread.
http://forum.xda-developers.com/showthread.php?t=770091
swindelljd said:
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
Click to expand...
Click to collapse
read the other thread, you need to update to 1.22.605.2 first, easy and does not lose date.
Root and OTA
I have rooted with unrevoked 3.1 but still have stock 2.1. Do I need to unroot to install the OTA or will the OTA still be pushed to my phone while I am still rooted?
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
Call T-Mobile customer service and verify with them that the IMEI number they have in your account is the correct one. This is the number one reason for not getting the update. I had a phone for over a month and they never changed the IMIE # until I called. The IMEI is on your box or under your battery.
Please post questions in the Q&A section.
remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading This was on the same page you posted.... have you by chance read it?
I'd recomend using the force method...I spent almost three weeks waiting on it after being put on a "push list", verifying IMEI, and other things. Some phones "won't update" for whatever reason and they will eventually tell you to swap it. I did the manual update from the thread linked above without issue after T-Mo was unable to resolve my issue and I wasn't willing to swap for a potential refurb after having to pay full $450 retail price on the phone.
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
remijenkins said:
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
Click to expand...
Click to collapse
THE update is in the post... if you want to try and copy it to every folder on your phone fine... try it... but it is in that post
and if you want you could turn s-off to flash it then turn s-on when you're done... and you won't be rooted after the update applies so you won't have to unroot
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
remijenkins said:
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
Click to expand...
Click to collapse
there is more than one file posted there... The one named "PD15IMG.zip" is part of the update. It replaces the kernel and some other system files, but does not include the patches from the update, which is why wifi breaks. The one labeled The OTA is the full OTA pulled from a phone and the filename is "update.zip" I could not get the full update to flash with S-ON because it has to do some commands on the system to let it know it's going to flash becuase the phone temporarily disables the write through in place... (not sure if i explained that right). My solution is to flash the partial update which gets your kernel up to date then patch the kernel (turning s-off) and then flashing the entire update. If you're really against root you can undo all the root stuff and S-Off after the update hits... but what's wrong with root? You should still get new updates if you're still running stock, but are rooted. BUT, if you uninstall programs the updates will most likely not take (I recommend a nandroid be made before removing things so you can flash back to it get the update, make a new nandroid, then reremove software.)
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
remijenkins said:
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
Click to expand...
Click to collapse
Why the aversion to rooting? it's really not that hard and there are at least 4 or 5 of us in irc that will walk you through it
Rooting is nasty
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Flash PD15IMG-->temporary root-->permanent root (lot of jibberish)-->flash rest of update-->unroot
This is an intimidating process which is nowhere given in simple and complete steps but yet is often described as "simple" or "took minutes." Maybe for some, but the "simple" suckers in a lot of people who stumble along the way.
As I did; all I wanted was an unrooted phone with 2.2.1 and I had given TMo a couple of weeks to do it. A few hours into the process and a few steps beyond trashing WiFi I realized I didn't want a rooted phone and decided either to pay somebody who knows a lot more about this subject than I do to fix it or, preferably to convince TMo to give me a new one. So I went to sleep.
And guess what? At 6AM TMo said they wanted to do a firmware update, to which I agreed, and the legit OTA over-rode that damned PD15IMG and cajoled my WiFi back to life. And as far as I know Tmo doesn't have my IMEI either, because they say on their site they don't know what kind of phone I have.
And none of that snarky "if you don't know what we're talking about you shouldn't be here," either. If she didn't know she could get pregnant from it she shouldn't have done it. The whole rooting business is nasty: there are no simple comprehensive directions, there are too many ROMs and there is too little honest description of where they fail.
It would be nice also if Google would save up its incremental improvements and let them loose at longer intervals, as Apple does, to reduce the frustration of those interested in Being First. It would also be nice if the Google open system had required carriers to be able to absorb the latest updates within a fixed time, regardless of whatever crud they lay over the basic Android. The software may be "open" as far as Google and Tmo are concerned, but between TMo and me the relationship is different.
ecdy said:
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Click to expand...
Click to collapse
I'm sorry you had problems, but when doing anything that has a set of instructions it is wise to read the entire thing before starting. This will ensure you are fully prepared instead of lost in the sauce halfway through... Piss Poor Planning leads to Piss Poor Performance.
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".
Hi All,
My Bell Atrix was rooted but not BL unlocked when I finally got tired of the pop up message wanting to update to the latest firmware and decided to let it update. I had checked a while back and I thought people were having no problem updating even though rooted.
If I remove and replace the battery the phone will boot up completely but then immediately re-boots before I can do anything and on the reboot it goes to the Failed to boot 2, Starting RSD mode screen and stays there.
Because this phone was not unlocked I'm not sure how to proceed. Can I use RSD lite to recover and if so, what files should I be looking to write.
I don't mind ending up with a BL unlocked phone as I had been intending to do that eventually, but just hadn't gotten around to it yet.
As far as what version I was at, the phone took a big update a month or two ago, and after a while wanted to do another update (teh latest I assume). I had downloaded it (wasn't very big) and was only getting around to letting it install now when this happened.
Please, need some help quick here!
Regarding what rev I was at, I believe I was at 4.5.91 updating to 4.5.141...if this make sense for Bell.
Hi Again,
From further reading, I believe I was trying to update to this:
System Version
45.21.MB860.BellMobility.en.ca
(previous: 45.2.17.MB860.BellMobility.en.ca)
Android version
2.3.6
(previous: 2.3.4)
Webtop Version
WT-1.2.0-167-BELL
(previous: WT-1.2.0-135_BELL)
Kernel version
2.6.32.9
[email protected] #2
(previous: 2.6.32.9-00002-gd5bf03a
[email protected] #2)
Build number
4.5.2A-51_OLL-17.8
(previous:4.5.2A-51_OLL-17)
Sorry for the confusion, but I obviously can't use phone to see where I was at and where I was going. Basically, it was the latest Bell update excluding ICS, supposively that is available now?
Surely someone can toss me a bone on this one?
Got the same issue but used rsd lite and working now ..
http://forum.xda-developers.com/showthread.php?t=1490283
This link is for AT&T is it not? I think I need a specific file to load with RSD or fastboot to fix the softbrick created when OTA ing from Bell 234 to 236.
I assume you were AT&T bobby2nag?
Try this http://forum.xda-developers.com/showthread.php?t=1302423
Sent from my MB860 using Tapatalk
I am on the same boat, i am on AT&T i was rooted, and i hit the update button =(
Got it to work thank to you ! =)
Followed this up until proper recovery section which i did not have to do.
This worked for me also. Seemed just the process of unlocking the bootloader fixed things. I needed to unlock anyway, so that was good, however I believe the more appropriate fix would have been this:
http://forum.xda-developers.com/showthread.php?t=1501454
All good in the end! Thanks much!
Telcel MEXICO
Hi i was so stupid i didnt make a backup, i rooted my phone then from ROM Manager i tried to install ClockWor*#*$$# and then when it was finished the phone restarted and FAILED TO BOOT 2 and now i dunno what to do, like i said im from mexico telcel
Quinton99 said:
This link is for AT&T is it not? I think I need a specific file to load with RSD or fastboot to fix the softbrick created when OTA ing from Bell 234 to 236.
I assume you were AT&T bobby2nag?
Click to expand...
Click to collapse
Yes mine is at&t .
Finally yours Atrix is back .
Telco Mexico - clearing the caches might help, up to you to decide
Have a look here: http://forum.xda-developers.com/showthread.php?t=1501454
You never said if you were in a boot loop or not, upon battery pull/insert does it boot up and then reboot immediately and bring you to Failed to boot 2? If so, I would try the caches myselp, JMHO!
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.