Related
Hi everyone!
I am getting messages on my Nexus One to install a 2 part update. The first prepares the Nexus One and the second installs the update.
I already installed a custom rom from here - and the build number is ERE36B with MCR2.0
I do not want to install the updates.
My question is - how do I stop the notifications to update?
I am searching both the Nexus, and the net!
Any advice appreciated.
Ofiaich
^Same here. I'm running stock 2.2 rom (but rooted) and the notification wont go away, really annoying. I tried the update just to see if it would get rid of the notification, but even though it fails (b/c of root) the notification still comes up. Any help would be appreciated. I'm just going to switch over to a custom ROM if it doesnt go away in a week (looking at a mostly stock rom but w/ black bar )
twolves14 said:
^Same here. I'm running stock 2.2 rom (but rooted) and the notification wont go away, really annoying. I tried the update just to see if it would get rid of the notification, but even though it fails (b/c of root) the notification still comes up. Any help would be appreciated. I'm just going to switch over to a custom ROM if it doesnt go away in a week (looking at a mostly stock rom but w/ black bar )
Click to expand...
Click to collapse
This exact thread exists on the MoDaCo site where I already told the OP that suppressing the update notification isn't an option here. Your have two options. One: You can restore your phone to complete stock without root and ride the OTA updates all the way to FRG83. At that point you could either stay stock or root via the rageagainstthecage method. Two: Flash a custom ROM, or a pre-rooted stock ROM. Paul has a stock ROM with root available on his site on this page. The ROM you mentioned should be fine too if you decide to flash that. Whatever you decide to do, good luck!
Cheers!
crawler9
Sent from my Nexus.
Reboot using Quickboot. It'll get rid of the notification for 4-5 days. Rinse & repeat when it starts popping up again.
Sent from my Nexus One
Thanks for the information, crawler9.
sitinon327 said:
Reboot using Quickboot. It'll get rid of the notification for 4-5 days. Rinse & repeat when it starts popping up again.
Sent from my Nexus One
Click to expand...
Click to collapse
I heard about this method, but I just tried it and it didn't work
Notification came like 5 minutes after boot.
twolves14 said:
I heard about this in other places, but didn't work
Notification came like 5 minutes after boot.
Click to expand...
Click to collapse
Worked for me fine unless I powered off the N1...then I just would Quickboot/reboot again to get rid of it
crawler9 said:
You can restore your phone to complete stock without root and ride the OTA updates all the way to FRG83. At that point you could either stay stock or root via the rageagainstthecage method.
Click to expand...
Click to collapse
If you restore the N1 to stock is there a way to only accept 2.2 ota instead 2.2.1?
Just attempt to install it. It will fail (due to incompatible recovery) and IT WILL stop displaying. Worked for me and I haven't seen the message yet. Just don't go back to "update software" or whatever in the settings.
stuff said:
Just attempt to install it. It will fail (due to incompatible recovery) and IT WILL stop displaying. Worked for me and I haven't seen the message yet. Just don't go back to "update software" or whatever in the settings.
Click to expand...
Click to collapse
Already tried that multiple times. Comes back within a few hours. Thanks though. But i'm just going to install a custom rom on the weekend.
crawler9 said:
This exact thread exists on the MoDaCo site where I already told the OP that suppressing the update notification isn't an option here. Your have two options. One: You can restore your phone to complete stock without root and ride the OTA updates all the way to FRG83. At that point you could either stay stock or root via the rageagainstthecage method. Two: Flash a custom ROM, or a pre-rooted stock ROM. Paul has a stock ROM with root available on his site on this page. The ROM you mentioned should be fine too if you decide to flash that. Whatever you decide to do, good luck!
Cheers!
crawler9
Sent from my Nexus.
Click to expand...
Click to collapse
Thanks crawler9,
Yes, it is my thread there too! I am trying the Quickboot method and will report back.
Ah! That didn't work for me!! Got the message on reboot!
At the weekend, I will read up about latest roms and install it! Only done this once before, and that was quite a few months ago... so always a bit nervy!
Ofiaich
Ofiaich
You're using an ERE36B based ROM? That's bloody ancient!
At least upgrade to a Froyo based ROM.
Hi Rusty!
I will!
I need to read up and be sure of the steps!
I also need to read about Baking roms, where to find latest etc..
But I got a more or less free weekend to do it!
Any specific advice welcomed!
Ofiaich
The Quickboot method actually did work for me, even though it comes back on reboot, if you do "install later" it stopped harassing me for the last few days!
Thank you sitinon327 and galaxys!
ofiaich said:
Hi Rusty!
I will!
I need to read up and be sure of the steps!
I also need to read about Baking roms, where to find latest etc..
But I got a more or less free weekend to do it!
Any specific advice welcomed!
Ofiaich
Click to expand...
Click to collapse
Quick & easy solution would be Enom or Cyanogen, both well specced and upto date.
In addition, both would get you rid of the update notification.
Just to give some info: there is no way to get rid of the notification without modifying the ROM. build.prop needs to be modified with the new signature to avoid this notification when running FRF91.
Just do the install and it will fail and stop asking you... until next time you reboot your phone
Sent from my Nexus One using XDA App
Hi everyone!
I ahve now installed a Modaco Rom and my setting -> About Phone show Android 2.2 and the Build Number shows the info for the Modaco Custom Rom -
FRF91
Now setting up screens as I like them!
Thank you to all for replying and giving advice.
Ofiaich
deleted by user
Hello All,
I am using HTC wildfire for past one month and I just love this phone. All the apps which are present and downladable are really exciting !!
Here I would llike to know few things :
1. I am getting messages of upadate 2.2 available in my phone. I do have a Wi-fi connection to do it (Wi-fi needed info I got from the mobile shop person initially)
My question is If i go for the update taking initiative through the updates message
will there be any problem (like phone may not work and the featues might not work etc etc after updation ?)
2. If anythig happens is it possible to bring back to 2.1
3. Will updation cause any other trouble (may be there will be anything which am not sure or thinking off now ?) ?
Can you guys helps me out by answering the questions . I would like to go for 2.2 as I have heard it is awesome than 2.1 but want to make sure nothing happens to the phone.
Please help.
Am from Bangalore India (if location matters for an update !!! )
This is an official update, so there will be no problems. Go go go
Sent from my HTC Wildfire using Tapatalk
vassileff said:
This is an official update, so there will be no problems. Go go go
Sent from my HTC Wildfire using Tapatalk
Click to expand...
Click to collapse
Hi Vassie,
Thanks for the reply - but if i go for the update is there anything else to do other than 'pressing the update button' in the message ? It will install 2.2 itself ?
Remember, you will lose the ability to root, install root apps, custom ROMs etc. However, looking at your post, it seems it is not a priority, so you might as well go for it.
* Updating should not bring any trouble, since, after all, it is an official ROM, and would have been thoroughly tested before release.
* That said it is recommended to both, restore factory settings and format SD card after the update. It is said to slow down the phone if you do not do so.
* Getting back to 2.1 from 2.2 is possible, but, it is a very long process and potentially risky, and, in general, not recommended.
As for the update, I am pretty sure it will install itself. Never attempted it personally, but, I am sure it will be a "Next - Next" type of procedure.
3xeno said:
Remember, you will lose the ability to root, install root apps, custom ROMs etc. However, looking at your post, it seems it is not a priority, so you might as well go for it.
* Updating should not bring any trouble, since, after all, it is an official ROM, and would have been thoroughly tested before release.
* That said it is recommended to both, restore factory settings and format SD card after the update. It is said to slow down the phone if you do not do so.
* Getting back to 2.1 from 2.2 is possible, but, it is a very long process and potentially risky, and, in general, not recommended.
As for the update, I am pretty sure it will install itself. Never attempted it personally, but, I am sure it will be a "Next - Next" type of procedure.
Click to expand...
Click to collapse
Hi,
Thanks for the valuable comments....
As you have told about rooting - I would like to know what is it (just for information if you dont mind ! any special advantages ?) Also in froyo is it possible to install apps and games in SD card ?
Rooting - Process to access the root of your device. Basically allows a lot more to be done with your device, like installing root only apps like Titanium Backup, SetCPU etc. Apart from that, it allows overclocking and underclocking your CPU, installation of Custom ROMs (Android 2.3.2 is available unofficially) etc.
For Apps2SD, Froyo supports it natively, but, not all apps and games can be moved using that. Only supported ones. Rooting allows you to install additional Apps2SD Scripts like DTApps2SD which allows install to SD irrespective of compatibility.
3xeno said:
Rooting - Process to access the root of your device. Basically allows a lot more to be done with your device, like installing root only apps like Titanium Backup, SetCPU etc. Apart from that, it allows overclocking and underclocking your CPU, installation of Custom ROMs (Android 2.3.2 is available unofficially) etc.
For Apps2SD, Froyo supports it natively, but, not all apps and games can be moved using that. Only supported ones. Rooting allows you to install additional Apps2SD Scripts like DTApps2SD which allows install to SD irrespective of compatibility.
Click to expand...
Click to collapse
Great info. OMG u mean ginger bread in Wildfire (2.3.2 !!!) Please pardon me if am bugging u asking more questions .
For 2.2 am getting an update message - how you install custom roms ?
I guess that will be your own risk !
Yes, it is at your own risk. However, it is pretty safe. There are exit routes available if something does go wrong, also, if you take a backup before installing it, getting back to it is a snap.
Refer this guide, it will tell you all about the process of rooting and installing Custom ROMs.
[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Easy & Safe!)
Apart from that, here is CM7 (Gingerbread)
http://forum.xda-developers.com/showthread.php?t=918072
Lastly, CM7 is still in Pre-Alpha stage, so, it may be a bit buggy. Also, it does not contain HTC's Sense Interface. So, if you prefer that, you can go for Sense Based Custom ROM's like WildPuzzle and SunAabh. They look and feel similar to the official ROM, but, offer many extras. (But they are based on Android 2.2.1)
3xeno, u r a store-house of info! thanx.
can u pls put a link for downloading wildpuzzle_v8.0.11 for htc wildfire?
vishbin said:
3xeno, u r a store-house of info! thanx.
can u pls put a link for downloading wildpuzzle_v8.0.11 for htc wildfire?
Click to expand...
Click to collapse
It is not recommended to use WildPuzzle v8 since it is based on the Chinese Froyo, and, has caused many types of problems like location not working, contacts name not displaying not properly and so on. It is recommended to use the latest WildPuzzle 2.2.1 v0.x if you wish to use WildPuzzle, and that is available here:
http://forum.xda-developers.com/showthread.php?t=877243
Still, FYI, Wildpuzzle 8.0.11 is available here:
http://forum.xda-developers.com/showthread.php?t=761927
Just wondering, if I were to flash to a custom rom, such as Thor... then a few months later ICS comes out for our tablets, what would the upgrade process entail?
I'm hesitant to try a custom rom, because when ICS finally comes I don't want there to be extra steps in order to get the update.
Anyone know how difficult/easy this is going to be? Will it involve having to flash back to stock first, then OTA to ICS?
TIA!
davanw said:
Just wondering, if I were to flash to a custom rom, such as Thor... then a few months later ICS comes out for our tablets, what would the upgrade process entail?
I'm hesitant to try a custom rom, because when ICS finally comes I don't want there to be extra steps in order to get the update.
Anyone know how difficult/easy this is going to be? Will it involve having to flash back to stock first, then OTA to ICS?
TIA!
Click to expand...
Click to collapse
Not trying to be rude but honestly, if youre afraid of a few extra steps than rooting and android is not for you. I suggest an apple product.
But to answer your question, when official ICS comes out OTA Im sure devs will create custom roms that you can just flash. I mean we already have ICS ports in the works.
Why would you want crappy OTA ICS when you could have a faster, custom rom ICS .
jon-.- said:
Not trying to be rude but honestly, if youre afraid of a few extra steps than rooting and android is not for you. I suggest an apple product.
Click to expand...
Click to collapse
Don't assume. I already have ICS running on my Galaxy S; I'm sure I've flashed and reflashed android devices just as much as anyone else here. It's not about being afraid. It's about convenience for a device I've come to rely on day-to-day.
Thanks for the post, anyways. But I'd still like to hear what the process would be to go from a custom rom to the offical OTA ICS.
davanw said:
Don't assume. I already have ICS running on my Galaxy S; I'm sure I've flashed and reflashed android devices just as much as anyone else here. It's not about being afraid. It's about convenience for a device I've come to rely on day-to-day.
Thanks for the post, anyways. But I'd still like to hear what the process would be to go from a custom rom to the offical OTA ICS.
Click to expand...
Click to collapse
From what Ive read (search function), you can update from a custom rom but you will lose root.
davanw said:
Don't assume. I already have ICS running on my Galaxy S; I'm sure I've flashed and reflashed android devices just as much as anyone else here. It's not about being afraid. It's about convenience for a device I've come to rely on day-to-day.
Thanks for the post, anyways. But I'd still like to hear what the process would be to go from a custom rom to the offical OTA ICS.
Click to expand...
Click to collapse
If u rely on this day to day, u do NOT want to flash an ICS rom yet. Not even close for day to day use.Stick with what u have and just be patient.
christianpeso said:
If u rely on this day to day, u do NOT want to flash an ICS rom yet. Not even close for day to day use.Stick with what u have and just be patient.
Click to expand...
Click to collapse
I agree wait for the kinks to be worked out.
If you rely on this device pretty heavily, and you still want to get ICS when it comes out, I would just recommend flashing a custom ROM now that is known to be pretty stable. like you suggested, Thor's ROM seems to be a great one. It definitely improves the speed of the tablet and I have yet to come across any bugs that would inhibit my everyday use. Then, once developers have worked out a ROM for a relatively stable version of ICS, you shouldn't have any trouble switching to that and not worrying about the OTA updates.
davanw said:
Don't assume. I already have ICS running on my Galaxy S; I'm sure I've flashed and reflashed android devices just as much as anyone else here. It's not about being afraid. It's about convenience for a device I've come to rely on day-to-day.
Thanks for the post, anyways. But I'd still like to hear what the process would be to go from a custom rom to the offical OTA ICS.
Click to expand...
Click to collapse
Well, if you're familiar with all that, then you already know how to flash an OEM ROM and would know you already knew how to do it.
can be a bit of a pain going back to stock ota updates. Depends on availability of your devices localized stock rom.( or being able to backup stock rom first). Took me about 5 days to find the right files and steps to get ota working again. Didnt help that i am a total newbie, the iconia is my first android device never flashed anything before except a pc bios. Do your research first and make sure you can go back instead of getting stuck. Here is a link to get you started http://forum.xda-developers.com/showthread.php?t=1155664 another thing when you go back to stock you also go to the back of the line in the update queue as well. I was on 3.2.1 went back to 3.1 got ota updates up to 3.2 but have not recieved 3.2.1 update again yet cheers.
blucmal said:
another thing when you go back to stock you also go to the back of the line in the update queue as well. I was on 3.2.1 went back to 3.1 got ota updates up to 3.2 but have not recieved 3.2.1 update again yet cheers.
Click to expand...
Click to collapse
Now THAT is very interesting. Thanks!
I'm still on a stock rooted 4.2.2 Rom and I need to upgrade to 4.4
I've really had no issues with the touchwiz and I'm running the KM kernel, but from what I was told I need to unroot to get 4.4. I don't know if that's true or not, but seeing as you don't have that many touchwiz roms here maybe I should go with ASOP instead? I was looking at the master list of roms but are the roms carrier dependent?
but from what I was told I need to unroot to get 4.4.
Click to expand...
Click to collapse
You can update your phone through settings (as long as you didn't mess with system files and apps) but you will definitely lose root and get knox.
I was looking at the master list of roms but are the roms carrier dependent?
Click to expand...
Click to collapse
Yes, roms are carrier dependent (with the exception of CM11 nightly builds, which are now unified across all carriers, the rest provide separate builds for different carriers)
carefree12 said:
You can update your phone through settings (as long as you didn't mess with system files and apps) but you will definitely lose root and get knox.
Yes, roms are carrier dependent (with the exception of CM11 nightly builds, which are now unified across all carriers, the rest provide separate builds for different carriers)
Click to expand...
Click to collapse
My phone is rooted but running the stock rom, when it came time to upgrade it would not upgrade at all, I forgot what it would hang at but it ended not doing anything, so getting tired of seeing the upgrade was ready to be installed I hid the message.
But now I need the upgrade because of Google Wallet and tap & pay.
So as far as getting another rom I assume I should be just looking under my carries forum here instead of the master list? Now having said that.. OK say I find a ASOP with 4.2 can I just use that instead of unrooting and then doing the update?
In other words installing a custom ASOP rom would still get me on 4.2 as well?
Samsungmobile said:
My phone is rooted but running the stock rom, when it came time to upgrade it would not upgrade at all, I forgot what it would hang at but it ended not doing anything, so getting tired of seeing the upgrade was ready to be installed I hid the message.
But now I need the upgrade because of Google Wallet and tap & pay.
So as far as getting another rom I assume I should be just looking under my carries forum here instead of the master list? Now having said that.. OK say I find a ASOP with 4.2 can I just use that instead of unrooting and then doing the update?
In other words installing a custom ASOP rom would still get me on 4.2 as well?
Click to expand...
Click to collapse
It depends on what version of android the rom features. CM11 for example is a 4.4 KitKat rom so if you install CM11 you would have 4.4 AOSP rom that is close to the original AOSP rom you would find on Google devices.
For some reason I can't boot my phone into recovery.. I'm holding vol up, home and power and I see it saying booting recovery in the upper left but if I keep holding the buttons the screen and the phone just turns back off again.
*edit
I just noticed I use TWRP Recovery so I think I have to start it from the phone being on.
Well this is odd.. OK so I moved the zip file to the root of the SD card and looking at the recovery and it's not listed under the root of the SD card.. I don't get it.
Oh never mind forgot the setting to switch to SD card
I recently installing PA 4.6 Beta 6 on my Nexus 4 because Android 5 just wasn't working out for me. Unfortunately I've encountered a serious problem: my phone is now using about a gigabyte of data per day! I only noticed this when the default data warning limit kicked in, but initially dismissed it as a side-effect of downloading/synching everything after the install. I reset the data limit and thought nothing of it until 2 days later when the 2GB limit kicked in again.
I've installed Network Connections by Anti Spy Mobile which seems to indicate all the data usage is from Google Contact Synch. I can only imagine something is looping, but seriously how could it be using so much data!?
I've un-installed anything I don't use and turned off automatic backup, but the data flood continues. A search for similar problems hasn't revealed anyone else with this problem, so I thought I'd ask on here before removing PA and switching to Cyanogen Mod.
Cheers.
It's not the ROM causing this.
#stayparanoid
Yep - was never insinuating that it was PA; just that it occurred following the install.
Sadly I haven't been able to work out what was causing it and have had to flash a new ROM before heading back to work in the morning or my mobile provider is likely to have a fit. I've flashed CM and will see how it goes, but I may well come back to PA or go the PAC ROM route. I'm definitely a fan of the PA features and am grateful for the work done by the dev team.
Did you try to accept the 5.0 update while on the 4.6 beta? It would probably have come through a notification. If you told it to download, it will never stop trying until you clean flash
#stayparanoid
Pirateghost said:
Did you try to accept the 5.0 update while on the 4.6 beta? It would probably have come through a notification. If you told it to download, it will never stop trying until you clean flash
#stayparanoid
Click to expand...
Click to collapse
It was actually 4.45 I downloaded because I wanted a stable release. After install there were some OTA updates and I did download them assuming anything OTA would be fairly stable, but I didn't know/realise it would have tried to bring down a major new version (5.0). Looks like it could have been my mistake then for thinking it would just be updates to the version I'd installed.
I did take a backup before switching to CM so if I get some time I might flash the backup and check what version it is.
onyx26_uk said:
It was actually 4.45 I downloaded because I wanted a stable release. After install there were some OTA updates and I did download them assuming anything OTA would be fairly stable, but I didn't know/realise it would have tried to bring down a major new version (5.0). Looks like it could have been my mistake then for thinking it would just be updates to the version I'd installed.
I did take a backup before switching to CM so if I get some time I might flash the backup and check what version it is.
Click to expand...
Click to collapse
If it was the google ota, it wouldn't install anyway.
We have not provided an upgrade ota from 4.x to 5.x
Its likely you were still on whatever version you installed, but the ota was constantly trying to download
#stayparanoid