Related
So today I was at work and a little notification popped up about a software update. I just left it alone and went on with work. I come back from lunch and it updated itself and disabled all my apps and root. The SD nethod with Nooter does NOT work. The software version showed 1.0.1. I ended up returning the Nook as its pretty useless with no root & 3rd party apps for me. I will be waiting and seeing where this all pans out as more people get the OTA. Good luck!
houseofbugs said:
So today I was at work and a little notification popped up about a software update. I just left it alone and went on with work. I come back from lunch and it updated itself and disabled all my apps and root. The SD nethod with Nooter does NOT work. The software version showed 1.0.1. I ended up returning the Nook as its pretty useless with no root & 3rd party apps for me. I will be waiting and seeing where this all pans out as more people get the OTA. Good luck!
Click to expand...
Click to collapse
I haven't gotten any notification of an update and I've been using the wifi all day. Don't see anything about an update on the Barnes and Noble site or community forums.
Not saying it doesn't exist. But if so, it's quite odd for them not to officially announce it the way they do for the original Nook firmware updates.
Keeping my WiFi off for the time being though.
This is definitely not good news. Can someone else confirm this firmware update ? B&N is not showing any updates on their website and the community forum over there is not indicating anything either. Haven't heard anything over on MobileRead.com forums either. I'd imagine that someone else would've gotten this update by now (either rooted or not) and reported it.
I'm wondering if mine just happened to get caught in a glitch in their system. Like how some Android phones got updated randomly before others. Your guess is a good as mine. I guess we will see if anyone else got hit too.
Any idea of where it saved it to? If this comes down the pipe, I'd like to pull it apart for a look at what they did
Those bastards
Maybe its time to edit the host file to prevent NC from calling home?
Sent from my SPH-D700 using XDA App
jimmyz said:
Maybe its time to edit the host file to prevent NC from calling home?
Click to expand...
Click to collapse
Do we know what domain the updates are coming from?
There are some instructions for blocking updates here:
http://forum.xda-developers.com/showthread.php?t=860480
But as the author says, they may not work (read the thread).
The best option is to flash a new rom probably and it looks like good progress is being made there.
houseofbugs: Did you get a notification before reboot? My guess would be that these updates are installed from recovery, so there may be an interim solution to delete the file from internal memory if you get a notice.
Far from perfect, but better than nothing.
So nobody else has received this update ? I Googled for any info, checked out the BN forums and another forum dedicated to the NC and nobody else has reported any kind of software update.
Just as a precaution I called my gf and had her turn off my nook and turn off wifi on hers, not looking forward to going home and finding root has been broken. Don't like the fact that it force updates itself without user interaction too, from what I gathered from the op's post. OTACerts.zip doesn't do anything on the nook?
ZeroSX said:
Just as a precaution I called my gf and had her turn off my nook and turn off wifi on hers, not looking forward to going home and finding root has been broken. Don't like the fact that it force updates itself without user interaction too, from what I gathered from the op's post. OTACerts.zip doesn't do anything on the nook?
Click to expand...
Click to collapse
If the Op didn't mess with the OTACerts.zip, then we wouldn't know. Op, did you disable updates as suggested in the thread above?
I haven't seen any "update" messages on mine. I double-checked and my NC is still running version 1.0.0. My wifi has been on for the past couple days (including all night last night) and I've seen nothing suggesting a firmware update.
Maybe I'm lucky. Looks like B&N may be planning to force a firmware update soon. It'd be nice if they gave us the option to decline it (they'll probably strip in-Store features without the most current version, but I've read here that rooting does away with in-Store features anyway).
There's another thread over in NC Android Dev where someone got a firmware update scare. Looks like a false-positive, but it's something to keep us on our toes.
Hmm no updates here either..
nothing...
I remember reading that someone else got an Update Available notification in the huge thread that started this forum. I think they said they did a system restore to factory and it allowed them to re-root it, but I don't recall if it had a version number in it. Same thing happened, nobody knew what was going on.
Regardless, we should eliminate the ability for B&N to apply automatic updates at will.
After un-rooting and resetting back to factory fresh settings, the Nook DID download an update, version 1.0.0.0. The notice appeared in the notification area.
The good news is that I am still able to root using the nooter method.
gojeda said:
After un-rooting and resetting back to factory fresh settings, the Nook DID download an update, version 1.0.0.0. The notice appeared in the notification area.
The good news is that I am still able to root using the nooter method.
Click to expand...
Click to collapse
That's not an update, it's an improper notification. It hasn't been *updated* to anything, since that's what it came with stock. It's just the nook's way of saying it's been reset to defaults.
Hopefully the update is not rolling out...
...but if it is I hope it hits my NC after this weekend when I have to take my son from the USA to the UK! Two flights and two airports without Angry Birds to keep him happy would be unpleasant.
Hmmm...
OTAcerts.zip would be my usual suggestion, for this kind of thing.
If anyone gets the nook with the update, try and grab the URL of the update via logcat.
Failing that, someone with the update might need to try things to get it rooted RageAgainstTheCage, anyone?
I don't know what you specifically need for the nook to let you sideload etc, but RageAgainstTheCage would make sense to work and get at least shell root.
I just got the nexus 6 from verizon, and it had a notification that there was a system update, I accepted it, and it rebooted, i think it got installed, but the notification was there again, I have done it like three times, but the notification is still there, the about phone says LMY48M, I think is updated already, How can I fix this issue?
thanks for the help
jorge3687 said:
I just got the nexus 6 from verizon, and it had a notification that there was a system update, I accepted it, and it rebooted, i think it got installed, but the notification was there again, I have done it like three times, but the notification is still there, the about phone says LMY48M, I think is updated already, How can I fix this issue?
thanks for the help
Click to expand...
Click to collapse
it will take you through all the updates. if you only updated one time, then you arent done yet. there are three marshmallow updates. one main update, and two security updates.
Something really strange happened to my father's Turbo. He got it brand new from Verizon about a month ago and I sat down and updated up to .44. I told him that if another update comes in, do not touch it because I was going to unlock it with Sunshine and root it. I don't allow him to do updates on anything, I do it for him when I know the bugs won't screw anything up and flash it myself.
I was ready to unlock the phone and when I looked About Phone, I saw it was on .49. So I checked a little more and found the exact date and time it updated (July 23rd, 7:23PM). The date and time coincided with his being in the hospital and I had possession of the phone. The phone was sitting in my room (there's no one else around to mess with things), undisturbed for a week. I never saw the .49 update show up before I left it alone--and I checked it to make sure he didn't accidentally update it, just in case. I know on my Turbo, it was annoying as all get out and I dealt with the nag screens for a week or so until I could buy the Sunshine app.
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.
pearlheartgtr said:
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.
Click to expand...
Click to collapse
Others have claimed that with some people being very skeptical. I would not put it past Verizon. Is it possible if you totally ignored the nag screens Verizon takes that as a yes?
Thing is, the update and nags never showed up in the first place for it to be accepted or ignored. It just happened.
My phone auto-updated while I was sleeping one night. I was thinking of unlocking the bootloader. Oh well.
lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconeted a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed
mt021322 said:
lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconnected a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed
Click to expand...
Click to collapse
(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.
(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.[/QUOTE]
yups,,for a first time the progress still there,,but after I'm trying to root a phone using vroot (via pc) and kingroot,specially by vroot cause this process makes turbo reboot a couple time (with a failed result :silly,.now on the second time on wipe cache,the progress is gone ( it's a temporary right?it's will coming again on a mysterius time :silly i'm use Gsm/Edge for a connectivity to make a slow downloading update progress when is coming back
.
a money problems for this time to buy that license
I, too, would probably resist unlocking that particular device, since the screen is so cracked up... if you replace the phone, you'd have to get another Sunshine license for the new device.
Anyway, back to the original point, I recall on my old GalaxyS3, VZ was pushing an update that only allowed you to postpone it for some specific amount of time and/or it had a timer for the "we're going to start installing" popup, after which it would force-install. Based on that, I wouldn't be surprised to hear VZ is forcing updates, especially on an unattended phone...
There may be hope...
http://forum.xda-developers.com/droid-turbo/general/sunshine-bootloader-unlock-su4tl-49-t3445523
while collecting a money,i'm try freezing updater using adguard.apk (non root) and the result for a last two days,the update progress is gone (I don't know if that's a result from a adguard method)..
The old user of my phone said that. The .49 update was made automatically, with no Yes/No options, just updated.
I think it might be that if you don't interact with the prompt it will update your phone after a certain amount of time. When the update first rolled out I would always postpone it, telling it to remind me at 12AM cause that's when I usually go to bed. However one day, after setting it to remind me at 12, I fell asleep earlier and didn't see the prompt. The next morning, surprise, surprise, it was updated to .49.
Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
jcase said:
We just released it, 3.4.6 will unlock SunShine
Sometimes stars align and a bug becomes apparent, one that we can use.
Click to expand...
Click to collapse
ChazzMatt said:
Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
Click to expand...
Click to collapse
It is a great news for a lot of people.
Good work by Sunshine team.
In the future with any phone. If you see a update is about to happen, plug your phone to your computer, go to root of storage, and delete the download.. Hell I do this all the time... You can't miss it, it will be the only white looking item there..
And then I update it and then like next week it's another update. This has been going on for three weeks yet even though it's a security update, in the about device menu, the device security is still dated to January. What's going on here?
The MechE said:
And then I update it and then like next week it's another update. This has been going on for three weeks yet even though it's a security update, in the about device menu, the device security is still dated to January. What's going on here?
Click to expand...
Click to collapse
I had a similar problem with my S5, I finally did a factory reset on it and it updated for real, and a lot of other apps suddenly updated. It was a pain getting it set up again, but I'm glad I did.
Hello, I have a Note 8 that I have previously rooted a few months ago, then came back to stock OS. I have been wanting to install a custom rom now, but the OEM unlock switch is not in settings despite waiting a week. I rebooted into download mode, and there it shows OEM lock: off, along with RMM: Normal. I attempted to install TWRP to it, but it gets blocked with "Custom binary blocked due to remaining installment payment". I've also noticed that there is a entry in about phone > status that shows "Installment payments: Outstanding". Does that mean I have to pay off my phone fully, or pay the current balance on the carrier account? Does CRHA have the same issue? Or is there a workaround that I don't know off?
Edusa said:
Hello, I have a Note 8 that I have previously rooted a few months ago, then came back to stock OS. I have been wanting to install a custom rom now, but the OEM unlock switch is not in settings despite waiting a week. I rebooted into download mode, and there it shows OEM lock: off, along with RMM: Normal. I attempted to install TWRP to it, but it gets blocked with "Custom binary blocked due to remaining installment payment". I've also noticed that there is a entry in about phone > status that shows "Installment payments: Outstanding". Does that mean I have to pay off my phone fully, or pay the current balance on the carrier account? Does CRHA have the same issue? Or is there a workaround that I don't know off?
Click to expand...
Click to collapse
Not familiar with this message, but just based on the wording alone it sounds like your carrier blocked it until it's paid off. Maybe part of an update somewhere along the way? I would probably phone them for more info and then go from there.
sefrcoko said:
Sounds like your carrier blocked it until it's paid off. Maybe part of an update somewhere along the way? Suggest phoning them for more info.
Click to expand...
Click to collapse
It was only happening in the recent updates when the installment payment showed up in settings, but I doubt the customer service will even know what a bootloader is. Otherwise I would have to wait 2 more years to be able to unlock it, and by then I'll probably have a Note 11 or whatever is out by then. Did the CRHA firmware have that feature?
Edusa said:
It was only happening in the recent updates when the installment payment showed up in settings, but I doubt the customer service will even know what a bootloader is. Otherwise I would have to wait 2 more years to be able to unlock it, and by then I'll probably have a Note 11 or whatever is out by then. Did the CRHA firmware have that feature?
Click to expand...
Click to collapse
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
sefrcoko said:
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
Click to expand...
Click to collapse
I'll try it during the weekend then. Odd that it happens even with a unlocked CSC (BTU)
Same problem
Bought my phone off of Swappa, which they claimed was good.
To date - I have installed 2 different factory firmwares to no avail. Have the same message and same status. Get stuck on Factory Binary screen trying to run combination ROM.
Bought this phone specifically to root and use on AT&T. Glad I paid little more than 1/2 of new...and tried calling Samsung support but they are of no help!
Definitely looking forward to any suggestions on what to do, to help determine what the problem is.
Thanks in advance, as well.
---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------
sefrcoko said:
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
Click to expand...
Click to collapse
The RMM state is listed as off, not prenormal, which is what I am guessing you are referring to.
Flashing latest firmware takes this to V4 bootloader which may/may not be something OP is interested in.
Might be a bit of a bump
On the Android Pie betas for the Note8, the OEM unlock button shows, and it toggles as expected, and the installment balance entry also does not show anymore in settings. However, it still won't let me flash TWRP or any binary, showing the exact same message as above. Has a fix been found for this issue, or am I stuck unrooted? Could the S10 have the same issue?