Related
I rooted my Nexus One with the 1-click androot and today I've received the 2.2.1 update (FRG83) OTA. I don't want to install it because it'll unroot, but the notification is really persistent and irritating, and I'm afraid I'm going to accidentally hit the install button.
How can I make it go away?
Install a custom recovery, make sure it works, try to flash the rom, it will fail because it needs to stock recovery to install, delete the update from /cache/.
That will at least leave you with a little time before it tries to notify you again. Best thing to do is load a rooted custom rom with a build.prop mod to make it think it's a version better/same so it won't try and update you.
I thought I had to have an unlocked bootloader in order to install a custom recovery or flash custom roms. Is this not the case?
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
tenbeau said:
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
Click to expand...
Click to collapse
I was in the same boat as you yesterday. I didn't think of the recovery so I hit update because I was tired of the notification. The phone applied the update successfully and I don't have root anymore. I have no idea how that impacts the recovery since ClockworkMod says the ClockworkMod recovery is installed.
Would like to know as well. Do not want to lose one-click root and would love to get rid of that stupid notification.
check out post #102 here:
http://forum.xda-developers.com/showthread.php?t=791124&page=11
this user says he has gotten it to stop via this method. I cannot verify yet as I have not received the OTA
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
tinymiata said:
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
Click to expand...
Click to collapse
I'm willing to try anything after 100+ "install later" replies Quickboot here I come
Thank you! I don't know why Quick Boot worked, but it seems that it has. It's now been a couple of hours without a notification message when they were coming back every few minutes. Thanks!
wouldn't it be cool if we got around Google's grand plan to force us to update by driving us crazy!?
Hi
newb here!
i have FRG33 build on my phone, and some time ago an OTA update came out that i couldn't install (i get "failed to verify whole-file signature" "signature verification failed" errors). i'm guessing the update is the 2.2.1 release - so how can i install it? i figure there's something i can drop on the sd card and install from there but i don't know what to search for or why this error happens at all (and google has been exceedingly unhelpful)
any help?
thanks!
Is your phone completely stock? Unrooted, stock recovery, stock rom...?
erm.. how can i tell? <,<
i bought it from a friend
i'm pretty sure it's at least rooted though, whatever that means (sudo-like access to phone i guess?) since i have an app called superuser and i downloaded lamppu (led flash as flashlight) which apparently needs root access to work (and it works)
if you need me to paste certain things from settings/options, i can do that
lavalove said:
erm.. how can i tell? <,<
i bought it from a friend
i'm pretty sure it's at least rooted though, whatever that means (sudo-like access to phone i guess?) since i have an app called superuser and i downloaded lamppu (led flash as flashlight) which apparently needs root access to work (and it works)
if you need me to paste certain things from settings/options, i can do that
Click to expand...
Click to collapse
Your phone has an unlocked bootloader if there is a padlock symbol on the first screen when you boot up (the one with the static x).
You can see what recovery is on the phone if you press and hold the volume down button while powering the phone on. This will take you to the Fastboot screen, and you will use the volume down button again to scroll down and select "Recovery" and then press the power button. That will either get you into the stock Android recovery (which will pretty much just be a /!\ symbol) or a custom recovery (which should have a nice text-based menu with options and such).
You can find out information about your ROM by going to Settings --> About phone, and scrolling down the bottom. If you would, post the various version numbers and settings and such.
If you are running another other than the stock recovery and a stock ROM, no OTA update will install for you.
aha, good stuff
here's what i got:
unlocked padlock symbol on boot
my recovery menu is "clockworkmod recovery 2.5.0.7"
android ver:
2.2
baseband version:
32.36.00.28U_4.04.00.12_7
kernel:
2.6.32.9-27237-gbe746fb
[email protected] #1
build#
FRG33
so presumably no OTA updates
how do i get my updates then? (and stop the "you have an update, update now!" pop-up which pops up even during video playback.. i mean, really?)
If you want to get the automatic updates, you'll have to revert back to a stock ROM and a stock recovery. There should be instructions for that in one of the stickied threads.
well, i assume there's a way to update manually as well?
so i guess my question is
a) how do i know what's this OTA update (i.e. where i can find a link for it)
b) how do i install it manually?
and/or i guess more generally -- is there a general intro tutorial to tinkering with android phones that also explains terminology etc (for instance, you said i need a stock ROM, but from http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms, FRG33 is a stock ROM, so am i misunderstanding terminology here? i.e. difference between ROM & build?)
thanks btw, you've been really helpful
Answer: SEARCH.
There must be at least 100 threads on this very topic. To update, you're either going to have to flash a new rom, or revert back to the original shipping rom. Search or read the wiki on how to do either.
Or disable signature checking on CW recovery and OTA updates will install fine.
GldRush98 said:
Answer: SEARCH.
There must be at least 100 threads on this very topic. To update, you're either going to have to flash a new rom, or revert back to the original shipping rom. Search or read the wiki on how to do either.
Click to expand...
Click to collapse
i've tried searching but it's a little difficult when i don't know any related terminology (hence the request for an intro guide of sorts). it's not like i'm posting here without doing nothing else, but google queries like site:xda-developers.com nexus one ota error frg33 for example didn't yield much. i did find a how-to-get-back-to-stock tutorial here but i am still looking for a tutorial to understand that tutorial as i have no experience with adb or fastboot, etc. (not to mention its last updated date is a year ago (although last edited date is fairly recent.. but i'm still wary) i'm learning though.
Rusty! said:
Or disable signature checking on CW recovery and OTA updates will install fine.
Click to expand...
Click to collapse
is there any risk to doing this? if not, this seems to be the simplest option so far, but doesn't a failed signature check usually signal an incompatibility/corruption?
thanks again for your help guys!
The reason it failed the check is because custom recoveries use test keys, and OTA updates use release keys. It's quite safe
If you poke around a little bit, you'll find stickies referencing you to the NexusOne wiki. The following are two guides on adb listed there:
[Newbie Guide] adb/fastboot/bootloader/android 101
[GUIDE] ADB For Beginners (Setup, Use, and More!)
I'm reading the threads and seeing a consistent pattern (and experienced it myself). Referring at least to 4.1.2 -> 4.2 and 4.2 -> 4.2.1, it seems that you can do the OTA update if you if you have CWM but not TWRP. If you accept the OTA and have CWM, it will reboot into CWM, apply the update, ask if you want to preserve recovery and su, and reboot you into the new version.
If you have TWRP, though, it seems people get stuck at error 7 or similar.
When a larger version comes out in the future though I suspect we'll have to flash by hand as the OTA could blow away custom recovery; but for the two mentioned above at least, it wont kill CWM and installs fine with it in place.
I've loved TWRP in the past, but in this case it looks like CWM is handling the OTAs more gracefully. It's just a random chance that I have the latest CWM on my N7 instead of TWRP.
I have never used twrp, but I have done the last updates through cwm recovery and kept recovery and kept root. Definitely recommend cwm recovery.
I just got the OTA here, on TWRP 2.3.2.1, Nexus 7 no 3G. No errors, just worked.
Yeah just got the new update and I'm still rooted
-Google
iGoogleNexus said:
Yeah just got the new update and I'm still rooted
-Google
Click to expand...
Click to collapse
And you are using which recovery?
Both work. If they don't something else is going on.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x
jb0ne said:
And you are using which recovery?
Click to expand...
Click to collapse
CWM ...
-Google
Worked for me using TWRP
Sent from my SAMSUNG-SGH-T989 using xda premium
Just took the 4.2.1 update im still rooted using TWRP...
Status 7 is usually a security thing regarding the signature I think. If anything CWM has signature verification off by default.
Sent from my Nexus 7 using XDA Premium HD app
I really don't understand why people are having such a hard time understanding what is wrong when they receive an error message with the OTA update.
It's not complicated people. You don't need to be a friggin' brain surgeon or a senior level developer. The error message TELLS YOU what the issue is.
Verifying current system...assert failed: apply_patch_check("/system/SOMEFILE")
Guess what? Something is wrong with SOMEFILE. You either modified it, deleted it, "froze" it in TiBu, or did something else that is causing the update to break.
If you look at the updater-script, you can see everything thing the OTA does. It's just a long batch script basically.
The ONLY way this 4.2.1 OTA update is going to fail due to recovery is if you are using the wrong recovery for your device (ie: grouper on talapia, etc.).
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
jersonf said:
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
Click to expand...
Click to collapse
Was your unit a 3G or Wi-Fi only model?
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What are you talking about?
XDA is in no way a site dedicated exclusively to "help people not use the stock software". It's a place where people can discuss their hardware/software including stock/custom/etc. usage and modifications. So not only is your comment 100% incorrect, but it's also contrary to this thread in particular. The thread title clear talks about using a CUSTOM recovery with an update to the stock software. So even if you were right (you aren't), your point is counter-intuitive.
There are many people here that are either mostly or completely stock. That's their personal preference and it's completely fine and acceptable. And it most certainly doesn't mean they don't deserve help or assistance here.
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Also, while OTA updates are written in such a way to remove suid root on the su binary and reinstall the stock recovery image, most new custom recoveries have a work around in place to prevent this. Not to mention it's trivial to restore them back after the update.
brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No accident ... I updated my N7 from 4.1 to 4.2 still rooted.. And I just updated again to 4.2.1 ... Don't know about you but I love these kind of updates
Also I like my devices stock, rooted and a few tweaks here and there along with rooted applications... I'm sure there are many of me out there.
-Google
I prefer to never actually flash the recoveries.. just adb boot them as required - that means my system is always stock for the updates and I can pick a recovery at random should I want them (although generally I only use them to get a root shell to install su when I get a new phone).
I am rooted stock with cwm touch and the ota fails staus 7. I'm pretty sure I didn't do anything to "break" the update for myself. It's kind of funny the clockwork stops and asks about flashing an untrusted rom and then doesn't allow it. I would rather sit out of this whole 4.2 bs anyway.
I was rooted and stupidly just clicked the update to 4.2.1 without thinking, it didn't even occur to me to take any measures to keep root or custom recovery. So I lost both. It only took a few minutes with Wugs' toolkit to fix though.
I've taken three OTAs with TWRP and had no problems with any of them.
Sent from my Nexus 7 using Tapatalk HD
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
re: twrp
NirAndroid said:
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
Click to expand...
Click to collapse
You already lost the ability to receive OTA updates by rooting
the phone. If you want to get OTA updates the phone cannot be
rooted or have custom recovery like twrp.
The whole and main idea behind having twrp custom recovery
is to be able to flash custom zip file roms and mods.
With stock rooted firmware you will not be able to successfully
flash any custom roms or mods.
If you do flash any custom zip file roms using twrp
you will also loose the ability to have OTA updates.
Good luck!
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Misterjunky said:
You already lost the ability to receive OTA updates by rooting
the phone. If you want to get OTA updates the phone cannot be
rooted or have custom recovery like twrp.
The whole and main idea behind having twrp custom recovery
is to be able to flash custom zip file roms and mods.
With stock rooted firmware you will not be able to successfully
flash any custom roms or mods.
If you do flash any custom zip file roms using twrp
you will also loose the ability to have OTA updates too.
Good luck!
Good luck!
Click to expand...
Click to collapse
NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
If you check the OTA option and find an update, the updater
will tell you that it cannot install the update due to an unofficial
operating system or something to that effect, I forgot the exact
wording of the message. (if you're rooted)
There is a way to unroot the phone but in my opinion it's just not worth the
hassle to re-root it because as I said being rooted and having twrp recovery
will not help you much at all since you will not be able to flash any custom
roms or mods with out loosing your official stock status which needs to
remain intact in order to be able to get future ota updates.
Good luck!
NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
Mr. Junky is correct. But why would you even want an OTA update? Even if you could it would unroot your device. If there is/was a software update it will be on here or SamMobile about the same time & you can install it manually.
NirAndroid said:
First, thank you for the quick reply,
Second, are you sure about it? every place I looked people saying that root doesn't have anything to do with OTA updates.
It also say that I can put TWRP or CWM and still getting the OTA updates, all I have to do for this to happen is to be with stock rom (which is what i'm currently using)
Click to expand...
Click to collapse
You have only 2 posts on XDA and you are second guessing our replies on your question? Either believe what we answer or stick to google and don't waste our time.
NirAndroid said:
Hello
I bought the Note 4 from T-mobile and i'm running stock rom.
I just root the device with chainfire tool and I'm thinking to change the recovery from stock to TWRP.
I'm wondering if by doing that i will lose the ability to get OTA updates from Samsung / T-mobile.
I did a search on the forum for this question, most of the threads are a year old so i just want to make sure that the answer is the same for our new device.
Please answer just if you know for sure, Thanks
Click to expand...
Click to collapse
Well OTA is out of the question. But I was successful with the last update by using Kies 3.
I just had to root again afterwards using the same method.
Brava27 said:
You have only 2 posts on XDA and you are second guessing our replies on your question? Either believe what we answer or stick to google and don't waste our time.
Click to expand...
Click to collapse
No body asked you to spend your time in my thread, you are more then welcome to move a long because its clearly that you have nothing smart to say beside rasing your post counter.
For all the others, thank you for your help.
The reason that i would like to keep the OTA updates is because i love the stock rom and i dont want to check every timr on the internet if a new build has came out.
its much more easier with OTA too keep being update. But i guess my needs to be root are biger and i will need to flash the updates manually.
Once again, thank you.
I get Ota updates on mine rooted.Only thing u can't install if u have twrp will put u in a boot loop it needs the stock android recovery.You have to wait for a rom with the update
...........As long as I can remember, you root a device you lose carrier OTA updates. ..why is this so difficult for people to comprehend o_0 every new device every year it's the same questions. .......you have the capacity to root......yet you question if you'll lose OTA -_-, & most root methods have disclaimers saying you lose this x we are not responsible for brick etc. ........
Sent from my SM-N910T using Tapatalk
I think I already know the answer, but with a £550 device I'd rather double-check with the experts.
Is there any reason that I should not boot temporarily to TWRP to install SuperSU 2.62 ("fastboot boot twrp.img")? I don't believe that a permanent TWRP installation is a necessity, and if I understand Chainfire's comment correctly:
http://forum.xda-developers.com/apps/supersu/chainfire-systemless-root-android-6-0-t3271137
leaving the device as stock as possible, including stock recovery, means an easier upgrade path for OTAs. The best of both worlds - regular OTA security updates plus root.
Any reason that this would not work, and more importantly any reason that it might risk the integrity of my N6? I don't want an expensive paperweight...
Thanks...
dahawthorne said:
I think I already know the answer, but with a £550 device I'd rather double-check with the experts.
Is there any reason that I should not boot temporarily to TWRP to install SuperSU 2.62 ("fastboot boot twrp.img")? I don't believe that a permanent TWRP installation is a necessity, and if I understand Chainfire's comment correctly:
http://forum.xda-developers.com/apps/supersu/chainfire-systemless-root-android-6-0-t3271137
leaving the device as stock as possible, including stock recovery, means an easier upgrade path for OTAs. The best of both worlds - regular OTA security updates plus root.
Any reason that this would not work, and more importantly any reason that it might risk the integrity of my N6? I don't want an expensive paperweight...
Thanks...
Click to expand...
Click to collapse
having root = no ota, so having twrp is besides the point. anyways, twrp is one of the mist useful tools to have if you mod your device. you can make, and restore, a nandroid backup. if you make a mod, and it messes up, you probably wont noot anymore, but a nandtoid backup restored will bring your device back to how it was.
Yes, thanks, Simms, I get all that, but it's not really answering my question. Is there any problem with using temporary TWRP to install SuperSU?
Also if you read Chainfire's comment he makes it clear that his systemless root doesn't prevent OTA, whereas having a non-stock recovery might.
dahawthorne said:
I think I already know the answer, but with a £550 device I'd rather double-check with the experts.
Is there any reason that I should not boot temporarily to TWRP to install SuperSU 2.62 ("fastboot boot twrp.img")? I don't believe that a permanent TWRP installation is a necessity, and if I understand Chainfire's comment correctly:
http://forum.xda-developers.com/apps/supersu/chainfire-systemless-root-android-6-0-t3271137
leaving the device as stock as possible, including stock recovery, means an easier upgrade path for OTAs. The best of both worlds - regular OTA security updates plus root.
Any reason that this would not work, and more importantly any reason that it might risk the integrity of my N6? I don't want an expensive paperweight...
Thanks...
Click to expand...
Click to collapse
Don't usually encourage use of toolkits but Wug's toolkit includes and option to do this kind of one time boot, I don't know off the top of my head what actual process it uses for that or I'd just tell you that. But yea I'd just recommend leaving TWRP on and after first flashing it and booting into it twrp should prompt you something along the lines of keeping /system mounted as read-only, do that and make a backup including the "system image" and boot. Then in Advanced>uncheck "mount system as read-only."
Whenever an ota rolls around you can go back into twrp and restore that boot and system-image backup when you boot up android will replace twrp with stock recovery and the ota should work.
Thanks again - I appreciate the answer, but again it doesn't really answer my question. I've been using TWRP for years and I'm well aware of its benefits. What I want to know if there's any problem with using it as a one-off to install SuperSU, leaving stock recovery in place when I reboot so that TWRP can't interfere with the OTA.
I'm also very well aware of NRT, which again I've used for years and have donated to several times (excellent program), but I don't need it when "fastboot boot recovery twrp.img" will do the job faster.
Am I not explaining myself properly?
dahawthorne said:
Thanks again - I appreciate the answer, but again it doesn't really answer my question. I've been using TWRP for years and I'm well aware of its benefits. What I want to know if there's any problem with using it as a one-off to install SuperSU, leaving stock recovery in place when I reboot so that TWRP can't interfere with the OTA.
I'm also very well aware of NRT, which again I've used for years and have donated to several times (excellent program), but I don't need it when "fastboot boot recovery twrp.img" will do the job faster.
Am I not explaining myself properly?
Click to expand...
Click to collapse
nah there should be no problem with that.
theres no issue with it, just keep your bootloader unlocked, or you can have issues in the future. btw..
fastboot boot recovery recoveryname.img as opposed to fastboot flash
Thanks, both - I appreciate the help.
Just in case anyone might find the confirmation useful, yes, it did work. I used "fastboot boot twrp.img" to install SuperSU 2.62-3 and it's all working fine. If I understand Chainfore correctly in the link quoted above, using SuperSU's "full unroot" will allow the next OTA, then I can repeat the fastboot install, which should be far simpler than overwriting the system.img.
why would you want an OTA? this is XDA Developers, the worst ROM here is better than ANY OTA that you can have, plus you get it sooner and can try them all and have a backup of your favorite one. This sort of thing always makes me laugh!
I am glad to have brought some laughter and joy into your life. Though I hope that you can find better in your real life, right...?
buschris said:
why would you want an OTA? this is XDA Developers, the worst ROM here is better than ANY OTA that you can have, plus you get it sooner and can try them all and have a backup of your favorite one. This sort of thing always makes me laugh!
Click to expand...
Click to collapse
For noobs, Android Pay is one reason they may want to stick with factory stock with OTA capabilities. Systemless root is not easy for noobs to grasp.