For the past month or so I keep getting a message that my phone has a new system update available, but every time I push "Yes, update now" the phone says it will restart, and then a countdown from 10 begins. When it gets down to 0 nothing happens... does anyone know why my phone will not update? I have a rooted Incredible that's running:
2.2
2.15.00.07.28
2.6.32.15-gb7b01d1
[email protected] #1
3.21.605.1 CL231334 release-keys
3.21.605.1
Sounds odd, my suggestion would be trying to reboot it manually- but I'm assuming you've already tried that.
Of course.. you could do a backup of your apps and install a custom ROM on your phone and restore all your apps and data
Yeah, tried manual reboot but no luck. Does anyone know what the update is? Like I mentioned, it originally started about a month or so ago, and shows up about every two days or so...
Something to add, my wife has a totally stock incredible and the only difference I see between hers and mine is her Kernel version is 2.6.32.17-g9afc16 and mine is 2.6.32.15-gb7b01d1... and also her Build number shows 3.26.605.1 CL264707 and mine shows 3.21.605.1 CL234334.
I'm assuming hers already updated so does anyone know why mine won't update?
I thought you couldn't receive updates while rooted. Unless S-on with stock RUU.
Is your wife rooted too?
Sent from my ADR6300
That's correct Jesssiii, you cannot get OTA updates when the phone is rooted & not running the stock ROM.
No my wife's phone is not rooted, which is prob why she was able to update. I figured that it had something to do with the phone being rooted. How can I manually find this update? Is there a link on this site somewhere?
Related
hey
I have an orange phone which a while ago i flashed with a generic rom and rooted. because of this i was unable to install the OTA so i did a manual upgrade to this rom:
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
This installed fine (it seems), but as i am on orange, when i rebooted the phone it was network locked. I read that flashing an older radio solved this problem so i went and flashed this radio:
update-bravo-radio-32.30.00.28U_4.05.00.11-signed.zip
This now makes my phone boot and work fine with no lock, HOWEVER, the software version still says it is on 1.15.405.4 and not the updated version!!!!
I have tried testing one of the bugs that was fixed in the new ota (i sms'd myself from skype and it still says it was sent by a facebook contact) and so that fix clearly wasnt present and the upgrade just hasnt seemd to work. Can anyone shed any light on this? could it have anything to do with what is installed on my phone during step 1 of the root? the root package i am using is called r5-desire-root-alt
Thanks for anyone who can help on this
Rooting the phone puts the 1.15.405.4 ROM back on your device, if you want 1.21 you'll have to then buy an unlock code to free up the device...
There is an update ZIP in the ROM dev forum which updates the system but leaves the radio alone so might wanna try that...
thanks for this, but the only update i have been able to find in the dev forum is the one on this page:
http://forum.xda-developers.com/showthread.php?t=695667
but there is a note at the top saying they all contain radio updates
do you have a link to one without the radio update?
Didn't look hard did you??
http://forum.xda-developers.com/showthread.php?t=694564
thank you sooo much, this has finally sorted out my problem
I just did the root, nand, and radio
However I didn't know that I was going back to 2.1
What are the cons of 2.1 vs 2.2 and how long usually before there is an updated rooted 2.2?
Thanks
2.2 is out officially??? Where/how can I/we get it?
It just automatically downloaded when I got my phone yesterday. Now I'm wondering if I should go back and update and wait then re root later or just wait.
Are you sure you had 2.2? Where did you get your phone? What is your hardware version?
Positive I had it. I got it at walmart yesterday. As soon as I activated it downloaded like three updates.
I was using flash etc.
kikwear002 said:
Positive I had it. I got it at walmart yesterday. As soon as I activated it downloaded like three updates.
I was using flash etc.
Click to expand...
Click to collapse
Flash lite?
Flash works with 2.1 also (at least on the evo)
I'm not really sure. I just know it said 2.2 and not 2.1.
also my hardware is 2.2
I wish I would've known I would've backed up before rooting. I didn't see any reason since the phone was new with nothing on it.
I just checked and it said no updates available.
So in order to go back to stock all I have to do is reflash with the stock rom. Just throw it on sd and flash as normal?
kikwear002 said:
I'm not really sure. I just know it said 2.2 and not 2.1.
also my hardware is 2.2
I wish I would've known I would've backed up before rooting. I didn't see any reason since the phone was new with nothing on it.
I just checked and it said no updates available.
So in order to go back to stock all I have to do is reflash with the stock rom. Just throw it on sd and flash as normal?
Click to expand...
Click to collapse
Just flash RUU from your computer.
Settings > About > Hardware, your Hardware Version is 2.2, NOT 002 or 003?
no its 002 sorry running on two hours of sleep here.
Ok i'm going to try to go back to stock then upgrade.
at least I know I can root it again. maybe faster next time too.
well I unrooted and got some prl updates but no firmware
here goes
Take the battery out of the for about 5 sec then put the battery back in and go in to recovery and try reflashing the rom that work for me
One of three things happened..
You are either have a nexus one and are in the wrong forum..
Are mistaken that you had 2.2 prior to root..
Or you're just trying to mess with everyone..
2.2 is not out in any way officially on any HTC phone, so you couldn't have had it. And no, you couldn't have been the only person in the country to have accidentally gotten it somehow.
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Hey Dude,
I figured I would get to you before the wolves do lol you'll probably get a better response to your questions in the "General" section. To answer you directly there is already rooted versions of this OTA such as (shameless plug) both my Roms Redemptive rEVOlution (Evo hybrid) and Redemption Rom.
OK. Thanks.
RuLEoF2 said:
OK. Thanks.
Click to expand...
Click to collapse
Not a problem enjoy Rom hunting.
RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
jrocket said:
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
Click to expand...
Click to collapse
you can edit the build prop to make it stop search the skyraider thread i think its in there.
ACD168 said:
you can edit the build prop to make it stop search the skyraider thread i think its in there.
Click to expand...
Click to collapse
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
jrocket said:
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
Click to expand...
Click to collapse
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
Like was posted previously, you'd be better off finding which ROM has the update and then just flash that, be sure to do a backup 1st and foremost in case you screw up, you can always flash back to what you had and start over.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Edit build.prop. Here is the configuration you'll need to change to stop the OTA updates. This will also help save your battery if it frequently tries to download on 3G.
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
Click to expand...
Click to collapse
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> http://solo.dc3.com/dinc/ (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
RuLEoF2 said:
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
The current Unrevoked3 (ver 3.21) does not work to root the Nov OTA, nor install a custom recovery. There were tweets about an update coming, but delays due to thanksgiving, finals, etc. I haven't seen an ETA posted yet.
joelcableguy said:
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Click to expand...
Click to collapse
thanks for the info. you're right, it didn't update, i'm still at 21. when i clicked update a window came up saying it was going to reboot, but it never did. must be due to change i had on the device.
KidJoe said:
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> LINK (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
Click to expand...
Click to collapse
thanks for that link - i'll try to go through that when i get a chance.
Rooted HTC EVO W/ S-OFF running Mikfroyo 4.4 smoothly until last night I wasnt sure if i was supposed to do this but I updated the PRL and FIRMWARE through settings>system updates on my evo. Boom.. lost my 3G icon and cant text or make calls.. getting error code 67 (check username or password) I went to my EPST settings and nothing seems to have changed.. all my info is still there. Any clue on what I can do?
Android Version: 2.2
Baseband Version: 2.15.00.11.19
Kernal Version:
2.6.32.17-gee557fd
[email protected] #15
Build number: MikFroYo v4.4
Software Number: 3.70.651.1
PRI Version: 1.90_003
PRL Version: 60674
RMACEVO427 said:
Rooted HTC EVO W/ S-OFF running Mikfroyo 4.4 smoothly until last night I wasnt sure if i was supposed to do this but I updated the PRL and FIRMWARE through settings>system updates on my evo. Boom.. lost my 3G icon and cant text or make calls.. getting error code 67 (check username or password) I went to my EPST settings and nothing seems to have changed.. all my info is still there. Any clue on what I can do?
Android Version: 2.2
Baseband Version: 2.15.00.11.19
Kernal Version:
2.6.32.17-gee557fd
[email protected] #15
Build number: MikFroYo v4.4
Software Number: 3.70.651.1
PRI Version: 1.90_003
PRL Version: 60674
Click to expand...
Click to collapse
Pretty sure a firmware update might have taken away your root. Boot into bootloader and make sure your still s-off?
That error code means you need to re-provision your phone. Call sprint from a different phone and tell them it needs to be re-provisioned and you'll be all set.
thats a tough one. Id hate to see you lose your stuff but have you tried flashing a stock ruu yet?
i run a stock sense rooted with clockwork. im not too familiar with the evo mods as i just got it; coming from a hero.
if it were me, id restore to stock. sorry i cant be of more help...ill keep looking as i have nothing else to do...
Biofall said:
That error code means you need to re-provision your phone. Call sprint from a different phone and tell them it needs to be re-provisioned and you'll be all set.
Click to expand...
Click to collapse
sounds perfect.
ive been having hiccups sending messages. perhaps i should call them and have them re-provision.
are you familiar if the provisioning could correct these issues? just curious, im not expecting you to have all the answers so no worries...thanks for the help
yea thats definitely sounds like all you need to do is provision your phone and actually there is probably a tutorial to refresh data somewhere in xda. Also if you are rooted and can get everything sprint can offer you and more right here why would you do an OTA... oh well like everyone has said call Sprint re-provision or look for a thread that shows how to do it but I doubt you need to unroot it..
Dial *2 and you can activate it yourself.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
From the home screen; menu, settings, updates, update profile. I get a FC when doing *2 because sprintzone is not installed.
Thank you guys for your help, just updating everyone that I did get this problem resolved!! I was getting "Error Code: 67". I called Sprint explained the issue, they had me take my battery out for 2 minutes. After that, Sprint had me power my phone back on and told me when I get to the home screen to enter: "Menu>Settings>System Updates>Update Profile". I asked them why this happened, when I updated my firmware/prl/profile and they replied "Its common on all of these devices and its considered an overload of data which simply crashes the system. If it happens again take your battery out for 2 minutes, power on, then update your profile through System Updates. Having the battery out for 2 minutes will reset your data and allows a smooth profile update(profile update=DATA Updated). They said its not really necessary to update ANY System settings as your provider will issue a notification asking whether you want to do the update when an update is needed because updates don't just come out like every month. Also if you experience your phone is running slow, acting funny, etc. This same method works for that too."
Also they told me sometimes its needed to call the service provider in cases like mine so they can manually disable incoming/outgoing data to my phone and wait for ME to ask their network for data permissions VIA "MENU>SETTINGS>SYSTEM UPDATES>UPDATE PROFILE".
Hope this helps anyone having the same issue, please note I did this with a fully rooted HTC Evo running MikFroYo v4.4 Rom
Android Version: 2.2
Baseband Version: 2.15.00.11.19
Kernal Version:
2.6.32.17-gee557fd
[email protected] #15
Build number: MikFroYo v4.4
Software Number: 3.70.651.1
PRI Version: 1.90_003
PRL Version: 60674
gpz1100 said:
From the home screen; menu, settings, updates, update profile. I get a FC when doing *2 because sprintzone is not installed.
Click to expand...
Click to collapse
When I was using CM's 6.1 Rom, That same thing happened to me. Im not sure what the reason for this is, but honestly I just flashed to MikFroYo v4.4 a week ago and it is BY FAR the BEST Rom I have used, It's Very fast.. I'd recommend switching to that and updating the radio's by simply wiping data and flashing the zip in recovery. No issues on his rom... I know its not because you dont have "Sprintzone" Installed because I dont have that nor any sprint apps on mine and have no problems with FC on system updates.
I'm having the same issue. I'm running CM7 and I called Sprint to help with the re-provisioning. I was following along until she had me enter the ##3282# code. She was expecting something to pop up so I could enter a code she gave me. Well, nothing popped up... It is obvious to me that CM7, and probably most non-Sprint ROMs, don't follow the same menu paths as Sprint does. I'm sure there is a way to go through the procedure Sprint was trying to perform with me, but it's not obvious what it is.
I'm sure someone can tell me what that procedure is... Anybody???
Thank you to everyone who tries to help,
Mike
Flash a Sense rom. Nandroid your CM first. Then the codes will work.
Thanks! This is working for me so far...
RMACEVO427 said:
Thank you guys for your help, just updating everyone that I did get this problem resolved!! I was getting "Error Code: 67". I called Sprint explained the issue, they had me take my battery out for 2 minutes. After that, Sprint had me power my phone back on and told me when I get to the home screen to enter: "Menu>Settings>System Updates>Update Profile". I asked them why this happened, when I updated my firmware/prl/profile and they replied "Its common on all of these devices and its considered an overload of data which simply crashes the system. If it happens again take your battery out for 2 minutes, power on, then update your profile through System Updates. Having the battery out for 2 minutes will reset your data and allows a smooth profile update(profile update=DATA Updated). They said its not really necessary to update ANY System settings as your provider will issue a notification asking whether you want to do the update when an update is needed because updates don't just come out like every month. Also if you experience your phone is running slow, acting funny, etc. This same method works for that too."
HTC Evo running MikFroYo v4.4 Rom
Android Version: 2.2
Baseband Version: 2.15.00.11.19
Kernal Version:
2.6.32.17-gee557fd
[email protected] #15
Build number: MikFroYo v4.4
Software Number: 3.70.651.1
PRI Version: 1.90_003
PRL Version: 60674
Click to expand...
Click to collapse
Thanks for the info! I followed your instructions, and data seems to be working nicely again. I'm running nearly the exact same package you mentioned, except my PRL version is 60680. Good lookin' out!
Possible fix I had same issue
ALl you have to do is update your profile from your phone usually using stock rom
Had 4.1.1 rooted with CWM. Phone downloaded a 600MB update file. Got some sort of error part way through. Flashed stock recovery back. Let phone download OTA update. Stopped half way through the flash and aborted. No error, rebooted before I could see one - just said that it was interrupted or something after rebooting. Go to check for updates and it says the phone is up to date, however about shows 4.1.1! Kernel though is showing SMP Preempt Nov 20 date so that's go to be something new.
I noticed on Kies it says 4.1.1 is the latest version! I know 4.3 had a lot of bugs initially. Is AT&T still chickening out on this for now and all the msgs I see about 4.3 OTA update are before AT&T stopped it? Or somet issue with my phone.
I'm about to just do back to CWM, move to CM11 nightly and roll the dice on having to deal with bugs and other funky stuff. But then stability is my #1 priority so maybe just stay on 4.1.1. Can't be right as I thought there was a 4.1.2 even?? (I had the update app frozen via TI so I never bothered with the OTA updates.)
*** shoots straight into your head ***
Dead, yet ?
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
jazee said:
Had 4.1.1 rooted with CWM. Phone downloaded a 600MB update file. Got some sort of error part way through. Flashed stock recovery back. Let phone download OTA update. Stopped half way through the flash and aborted. No error, rebooted before I could see one - just said that it was interrupted or something after rebooting. Go to check for updates and it says the phone is up to date, however about shows 4.1.1! Kernel though is showing SMP Preempt Nov 20 date so that's go to be something new.
I noticed on Kies it says 4.1.1 is the latest version! I know 4.3 had a lot of bugs initially. Is AT&T still chickening out on this for now and all the msgs I see about 4.3 OTA update are before AT&T stopped it? Or somet issue with my phone.
I'm about to just do back to CWM, move to CM11 nightly and roll the dice on having to deal with bugs and other funky stuff. But then stability is my #1 priority so maybe just stay on 4.1.1. Can't be right as I thought there was a 4.1.2 even?? (I had the update app frozen via TI so I never bothered with the OTA updates.)
Click to expand...
Click to collapse
jukiewalsh said:
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
Click to expand...
Click to collapse
Jazee, I read your posts on why you chose to try 4.3. I did what jukiewalsh recommends & have 4.3 as a stable DD.
This only works if your bootloader remains on 4.1.2 or less!
Posted some detail in these 2 posts:
http://forum.xda-developers.com/showthread.php?p=48303313#post48303313 #264
http://forum.xda-developers.com/showthread.php?p=48550720#post48550720 #875
jukiewalsh said:
There's a flashable zip of the official 4.3 update in the development thread. I would recommend the no knox prerooted version though because the other version is apparently "unrootable" right now.
Click to expand...
Click to collapse
I took a quick look and qasn't sure what thread you are referring to?
I'm guessing this one:
http://forum.xda-developers.com/showthread.php?t=2498233
But aside from having a pre-root pre-no knox version how does this one compare to this one?
http://forum.xda-developers.com/showthread.php?t=2387423
Are both of these buggy and that's why AT&T stopped pushing out the update?
jazee said:
I took a quick look and qasn't sure what thread you are referring to?
I'm guessing this one:
http://forum.xda-developers.com/showthread.php?t=2498233
But aside from having a pre-root pre-no knox version how does this one compare to this one?
http://forum.xda-developers.com/showthread.php?t=2387423
Are both of these buggy and that's why AT&T stopped pushing out the update?
Click to expand...
Click to collapse
I'm pretty sure that is the difference, that it's pre-rooted and insecure. As the second one's title says it's a "one way road". If you have any plans on rooting or installing a custom rom in the future I wouldn't do the second one because currently I think it's hard to root. The other one is essentially like flashing a custom rom so you can still switch between other ones or flash a kernel if you ever decide to. And I haven't tried the 4.3 TW yet so I can't attest to the bugginess