I'm not usually one to make these kinds of pitiful noob posts, but I've been Googling and reading for the past 3 hours and have gotten nowhere.
I installed ADP1.1 JFv1.41, because this post hasn't been updated and the JFv1.43 version was cleverly hidden in another post titled "...for UK RC9 firmware!". I am now getting an ota update prompt (0.95.0000, 1 of 2 updates) frequently now, which is odd because if I'm reading the latter post correctly, ota updates should have been disabled in 1.41. I tried to confirm this in the attached changelogs, but they are inexplicably for RC30/ADP1. Someone in another forum claimed that update notifications could be turned off in the marketplace, but this is not (or is no longer) true. A few questions:
* Which images have all update prompts (current and future) disabled? Or alternately, is there some way of disabling them without reinstalling?
* On a non-dev G1, what are the differences between ADP1.1 and RC33? So far, the only thing I've been able to confirm is that ADP versions can't download protected Market apps. Are there any particular advantages? Does ADP unlock the SIM, or is that handled at a lower level?
Many thanks in advance.
Most likely you're getting updates from Market for your installed apps.
Does ADP unlock the SIM, or is that handled at a lower level?
Click to expand...
Click to collapse
It does not. SIM lock is handled by baseband (radio) processor.
jashsu said:
Most likely you're getting updates from Market for your installed apps.
Click to expand...
Click to collapse
No. Other people have encountered this issue, although I thought it was fixed in JFv1.41 and above:
" A System Update is Available.
Holiday phone update 1 of 2: This is a bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update."
Hm... I guess? I don't know. I am running RC33 1.42 now so I have never seen the dialog in question. If the update servers are sending out code to dreams that report an ADP1 fingerprint then you might want to switch to RC33. Otherwise I believe someone detailed how to kill the update process a while back.
Edit: Typo
I never got update notices on ADP1.1 JFv1.41, so I don't know why you are getting them. Sorry I can't help with that. The only thing I can think of is that maybe you need to flash one of the SPLs? Probably either the engineering one, or the hard SPL if you haven't flashed them before. That won't touch your rom, so you won't lose anything.
I have the jf holiday version, and i'm not getting update notices.
jashsu said:
Hm... I guess? I don't know. I am running RC33 1.43 now so I have never seen the dialog in question. If the update servers are sending out code to dreams that report an ADP1 fingerprint then you might want to switch to RC33. Otherwise I believe someone detailed how to kill the update process a while back.
Click to expand...
Click to collapse
Is that a typo? I haven't been able to find anything newer than JFv1.42 for RC33. (Holiday and RC9 are at JFv1.43).
Material Defender said:
Is that a typo? I haven't been able to find anything newer than JFv1.42 for RC33. (Holiday and RC9 are at JFv1.43).
Click to expand...
Click to collapse
Oops! Yes, meant 1.42 for RC33. Damn inconsistent versioning
Dont remember reading that notification of OTA's got turned off. I do know if you are using RC33 or RC9 of his that if you get an update notification and accept it that it wont install due to the update will be using the release keys and you are using the test keys.
Since the ADP firmware uses testkeys to begin with the update will work. If you dont want to keep getting the notifications Id suggest updating your phone to ADP 1.43 or letting the OTA update run.
Related
So yeah, I woke up this morning and the phone wants to go ahead and apply the update but the phone needs more charge before it will do it, so I purposefully haven't charged it for that reason until I can gather more information on this new update. Anyone have any ideas as to what it is, or does.
I have 1.6 DRC92 and its asking to update to 1.6
Nobody!!! anybody!!!
My phone already has Firmware 1.6 but its telling me it has an Android Update 1.6 approx 9.6 MB in size. Its downloaded and verified, but its waiting on my input to restart and install.
Xx_xBLADEx_xX said:
So yeah, I woke up this morning and the phone wants to go ahead and apply the update but the phone needs more charge before it will do it, so I purposefully haven't charged it for that reason until I can gather more information on this new update. Anyone have any ideas as to what it is, or does.
I have 1.6 DRC92 and its asking to update to 1.6
Click to expand...
Click to collapse
i couldn't update my fremware , can you tell me how to set the phone , let the magic update automatically
Its a small update that updates missed call notifications, nothing major.
frank_genius said:
i couldn't update my fremware , can you tell me how to set the phone , let the magic update automatically
Click to expand...
Click to collapse
The Firmware updates when you get it OTA (Over the Air) Its all depends on your carrier due to Bandwidth restrictions and what not. So you'll just have to be patient. Until then the phone will actually tell you when an update is downloaded and ready to install.
kcm117 said:
Its a small update that updates missed call notifications, nothing major.
Click to expand...
Click to collapse
Thanks for the help, I would have guessed the same, but I didn't want to go through with it if it would have made it even harder to root the phone or something, but it still installed on its own somehow.
YAY MY STORY WAS POSTED TO ANDROID GUYS!!!
UPDATED: So I had to rush home after class and give everyone that definate answer that they long. This was in my email as I finally got a STRAIGHT answer from Google to the question
"Will the people that did the manual update to Froyo still receive the OTA, and did it void the warrenty? Can I get a straight Answer?"
Hi,
The answer is yes and no, respectively. When 2.2 (Froyo) is sent via OTA, everybody will get it, including those who have already manually updated to Froyo. No, your warranty is not voided by manually updating to Froyo. But we do recommend waiting for the OTA if you're still on 2.1 / Eclair.
Cheers,
Ben
Click to expand...
Click to collapse
Origonal Post:
I found some evidence that supports, all manual user will get the OTA, even if you updated manually.
Hi all,
Thanks for the responses!
Just wanted to give a heads up that the build floating around is not the official Froyo release. You will get an automatic notification when we OTA the build, no need to manually download it. You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat...but I'd highly recommend waiting for our official release
@Bhushan4181: You will get the OTA update as long as you are connected to the internet and can communicate with Google servers.
We are striving hard to OTA the build to you ASAP, thanks for your patience!
Gaurav.
Click to expand...
Click to collapse
From what I am TOLD as long as your manual update came from GOOGLE than it is still a LEGIT and offical update, just not the final, therefor you HAVE NOT voided your warrenty, and will most likely get the OTA so don't panic
P.S Those who did the manual update(me included) I would not worry about trying to roll back to 2.1. They sent out a test build via ota to testers, and when the final build comes i'm sure EVERYONE will get the OTA as it will have a different signature and what-not. How else would they get the final build to the testers?
Beautiful. Only thing missing now is a release date :|
Good find, I think its a no brainer but confirmation is good for some folks that were worried.
yeah good to know....
krabman said:
Good find, I think its a no brainer but confirmation is good for some folks that were worried.
Click to expand...
Click to collapse
Ya even I was a little tweaked. Not saying we wouldn't be able to just flash it anyhow even if you are NON root. But there was alot of mixed answers not only here but all over the net, and some people were freaking out
ChillRays said:
Beautiful. Only thing missing now is a release date :|
Click to expand...
Click to collapse
It appears, according to the quote ' We are striving hard to OTA the build to you ASAP, thanks for your patience!' that the build is complete and it may only be the OTA to be sorted.
I hope so anyway
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Let's take a look at that again:
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Just wanted to point that out
There is no question that there must be a newer version of froyo thats coming out. I say that because every forum I visit on this site (and other sites) have people complaining that this and that doesn't work (anymore).
Paul22000 said:
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Let's take a look at that again:
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Just wanted to point that out
Click to expand...
Click to collapse
I knew there would be at least one person that would point something out to try to kill the post cause they didn't find it first. Obviously it will be newer. The file that was MANUALLY downloaded was available to the media and what not, so what, they are never gonna get the final OTA. Its common sense. And like I siad even if by what slim chance you don't get the OTA, you will be able to push it manually.
Way to try to kill a post
BTW...
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Paul22000 said:
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Let's take a look at that again:
"You will still get the automatic notification if the official release is a newer version than the one you have, so don't sweat"
Just wanted to point that out
Click to expand...
Click to collapse
lol nice one ...
I dont find any good reason to give/update the press or the "preview phones" some unfinished or still bugged version of 2.2
For what ? so that they review it (Froyo) and write down all the bad or not working things ... it makes no sense , at least for me ...
pvillasuso said:
lol nice one ...
I dont find any good reason to give/update the press or the "preview phones" some unfinished or still bugged version of 2.2
For what ? so that they review it (Froyo) and write down all the bad or not working things ... it makes no sense , at least for me ...
Click to expand...
Click to collapse
BINGO..and what when they find the mistakes...NOT FIX IT...haha, that exactly what I was saying
what about those who installed the OTA manually and then installed the custom recovery image? will they still be able to get the new OTA?
pvillasuso said:
lol nice one ...
I dont find any good reason to give/update the press or the "preview phones" some unfinished or still bugged version of 2.2
For what ? so that they review it (Froyo) and write down all the bad or not working things ... it makes no sense , at least for me ...
Click to expand...
Click to collapse
I don't claim to know what happened, but I'm damn sure there is more to all of this.
I cannot believe the degree to which Google has fumbled this Froyo release. They let us all think we might get it at I/O and look where we are now.....another week later...all anyone has gotten is a broken version.
I said it before and I'll say it again: Mickey Mouse time in Mountain View
nice find!
did anyone read this?
maybe we don't have the offical release... yet...
http://www.google.com/support/forum/p/android/thread?tid=13a3e39bb5ce4e13&hl=en
Since I'm still semi new to Android, you miss out on OTA updates if you're rooted right? Does that also mean you miss out if your bootloader is unlocked?
jblazea50 said:
what about those who installed the OTA manually and then installed the custom recovery image? will they still be able to get the new OTA?
Click to expand...
Click to collapse
I am not sure. I didn't think you could install custom recovery image without root
darkjedi said:
Since I'm still semi new to Android, you miss out on OTA updates if you're rooted right? Does that also mean you miss out if your bootloader is unlocked?
Click to expand...
Click to collapse
That would prolly be answered if you do a search
http://forum.xda-developers.com/showthread.php?p=5723511
Mod Edit: No need to flame the user.
ChillRays said:
There is no question that there must be a newer version of froyo thats coming out. I say that because every forum I visit on this site (and other sites) have people complaining that this and that doesn't work (anymore).
Click to expand...
Click to collapse
And how many of those things are 3rd party apps that still need to be updated for 2.2 compatibility?
Dude hes got a point. You posted something that had Nothing to do with the topic at hand. We all already knew the info you posted. Thats what the whole thread was about.
I have a factory unlocked n1 that ive only owned for about 3 months.
I noticed its still on FRG83 (not the latest FRF91).
Will I have to do anything special to get the 2.3 update? (Im in the UK if that makes a difference).
FRG83D is the latest, not FRF91.
mcrosmar said:
FRG83D is the latest, not FRF91.
Click to expand...
Click to collapse
Ok, well im still running FRG83 (not FRG83D)...
maxppp said:
Ok, well im still running FRG83 (not FRG83D)...
Click to expand...
Click to collapse
hopefully this will solve your problem
http://forum.xda-developers.com/showthread.php?t=844464
maxppp said:
Ok, well im still running FRG83 (not FRG83D)...
Click to expand...
Click to collapse
to get the latest available update for your phone, dial
Code:
*#*#2432546#*#*
flybyme said:
to get the latest available update for your phone, dial
Code:
*#*#2432546#*#*
Click to expand...
Click to collapse
Thanks, it came up with 'check in succeeded', but nothing else (this was 5 mins ago).
I take it that it doesnt matter that the nexus one wasnt ever offered on my network (o2 uk), and the phone actually polls google servers?
It doesn't matter at all, just have to wait patiently, or force it (as above).
Rusty! said:
It doesn't matter at all, just have to wait patiently, or force it (as above).
Click to expand...
Click to collapse
But 83D came out two and a half weeks ago, isnt that abit too long to wait?
maxppp said:
But 83D came out two and a half weeks ago, isnt that abit too long to wait?
Click to expand...
Click to collapse
Can't you just update using the link provided above?
Im in the uk, running FRG83D and expecting the 2.3 update today. (also on o2)
Could it be my simcard? It works with 3g but its quite old still...
Also do I need to register my IMEI or anything?
Rest of the phone says this.
Code:
android version
2.2.1
baseband version
32.50.00.32u_5.12.00.08
kernel version
2.6.32.9-ge9111ea
[email protected] #1
build number
FRG83
Poolmunch said:
expecting the 2.3 update today. (also on o2)
Click to expand...
Click to collapse
Good luck with that
maxppp said:
Could it be my simcard? It works with 3g but its quite old still...
Also do I need to register my IMEI or anything?
Rest of the phone says this.
Code:
android version
2.2.1
baseband version
32.50.00.32u_5.12.00.08
kernel version
2.6.32.9-ge9111ea
[email protected] #1
build number
FRG83
Click to expand...
Click to collapse
You've got a weird kernel there? And the Korean baseband... my guess is your phone has had the KT FRF91 passimg flashed at some point, which would explain your lack of update.
That is very weird!
Are there any instructions on how to flash the kernel and baseband back to UK defaults?
Also what is the KT FRF91 passimg about, is it anything dodgy / something I should be concerned about?
Edit: I sent my phone to HTC last week and it's come back with a different IMEI...i guess that explains the korean part.
It's not really dodgy, or anything to worry about, it was an easy way for European N1 owners to update to Froyo without unlocking the bootloader back in the day. It does mean you'll lag behind with updates though.
I don't think you'll be able to get back to the proper Google firmware without rooting/unlocking your bootloader due to the 0.35 HBOOT (you can check if you have this or not by turning the phone off, holding in the tackball and powering on, the second line will say either HBOOT-0.33.0012 or HBOOT-0.35.0017).
Ive got the Hboot 0.35.0017 on FRG83D, i got the FRG83 -> FRG83D OTA update when everyone else did. I dont think this is his problem
It's not a problem as such, but it will prevent downgrading to get onto the Google version.
Ok its says HBOOT 35.0017.
If i root the bootloader, can I then flash my way back to 'Default' kernels / radios?
Yes, easily, you might not even have to wipe it in fact.
You use fastboot to flash the system.img and boot.img from the FRG33 image on shipped-roms.
Ok thats great, thanks for all your help.
Just to re-cap, install android sdk / fastbook on my pc, then flash boot.img then system.img from FRG33?
Exactly, although I lied, you will have to wipe.
I forgot that unlocking automatically wipes the phone.
Hi all,
Hopefully I am asking in the right place here - it is my first question regarding the Moto X Style.
I got my phone at the end of last week. I decided to unlock the bootloader right from the off as it requires a full wipe. I see that people are seeing the Marshmallow update rolling out in Europe. My question is two fold really.
Firstly, should I receive the OTA update with an unlocked bootloader? Based on what I have read, it looks to me like I should get the update.
Secondly, what "decides" if the update is available to a given phone? When I check for a software update I get the message that the phone is up to date. I'm happy to wait a while but I am also curious how the update rolls out.
Just for extra info, the phone reports as an "XT1572" and the system version says "23.21.18.clark_reteu.reteu.en.EU reteu"
Thanks for any pointers
Just sideload the zip from this thread:
http://forum.xda-developers.com/showthread.php?p=64248551
kadopt said:
Just sideload the zip from this thread:
http://forum.xda-developers.com/showthread.php?p=64248551
Click to expand...
Click to collapse
Thanks for that, I had seen and I will use the sideload method if I don't see the OTA update soon.
My curiosity is more about the mechanics of the OTA method and why my phone does not see an update when I tell it to go and check vs others already seeing it.
user7743 said:
Thanks for that, I had seen and I will use the sideload method if I don't see the OTA update soon.
My curiosity is more about the mechanics of the OTA method and why my phone does not see an update when I tell it to go and check vs others already seeing it.
Click to expand...
Click to collapse
My device is a retfr and didn't receive the update while other users had it, so I just sideloaded it. The update seems to be universal for all eu devices.
user7743 said:
Thanks for that, I had seen and I will use the sideload method if I don't see the OTA update soon.
My curiosity is more about the mechanics of the OTA method and why my phone does not see an update when I tell it to go and check vs others already seeing it.
Click to expand...
Click to collapse
Usually the rollouts are sent on batches and not all at once. I'm not sure if the criteria they use.
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
I got the same.
Sent from my HTC 10 using XDA-Developers Legacy app
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Mispelling
nanofoxx said:
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Click to expand...
Click to collapse
Sorry for the misspelling. I meant to say "without any problems" not "without many problems". In fact, the whole update process was smooth and fast. Everything works fine. I understand, however, that everyone's setup is different and my experience should not be the absolute rule.
Nothing here on my device. Although it might be because I'm in Sweden.
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
dingnecros said:
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
Click to expand...
Click to collapse
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Maris_ said:
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Click to expand...
Click to collapse
There's a whole new Lollipop firmware on the San mobile firmware site.
Yes...problems
My tablet updated and now the OS boots super slow and then does a soft shutdown and reboots a second time. It takes more than 60 secs to get to the home screen. Anyone know how to uninstall this update?
ADRz said:
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
Click to expand...
Click to collapse
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
I also have a SM-P605V but have Verizon as my carrier. I got the notification to update today. I don't see anything on VZW site about it nor under the specific SKU on SamMobile (still has 10/15/15 as the last official update). When looking at the SM-P605 model, there are some in the list (even today's date), though they are for non-USA countries.
Even so, it looks like they are still all Android 5.1.1, so it's likely just some minor tweaks. To my understanding, you would need to pop in an activated Verizon SIM to get the update for your specific tablet, as Verizon is the one that issues it. You can also wait until it's posted on SamMobile and manually do it. https://www.sammobile.com/firmwares/database/SM-P605V/
---------- Post added at 12:02 PM ---------- Previous post was at 11:33 AM ----------
I think I found the official from Verizon: https://www.verizonwireless.com/support/samsung-galaxy-note-10-2014-update/
Software Version: LMY47X.P605VVRSDPL1
The current software update gives you the most up to date Android™ security patch on your device.
Click to expand...
Click to collapse
(I called VZW and she confirmed that it was an Android Security patch, no MM, darnit!)
Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
You should be able to flash this now that Sammobile posted it... https://www.sammobile.com/firmwares/database/SM-P605V/
I got this a couple of days ago - managed to odin flash after I put the wrong file and got the boot loader triangle a day before.
Its extremely stable and the tablets working like a dream - the only issue is no root.
Edit: I noticed a great improvement in battery management and it will charge to 100% from 30% in 4 hours before I flashed the 5.1.1 rom it took nearly 8 hours with a new(second hand) USB Flex connector and nearly 20 hours with the old usb flex connector to go from 30% to 100%.
I really like this tablet - it reminds me so much of my SM-N910F note 4.
You can root the latest firmware and also install twrp. I have a 600.
louvass said:
You can root the latest firmware and also install twrp. I have a 600.
Click to expand...
Click to collapse
did it actually do anything? or is it not worth it
graffix31 said:
did it actually do anything? or is it not worth it
Click to expand...
Click to collapse
Probably just a security update
Please excuse my silly question but I have P600 with 5.1.1 and never rooted. Do I need to install twrp before I update or it doesn't matter? Updates always make me uneasy with locking bootloader or needing new root methods.
If you just want to update then flash with Odin and the appropriate file. Try looking at sammobile.com for the appropriate rom file.
If you want root then you will need to install a custom recovery using CF auto or Twerp - the latter will NOT work on the SM-605v version as the bootloader is locked and will result in the yellow triangle and stating that the tablet has a strange recovery and that you should see a verizon technician. By installing the recovery you can then update the system or even try out new roms created by the people of this wonderful community.
Rooting will potentially stop business application with built in security from working - i.e. HSBC application, Virgin Media app and Sky Movies apps will not work on rooted phones to name a few.
I updated and rooted and everything is working ok. I had trouble with 64gb Sandisk microsd with "sd card unexpectedly removed" error. Then it mount itself back. Sometime it shows empty and asks to format and sometime it works. Also the lockscreen flicker and that usually when the card error happened. I suspect they are related and it happens only when waking up the device. The card works fine with all my other devices including my note 4 on stock 5.1.1. I'm not sure what caused it because I just used this sd card with the note 10.1 and then updated and rooted all in the same day.
Anyway, I removed the Sandisk and now I'm using 32gb Samsung and it only happened once for maybe 12 hours (could have been 100 times with Sandisk). Also, I don't notice the lockscreen flickering anymore. I will see if this problem comes back or it just that Sandisk doesn't play well my note. I have seen many people here reported similar problem with other Samsung devices for too many reasons. I don't believe file format is the issue but I'm using exFAT.