BEFORE you start flaming, I know this is an EVO rom, but these are Incredible-related issues. And I don't have enough posts in the general forums to be allowed to post in Development.
Now:
After installing it on my Inc(by installing it then using the patch made by IncDoes), I completed inital setup. After, the phone gave me the OTA update notice (for a Verizon update), and it WILL NOT GO AWAY. I know that it either will not install (due to me running a EVO rom), or, if it does, it will bork the rom. Is there a way to permanently disable this? The only method I've heard of (changing otacerts.zip to .bak), justs starts a loop. The image downloads, checks, finds it does not match certs, and restarts download. Plus the name returns upon reboot.
P.S: Anyone else using the Evo flashover patch (using a SENSE rom) and having these issues?
Thanks in advance.
========
Posted from my IncredEVO
You can change your build.prop to reflect a newer update. Idk the exact changes off the top if my head and I'm on my phone but that's gotta be a decent starting point.
Sent from my Incredible using XDA App
Gahh Its Lee said:
You can change your build.prop to reflect a newer update. Idk the exact changes off the top if my head and I'm on my phone but that's gotta be a decent starting point.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Thanks man. Will try this in morning. Brain says droid, body says sleep.
If you want message me and ill get you the build number I have on my phone since I have the latest update.
Sent from my Incredible using XDA App
Related
Yesterday 1/26/2011 Verizon pushed an update on my HTC Incredible. I don't know what was this upgrade about (it wasn't Android 2.3) but now my device keep rebooting 5 times per day. All(!) marketplace application are crashing and required to be uninstalled and re-installed again in order to run. WTF? Anybody got updates pushed recently (or I'm a verizon's guineia pig?).
I don't know if I got the update or not but I having the same problem...
Sent from my ADR6300 using XDA App
Did you try doing a factory reset?
There's an update?
I got it too but I clicked too damn fast to see what it was.
Can you tell us what build number your phone is reporting? You can find this under settings/about phone/software....
Sent from my ADR6300 using XDA App
I never saw anything about an update, but my phone also started rebooting randomly today. Running Skyraider 3.5
I have GRH78C running CM7. I havent had any problems though
r3dlined said:
I got it too but I clicked too damn fast to see what it was.
Click to expand...
Click to collapse
r3dlined said:
I have GRH78C running CM7. I havent had any problems though
Click to expand...
Click to collapse
How did you get the update if you are running CM7? I don't think it's possible for you to have gotten one...
g00s3y said:
How did you get the update if you are running CM7? I don't think it's possible for you to have gotten one...
Click to expand...
Click to collapse
Was before I rooted and loaded rom.
if you're running cm7 that update shouldn't affect you at all since you already flashed something over it
if ur rooted and have a custom rom loaded u should really think about blocking OTA's. Theres a guide for it in this forum. u have to change the name of a file in system/etc/security
INC. SR3.5, Lou #9, 40gb, 1800mah
If my DINC is flashed to metropcs. I shouldnt get this update right?
I called Verizon customer support and ask them what type of update was it. Fisrt they confirmed that they pushed an update, second they told me that the update was containing multiple improvements for system applications mail, gmail, media player, etc. They suggested to do factory reset to device. So after factory reset and re-install of market apps, I still have my DINC self-rebooting at least once per day. Usually when I browsing internet. After update my Build number is 3.26.605.1 CL264707 (release-keys). Kernel Version 2.6.32.17-g9a2fc16
Yeah that build has been out for months now. As recommend in the previous replies you should disable ota updates to stop this from happening. I have not had this problem but then again I flashed the lastest ruu which is the same build as your update. I then went to other custom roms which may explain why I didn't get any ota's lately. I'm currently rocking out on miui 1.1.28
Try running the ruu and see if that fixes the reboots.
Sent from my ADR6300 using XDA App
In all my roming madness I never did block the OTA's Off I go......
Hey, I'm sorry I'm a noob, but I was wondering, I'm on the Virtuous 3.2 ROM which is pretty much like the stock ROM, minus the bloatware, buy has other features like battery percentage on the notification battery icon and other few tweeks. I got a notification saying that I was verified for the Android 2.3.4 Gingerbread update. Since I'm not on my stock sense ROM, would it be alright to just go ahead and install it or just manually install it?
I am on the skyraider 4.3, which I love. I woke up and saw the same notification, I believe that not update right now or it might brick your Di, can somebody help us? Thanks.
Sent from my ADR6300 using XDA App
I too received the notice to update. I am rooted with s-off bit still on the stock Rom. I don't want to lose root or s-off so I am going to wait a bit.
I think you can accept the OTA update and re-root but not 100% sure.
I want to start flashing roms but I need a bigger SD card first.
Sent from my rooted HTC Incredible using XDA App
I'm pretty sure the s-off part is not going to hurt anything, but if you are rooted and have a different recovery the OTA will not work. My suggestion is, even tho its annoying resist the urge to do the OTA until someone can root it, and make it flashable with CWM.
So i recently broke my original Incredible but got a basically unused one from a friend. It had stock 2.2 on it, so i manually upgraded to 2.3 with the previous gingerbread update verizon released, but then pulled. So i never rooted or S-off'd this phone. This might seem like an obvious answer, but should I, or even can I perform the OTA update?
I think there is someone who already made a flashable version of the OTA update, but its for root users only and it has to be done through CWM
Sent from my ADR6300 using xda premium
I've been on the stock ROM since I got the phone, and I'll probably just flash the OTA Rom once I get some clarification on the process
Is there a way to make the OTA update nag screen go away? I'm on skyraider 4.3, I'd rather just wait for 5.0.
@cpuspeed I'm getting there same problem. Hopefully, some of the ROM developers will update. I actually want a ROM based off the OTA release so I can keep on using my TV out cable lol
Sent from my ADR6300 using xda premium
Here's a link to it, but I'm gonna wait because I wanna do more research on it.
http://www.droid-life.com/2011/05/19/download-android-2-3-3-gingerbread-for-droid-incredible/
Sent from my ADR6300 using xda premium
Is there a way to force the nag/ notification to appear? I've been checking for it all morning
You can force your phone to check for an update by opening the phone screen (like you're going to make a call) and typing the following:
*#*#checkin#*#*
Don't spell out checkin in letters, those are simply the numbers on the keypad that you need to press. You should receive a notification that the checkin succeeded. Now you can go to menu>settings>about phone>system updates and see if it shows up. This doesn't guarantee that it'll immediately find the update, but it does force the phone to check for one.
But is there any way to get rid off the nagging message "there an update ready for the phone, install now or later?"
Sent from my ADR6300 using XDA App
joanchoma said:
But is there any way to get rid off the nagging message "there an update ready for the phone, install now or later?"
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not that I'm aware of. I'm running Skyraider 4.3 and am encountering the same message. Rather annoying.
what if it says 'checkin failed'? Do I need to be on 3g for the checkin to work?
edit: Ok I switched to 3g and it said 'checkin succeeded', but still shows no update when I go to settings, about, system updates. Guess I'll have to wait.
thank you though.
to get rid of the nag screen delete or rename OTAcets.zip in /system/ect/security, I just renamed to OTAcets.zip.bak.
use root explorer or ghost commander w/busybox to edit root files.
reboot for the nag screen to go away. go to menu>settings>about phone>system updates if you want to update in the future or delete the file in /cache directory if you know you don't ever want to.
give thanks if this was helpful.
silly question I guess, but do I need to be on 3g in order for the update notification to show up? I work from home am connected to wifi 24/7. I rarely put my phone on 3g since it eats battery on 3g. I will keep it on 3g though for next few days if necessary.
veroson said:
silly question I guess, but do I need to be on 3g in order for the update notification to show up? I work from home am connected to wifi 24/7. I rarely put my phone on 3g since it eats battery on 3g. I will keep it on 3g though for next few days if necessary.
Click to expand...
Click to collapse
Nope, I was on WiFi only yesterday and it showed up all by itself in the evening. I'm also on Pagepluscellular, so you don't even have to be directly subscribed with verizon. Also don't have to have stock rom as I'm rooted, s-off and using custom rom (skyraider 4.3).
@cpuspeed, the method didn't work. Is there any way? Also there is another file in the same directory *.bks
Sent from my ADR6300 using XDA App
you do need to reboot after renaming.
an alternative is http://forum.xda-developers.com/showpost.php?p=17372850&postcount=638
Running TemNocturnals newest rom and ran into two problems. I kept getting annoying popups from the device saying there are 'system updates', to which I finally said install. It downloaded, then on reboot got the triangle, so power cycle again and boots fine and that message stopped. But the 2 things that I find are;
1. GPS when using in maps/navigation. The phone get's extremely hot and it takes a good amount of time to connect, then dropping on and off. In the older versions it did work so I know it's not a signal problem, but thats 1.
2. When I click the menu/settings/ROM Updator, I get a black screen, it sits there for a few minutes, finally getting an "Update Me has stopped". I am running Mijjz Blend ICS FF18 v16.6.5 which I think is the newest, but wondering if was the system update that did that as it did work!
Tnx
System update was from sprint not the goodness. There is a patch to block it in the updater.
Did you update update me? I say reflash the ROM.
Why didn't you post in the thread?
Sent from my SPH-D710 using xda premium
fryingpan0613 said:
System update was from sprint not the goodness. There is a patch to block it in the updater.
Did you update update me? I say reflash the ROM.
Why didn't you post in the thread?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yea the system update was from Sprint and I guess I didn't install the patch. I remember starting at like .2 and did the few upgrades via the ROM updater which was nice and slick. As for why didn't I post in the thread, good question! I made a mistake of posting a Q in the dev section a while back and started to twich after being flamed, so thought just ask in the Q&A
I have the .5 update as well as the others, so will give that a shot...
Tnx
xlancealotx said:
Yea the system update was from Sprint and I guess I didn't install the patch. I remember starting at like .2 and did the few upgrades via the ROM updater which was nice and slick. As for why didn't I post in the thread, good question! I made a mistake of posting a Q in the dev section a while back and started to twich after being flamed, so thought just ask in the Q&A
I have the .5 update as well as the others, so will give that a shot...
Tnx
Click to expand...
Click to collapse
You must have asked something that had been answered a, million times to get that response in the thread.
The ota block is under bug fixes.
Sent from my SPH-D710 using xda premium
Ok. I am really upset with Tmo for blocking Wallet. I used it ALL THE TIME on my Nexus S on AT&T and I LOVED it. I've been trying to get it installed since October when I bought the phone and I cannot for the life of me get it to work. Everything I try fails or screws up the phone and I have to re-flash, so I eventually just said screw it and went to AOKP because I felt like trying something new. My friend said that I would be able to just install wallet once I did, but that is not the case. the install fails when using an apk, wallet is hidden in the market, and once when I got it installed it says "not available on your device/carrier blah blah blah" and quits. So, what I want is a solution. I need to know how to make this work because I am starting to get really upset. No solutions I can find work, nothing I've tried is successful... I might just be doing it wrong or missing something but I am determined to get it to work. NFC is working fine, I used it several times already.
Phone info:
Model: SGH-T999
Android Version: 4.1.2
Baseband: T999UVDLJA
Kernel: 3.0.48-cyanogenmod-faux123-att-tmo-00041-ga2c7267
AOKP Version: aokp_d2tmo_jb_milestone1
Build: aokp_d2tmo_userdebug 4.1.2 JZ054K eng.sethyx.20121029.025840 test-keys
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Pennycake said:
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Click to expand...
Click to collapse
I tried that the first time and it caused a failure to boot. second time, it was a program that was supposed to do it for me - same result.
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
up until now I was using touchwiz. I screwed up the phone both times while using touchwiz. Now, I'm on AOKP and cannot find anything that works for that - everything seems like it's for touchwiz. What I tried was flashing wallet now on aokp, and it didn't harm the phone but the program will not work. If I load it, it just says "Unfortunately, Google Wallet is not yet available for your device or mobile network." and I want to know how to get around that on aokp, ignore touchwiz, I was just mentioning that because I ditched it in part due to the problems it had with wallet.
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Pennycake said:
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok ok, I think I understand you now. You still have to mod build.prop even on aokp? just don't have to do all that other stuff that you do have to do for touchwiz?
osmosizzz said:
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2044362&highlight=wallet This thread?
I was using this exact app that it screwed up my touchwiz last time, and now it does not show an option for AOKP, just AOSP. Will the AOSP work?
Ok seriously. I didn't even run the app this time I just opened it and it screwed up my rom! God, why is this so infuriating! If someone had told me I would have to go through all this bull**** to get my stupid phone to work as well as my old, slow nexus s I would never have upgraded! BRB, time to reflash aokp.
*seeths with rage*
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
IF I'm not mistaken aokp is rooted by default. Anyways, I'm in the process of reinstalling it... again.
Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
used an app from the market to edit my build.prop and it works perfectly now. Thanks!
Ok so I can't post a question in the Rom Thread it will let me ask it here hopfully someone can answer. When I was using 3.5 it would tell me a update I had to install from Sprint no matter if I installed it or not it kept coming back a couple of days later again. If I update to 5.0 will that update finally be gone or is there something eles I can do to stop it. Thanks
All you need to do is accept the update, it's going to fail then just reboot the phone and the update prompt should stop. I don't think it goes away until you accept it regardless of the ROM. Hope that helps!
Sent from my SPH-L900 using Tapatalk 4 Beta
blacksmith_84 said:
All you need to do is accept the update, it's going to fail then just reboot the phone and the update prompt should stop. I don't think it goes away until you accept it regardless of the ROM. Hope that helps!
Sent from my SPH-L900 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah I did that before and maybe a week later it would return. That is why I removed that rom but it was the best I used. I would really love to go back especially if that is fixed
Man I never had it pop up again after pushing it through once sorry man...I feel your pain not being able to ask in the devs thread...just keep reading fellow noob!
Sent from my SPH-L900 using xda app-developers app
I found the solution somewhere in the many pages of the thread for the Mack's Rom. It involved going into the build.prop file and changing something I believe. After I made the changes the update notification stopped and hasn't come back since. Hope this helps point you in the right direction.
red23wolf said:
Yeah I did that before and maybe a week later it would return. That is why I removed that rom but it was the best I used. I would really love to go back especially if that is fixed
Click to expand...
Click to collapse
Go to root folder then navigate down to system click it then open up etc then security. In that folder you will find a file called otacerts.zip rename that file to otacerts.zip.bak reboot and your problem should go away. Try to use Root Explorer app. Thats what I use and never had it come back again.
Android...A New Digital Revolution Of Incredible Developers...