Related
I have a rooted N1 running 2.2 with no mods installed. I dont want to upgrade to the latest 2.2.1. How do I get rid of or disable the system update available notification? Cant find any settings anywhere to turn it off.
Why the opposition to FRG83 out of interest?
Rusty! said:
Why the opposition to FRG83 out of interest?
Click to expand...
Click to collapse
1. I used the 1 click root
2. I have not found any info on why I need 2.2.1
3. I tried 3 times to install the update with not success
You can't turn off the update notification. You need to modify the build.prop for that.
You can't install update if your system isn't stock.
For me the update notification stopped after I ignored it for 1 week.
Be warned though - my N1 became super unstable at that point (2-3 crashes per day).
I finally gave in and upgraded - did not see any improvements. Battery seems slightly worse. Rooting was easy. And has crashed once. (Compared to NOT a single crash in 4+ months before)
nexusdue said:
did not see any improvements
Click to expand...
Click to collapse
This seems to be the consensus...at least among those I know with Nexus Ones. I'm on CM6 and never received the OTA notification..and I have no intention of updating to 2.2.1....ever... unless it's a CM nightly, but I'm happy with CM6 stable so I'm sitting pat.
So......It looks like I either update my phone, install a rom or get use to pushing "install later" every time I go to use it?
bhds said:
So......It looks like I either update my phone, install a rom or get use to pushing "install later" every time I go to use it?
Click to expand...
Click to collapse
One more thing you can try: Download quickboot from the market. When you get prompted to install the update again, dismiss it and then reboot your device using quickboot. Seems to make it go away, for few days anyway. Check out post 117 on this page and you can read backwards from there and see what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=791124&highlight=quickboot&page=12
Old MuckenMire said:
One more thing you can try: Download quickboot from the market. When you get prompted to install the update again, dismiss it and then reboot your device using quickboot. Seems to make it go away, for few days anyway. Check out post 117 on this page and you can read backwards from there and see what I'm talking about.
http://forum.xda-developers.com/showthread.php?t=791124&highlight=quickboot&page=12
Click to expand...
Click to collapse
I'm currently using this method to "hide" the update prompt. I haven't been keeping close track, but it's seems to have hidden the message for almost a week. I'm trying to decide if I want to root using the new SuperOneClick method (http://forum.xda-developers.com/showthread.php?t=803682), but I want to make sure it's as painless as it sounds. Hopefully, it's just 1) let the phone update to 2.2.1, 2) reboot, 3) run this OneClick method, and I'll have superuser back without having to reinstall my root apps or set them up again.
Anyone know if this is all that's needed to root after letting the phone upgrade to 2.2.1?
bhds said:
So......It looks like I either update my phone, install a rom or get use to pushing "install later" every time I go to use it?
Click to expand...
Click to collapse
I just installed 2.2.1 and used the SuperOneClick method to root the phone again. I had to turn the phone off, run the program, and then boot the phone for it to work. I suggest you try this method. It couldn't be much simpler.
I just got a prompted notification that 2.3.2 system update is now downloaded and verified in my phone. Just need to go ahead and ok the install/update on my phone. Not sure if most or all are getting this?
Should I? LOL
more info:
"Android 2.3.2
601kb
This system update from Google contains important bug fixes."
Go for it.
This is probably the update that includes the major SMS bug fix. Samsung posted to their official twitter account that and update to address that is coming very soon.
It looks like v2.3.2 is the one.
Funny thing though, I never had problems with the SMS bug. I have sent/received SMS (2k+). And when I got the notification, I just pulled the battery off to check my S/N to register in the Samsung website. LOL
Is there any other bug/fixes with this updates other than the SMS bug?
If you're rooted, you might want to wait and see if it's safe to do it (ie., doesn't break root) unless you're confident on how to get it back. The last update screwed with Recovery and gave some people some slight grief for a short period.
Just rooted
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Just rebooted after update, seems that at least the browser got some kind of lagfix, for example www.n4g.com.
"Your system is currently up to date."
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Without thinking I chose to install it while being rooted and not backing up. After it rebooted it froze (when it couldn't find a recovery I'm guessing.) I pulled the battery, let it reboot, and I'm still 2.3.1 and rooted. Just FYI
AllGamer said:
hmmm.... what about people on Custom ROMS ?
i check the Settings > About > System Updates
and there's nothing it says
"Your system is currently up to date."
Click to expand...
Click to collapse
Often one have to wait untill the devs implement the update into the custom rom.
Generally once you're on a custom rom, you're best to wait for the rom dev to give you guidance.
treodoc said:
Wouldn't you know it? After I just finish rooting using the step by step guide, the first thing that pops up is that there is an update to install. So my question is, will installing this update kill my root? Or any other negative consequences for my newly-rooted SNS if I update to 2.3.2?
Click to expand...
Click to collapse
Not sure without being able to open the update file and see what it actually does.
IF you're going to try it. Have a nandroid backup made of your system as it is right now, and have a copy of CWM recovery handy to reflash via fastboot.
You'll probably have to re-root if you can even get the OTA to stick (like the one post above that says it didn't...)
so, back to stock recovery before update?
swype
FYI, swype did not work after update, had to reinstall, now works fine.
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Would those of you who get it, if you have a chance, please run the logcat on your phone BEFORE updating and try to catch the url so we can get a manual link for it:
in order to extract the url for the system update, we need to run alogcat from the market, then when the update notification appears look in your logs for a url that says something like clients.google . You can install alogcat, then set filter to clients.google
Click to expand...
Click to collapse
Phantom1275 said:
How do I get this update?
Made a check for updates in my NS, and I got none.
Still in 2.3.1 here.
Click to expand...
Click to collapse
You can try to check in. *#*#2432546#*#*
it just says that checkin succeeded on notification bar and that's all... No updates...
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
krohnjw said:
You can try to check in. *#*#2432546#*#*
Click to expand...
Click to collapse
That's the check I have mentioned.
Still nothing. Guess I have to wait.
Trinitronik said:
it just says that checkin succeeded on notification bar and that's all... No updates...
Click to expand...
Click to collapse
It's going to roll out slowly, just like the 2.3.1 and Market updates did. I don't think all the checkins in the world will speed it up by any significant amount.
What we impatient types need is someone who is offered the update to grab the url so we can just manually download it.
Udaw said:
How to root 2.3.2. Are there any differences ? what clockmod recovery use ?
Click to expand...
Click to collapse
No one knows yet! Have to get it to see what it changes (breaks).
Just got a system update notification... taking forever to install... anyone know what it entails?
Edit: SO I see that Sprint ID / EW!!!) was installed, and my Firmware is 2.2.1, and baseband is S: P100.08 S: EB28, and Build is SPH-P100.EB28...
Problem is, I can't remember if that's new or not...lol. Damn me for not paying attention, and DAMN ME for thinking that the possibility of a HC release was possible... stupid hopes and dreams....
Edit II: Just found this report... compared to the rest of the updates, the SGT got the short end of the stick YET AGAIN!!!
http://www.wirelessandmobilenews.co...epic-4g-tab-transform-updates-coming-321.html
"The Samsung Galaxy Tab update adds Sprint ID features."
I updated also and 2.2.1 is new, also ot updated the modem as seen by hitting the soft menu key during the update and looking under about phone, baseband. I would like to see if the update package had a whole modem.bin in ot but i installed the update before I got the temp file. The last update only had a modem file of a few kbytes so it just patched the modem. It would be great to get hold of a whole modem.bin as there are none for the sprint tab currently.
Sent from my SPH-P100 using XDA App
I was just going to as if anyone was able to grab the modem.bin. Hopefully we get luck and someone is able to do so.
What about root status? I'm hesitant to update if it breaks root because of the issues I've had with the stock gallery app (removed it via a root file explorer).
I updated my rooted Gtab and the root seems unaffected. I use mine without a data pack - wifi only. I used the root to get rid of the activation nagger in the notification bar - and it's still gone and SuperUser is still operating.
However: Sprint ID only works through a Sprint Subscriber Data Pack - not over WiFi, unless you have a company "Keyword". Alas - I don't like Sprint ID anyway.
sprint tv
i installed the "sprint" id, and it says in the description about sprint tv. i had this on the evo, but i feel like i'd make better use of it on a 7 inch screen. any ideas how to get it on the tab? i searched the market under the sprint tab and had no luck finding it.. any suggestion would be great
I got the OTA shortly after trying to install clockwork and patching an overclocked kernel. I wasn't expecting the OTA until Monday, but I went ahead and try to install it (it failed, of course).
I managed to pull the downloaded zip file out of my cache and check if there was a modem.bin. Unfortunately, once again, there's only a modem_delta.bin, so no luck there.
I tried running the update again manually after rolling back my kernel, and apparently I still had a modified boot.img, so after doing a full wipe, rolling back to DJ30, and then manually updating to EA24, I was able to get the EB28 update installed, with all of its Sprint ID goodness. It's very late now so I don't have time to actually play with it much, but I'm actually happy to be back to an official build. I'm hoping they fixed a few of the bigger issues I had with EA24, but I somehow doubt it.
Previously I was rooted and had the Bauxite kernel. I flashed the original kernel back and then installed the EB28 update. I lost root, so I tried superoneclick again. It said it rooted but superoneclick locked up while "Remounting system with read-only access..." My tab is unresponsive but the buttons are still lit up.
Update: I finally got it to reboot and I am rooted again.
matt6x7 said:
Previously I was rooted and had the Bauxite kernel. I flashed the original kernel back and then installed the EB28 update. I lost root, so I tried superoneclick again. It said it rooted but superoneclick locked up while "Remounting system with read-only access..." My tab is unresponsive but the buttons are still lit up.
Update: I finally got it to reboot and I am rooted again.
Click to expand...
Click to collapse
Would you mind attaching your file for the original kernel? I forgot to make a backup when flashing Bauxite.
powermatt said:
What about root status? I'm hesitant to update if it breaks root because of the issues I've had with the stock gallery app (removed it via a root file explorer).
Click to expand...
Click to collapse
I applied the update last night and can confirm that root is still intact, so the super one click method should still work if you haven't rooted your tab prior to this update.
Unfortunately, what is also intact is my long standing issue with the stock Gallery app (rogue sensor usage causing massive battery drain). Ah well, removed with Titanium backup, replaced with Just Pictures, problem fixed. Again.
Other than the addition of Sprint ID, this seems to be a pretty minor update. Could be my imagination, but it seems a tad snappier than the EA24 update. Could be the incremental increase to Android 2.2.1. But other than Sprint ID, there are no major new features.
powermatt said:
I applied the update last night and can confirm that root is still intact, so the super one click method should still work if you haven't rooted your tab prior to this update.
Click to expand...
Click to collapse
Thanks for the useful info. I was hesitant to run the update after the previous hassles. I've just updated mine without any noticeable detrimental effect.
regards,
Tony C.
Root was not intact for me after upgrade. I tested with root explorer, and font changer. Both failed after trying to get root permission. I just used SOC after upgrade. All was good...
@lloydcabraham
Here is my backup kernel prior to the new EB28 update. Sorry for the delay, I've been engrossed in basketball.
matt6x7 said:
@lloydcabraham
Here is my backup kernel prior to the new EB28 update. Sorry for the delay, I've been engrossed in basketball.
Click to expand...
Click to collapse
Thanks I really appreciate it!
I was previously rooted with SuperOneCLick (rageagainstthecage method). I did not unroot prior to the upgrade. The upgade said it failed but a look at About Phone proved otherwise. I would suggest that people unroot before the upgrade but it did not matter for me.
After the update I no longer had root access. But I was able to root with SuperOneClick again. I have had no problems since the upgrade/reroot. There are no interface differences that I have spotted so far.
Can someone please post the application name for the Sprint ID so I can remove it. I had gotten rid of all the Bloatware and now after this update I get this which I will not use.
By the way I was rooted with Super One Click and using the Once Click lag Fix and after update I did lose Root. Just re-rooted and am fine now. Got scared because the orientation was not working and I thought it broke it. Sohow the update set the orientation lock.
Also I deleted a couple files hoping these were the new Sprint ID update.
Does anyone know what they are and if I need them can somone please post them? I will take the best guess of what I remember them being called.
Perhaps someone can post there Sprint file names.
SprintAndroid
SprintUpdate
Thanks,
Mark
Can someone post the update.zip for the update? I got the OTA notification but when it attempted to install (using Stock recovery), it failed, somehow.
Thanks in advance.
I need the update.zip as well.
Hell, mine still tries to update my tab to EA24 which always failed. Can't even get the notification for 28. Time to go to Sprint and raise some hell....
Sent from my SPH-P100 using XDA Premium App
My sprint galaxy tab was updated the EB28 the day I got it (two days ago), today I was trying to get CWM on the tab, got stuck at Samsung screen, so I used odin and flashed back to DJ30 (without baseband, which is already at EB28) and have been trying to get back to EB28 since.
Can any of you kind gentlemen who updated to EB28 do a roto backup and upload the file? I think this is the only way I can get back into EB28 at the moment.
Many thanks!
hallo guys
just saw that amazon is pushing the next OTA - 6.2.2
this time i could again verify this method to prevent the OTA:
i deleted /system/etc/security/otacerts.zip - watched the update downloading to the cache folder but did not install - after a reboot the update file was disappeared from the cache folder - i was registered at amazon all the time - and i'm still on 6.2.1
this worked for me - no guarantee
update: worked with 6.3 again !
I assumed the file needs to be permanently removed based your post, but I renamed them to keep them around (I am glad I did)
I did what you recommended and then I rebooted (renamed instead). Once I rebooted though, GMail would crash everytime I tried to use it and the Market said it could not connect. Once I put those files back and reboooted they worked again. So any other ideas would be appreciated.
... but I renamed them to keep them around ...
Once I put those files back and reboooted they worked again
Click to expand...
Click to collapse
yes - as i wrote - i deleted otacerts.zip (only this one) from /system/etc/security/ (renamed and moved to sdcard)
i'm using the android market without any problems
sorry had a typo with the filename !
I only see cacerts.bks and otacerts.zip. Which did you delete?
sorry it is a typo - thank you !!!
it is otacerts.zip !!!
will correct the post - again thanks !
Anyone have any details about the update? What's new?
i think it's too new for detailed information and don't know cause it did not install
but i'm shure detailed information will be availabe in the next days
as well as a pure update version as it was with 6.2.1: http://forum.xda-developers.com/showthread.php?t=1407852
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
DalekCaan said:
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
Click to expand...
Click to collapse
don't know - sorry - but for me it's the second update i survived
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
It should wipe everything.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
podspi said:
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
Click to expand...
Click to collapse
The OTA updates thus far typically overwrite the filesystem, so yes it would knock out recovery. You can use a "patched" ROM that will not touch the partition the recovery data is on.
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
jshaw49 said:
Anyone have any details about the update? What's new?
Click to expand...
Click to collapse
One thing I've noticed is that it mounts a lot faster when attached to my PC via USB. On 6.2.1, it mounted in about 10 seconds. Now it does it in less than 2.
DesDr0id said:
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
Click to expand...
Click to collapse
Thanks for this. Exactly what I was looking for (I'm fairly new to rooting).
Sent from my Kindle Fire using xda premium
Just wanted to say that I tried this, and as far as I can tell it worked like a charm. I even tempted fate by hitting 'Sync', but my Kindle refused to update (it wouldn't even attempt to download the update from device settings).
I just flashed the pre-rooted 6.2.2 update and deleted otacerts.zip, so here is hoping they didn't change something to make this not work...
i'm glad that it is working for you too ...
I just wanted to add that I have been blocking the OTA update using Droid Wall. Still running very happy on 6.2.1.
The only down side to this method is having to set permissions initially then updating Droid Wall as I install apps.
Meh. I'm not sweating this update much.
I've still got the Market, still have Swype... Sooooo far as I can tell the only thing I lost is Google Currents, which I wasn't finding much useful since the KF doesn't seem to want to let it sync while I'm not around.
Sooooo sooner or later I'll get the Burrito running again, but I'm in no rush.
FIREMOD replaces BURRITOROOT
http://forum.xda-developers.com/showpost.php?p=21595398&postcount=105
as i am fairly familiar with the rooting process I am okay with amazon pushing update OTA, but some of my friends are complaining and I have to help them root their devices again after OTA update. So if this OTACERTS.ZIP deletion actually works (without other consequences) then I will surely recommend this to my friends
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
positivehxcgo said:
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
Click to expand...
Click to collapse
just try kingroot 4.1 (New Version)
has worked for me
LG Noah
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
There is no official download for 4.5.4 yet, did you get it OTA ? If so, it's a big warning for everybody out there to disable the OTA updates!!!
Most likely Amazon fixed the Kingroot exploit, so I'd be actually surprised if 4.5.4 is rootable via the same approach as before.
Fellas, cherish the root that you got, and don't even think about updating !!!
Is there any way to downgrade to 4.5.3 without going through Amazon?
what is the command line to disable auto update ?
and does it auto update ?
alucard_xs said:
what is the command line to disable auto update ?
and does it auto update ?
Click to expand...
Click to collapse
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
jmz said:
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
Click to expand...
Click to collapse
Thanks so just adb to my device and this command line is enough ?
alucard_xs said:
Thanks so just adb to my device and this command line is enough ?
Click to expand...
Click to collapse
yes. I dunno if it gets reset on boot or not. I think it does.
My tool also does
Code:
mv /system/priv-app/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA.apk.bak
Yeah it was an OTA update. Literally just as is was getting my laptop out to block them
otaverifier stays blocked with boot
jmz said:
yes. I dunno if it gets reset on boot or not. I think it does.
Click to expand...
Click to collapse
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
DoLooper said:
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
Click to expand...
Click to collapse
Ok. I wasn't sure.
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
alucard_xs said:
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
Click to expand...
Click to collapse
Code:
adb shell pm block com.amazon.otaverifier
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
CrazyRach said:
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
Click to expand...
Click to collapse
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
bibikalka said:
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
Click to expand...
Click to collapse
i actually had my device proxied via burpsuite while contacting support and them conducting the rollback but wasnt able to capture anything
one interesting thing i noticed while having the hd6 proxied is that the silk browser constantly tries to phone home to internal.amazon.com
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
CrazyRach said:
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
Click to expand...
Click to collapse
apologies for the delayed response,
ive been dealing with a serious injury over the past few days.
i just went and told them that after updating to 4.5.4 i was having issues with the screen flickering and glitching, and system lags that persisted across factory resets.
if i have the time to try later im gonna see if i can get them to roll back one of my other devices while monitoring my entire network this time vs just proxying the device via burpsuite like i did before, then perhaps this may shed some light on the rollback/upgrade process