If i update my software via official updates, do i lose my unlocked bootloader. I know via gsm you cant even update, but verizon is like an overprotective parent....
zero_1_2 said:
If i update my software via official updates, do i lose my unlocked bootloader. I know via gsm you cant even update, but verizon is like an overprotective parent....
Click to expand...
Click to collapse
I'm pretty sure that accepting the official update would brick your phone. I am new to this too but as a general rule with any device you altered don't accept any updates without researching first.
I just received a prompt to update and it says if no action is taken it will update for you. Right now the update doesn't actually do anything but if 2.3.3 is ever pushed out this could be a problem if you are not on top of it within the 3 minute time.
I have been getting that prompt on my R800x for the past month, any time I restart the phone and any time I disconnect from a WiFi Source it tells me that there is an update available. I hit "ok" to download it then does nothing and says I am up to date.
JasonKnight said:
I have been getting that prompt on my R800x for the past month, any time I restart the phone and any time I disconnect from a WiFi Source it tells me that there is an update available. I hit "ok" to download it then does nothing and says I am up to date.
Click to expand...
Click to collapse
I found on the internet how to disable the OTA prompt. I got a root explorer and modified OTACert.zip to OTAcert-bak.zip The file is located in: /system/etc/security folder
ah thanks guys. Also, is there any way to install xloud on the verizon xplay? like an apk or something. im not finding anything on teh internets
Related
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).
I was not planning on installing it but i am wondering why the phone is not even finding it.
I'm on 1.83, locked BL, rooted (gingerbreak), a few mods like sideloading, tethering, webtop, etc. And a few frozen sys apps that i did unfreeze but still not finding the update?
Have you tried the SD card option?
http://www.motorola.com/Support/US-EN/Atrix Upgrade/Atrix-Gingerbread-Update
gnahc79 said:
Have you tried the SD card option?
http://www.motorola.com/Support/US-EN/Atrix Upgrade/Atrix-Gingerbread-Update
Click to expand...
Click to collapse
I realize i have different options, just confused as to the simple OTA is not working. I heard that if the files are modded and so on that update will not install, but my phone is not finding an update period.
Are you on WIFI? I believe it is required.
demens13 said:
I realize i have different options, just confused as to the simple OTA is not working. I heard that if the files are modded and so on that update will not install, but my phone is not finding an update period.
Click to expand...
Click to collapse
No idea.
Using the official SD card option is equivalent to downloading the OTA through your phone. It's the same image file from moto. Better IMO if you've modded your phone and if you need to retry the update. With the download through your phone route I think the update file needs to be re-downloaded if the update fails for whatever reason. With the SD card route the update image stays on your sd card after reboot/update failure. Be sure to delete it after the update is applied as stated in the instructions.
I had a similar issue as well. When checking for updates my device reported "check for update was not available at this time" whether or not the update was actually available. In order to get it to come up I had to go to settings, data manager, data delivery, social applications and then uncheck sync over wifi only. I'm not sure why this mattered but after I restarted the phone and checked for updates it found it.
Hope this helps.
jruweaver said:
Are you on WIFI? I believe it is required.
Click to expand...
Click to collapse
DING
"Not available" is the error you get when the phone is not on Wi-Fi and you attempt to check for updates.
Yesterday I got a notice from Verizon on my Note 10.1 that says I have an update from Verizon. It doesn't give me the option of declining it, nor does it tell me what the heck is in the update. All it gives is a web address to a page that talks about galaxy TAB updates not note. It tells me I can defer the update for up to 5 days but I'm rooted and don't want to be un-rooted so I'm a little skeptical about this up date. Has anyone else seen this or know what it is about? The net seems to know nothing about this from all the searching I've done the last few days.
Sent from my SCH-I925 using XDA Premium HD app
ddickenson said:
Yesterday I got a notice from Verizon on my Note 10.1 that says I have an update from Verizon. It doesn't give me the option of declining it, nor does it tell me what the heck is in the update. All it gives is a web address to a page that talks about galaxy TAB updates not note. It tells me I can defer the update for up to 5 days but I'm rooted and don't want to be un-rooted so I'm a little skeptical about this up date. Has anyone else seen this or know what it is about? The net seems to know nothing about this from all the searching I've done the last few days.
Sent from my SCH-I925 using XDA Premium HD app
Click to expand...
Click to collapse
Never take an OTA update when you are rooted. Just asking for trouble. Use a program like RootExplorer or any file manager that can get root access and go into your \System\Apps folder and rename SDM.apk to SDM.apk.bak or something similar. That's the file that downloads OTA updates.
I decided to give it a shot. I updated and it does patch the frodo exploit so root does go away.
*Madmoose* said:
Never take an OTA update when you are rooted. Just asking for trouble. Use a program like RootExplorer or any file manager that can get root access and go into your \System\Apps folder and rename SDM.apk to SDM.apk.bak or something similar. That's the file that downloads OTA updates.
Click to expand...
Click to collapse
So by renaming this file it will stop bugging me to take the update? I never allow ota updates until I know what they do so I wasn't planning on taking it I just didn't see there being an option to not take it short of "defering" every 5 days and thats obviously BS.
ddickenson said:
So by renaming this file it will stop bugging me to take the update? I never allow ota updates until I know what they do so I wasn't planning on taking it I just didn't see there being an option to not take it short of "defering" every 5 days and thats obviously BS.
Click to expand...
Click to collapse
That is correct. Renaming it is the safest way so if you ever want to bring the ability back, you can. But one could delete the file as well.
Edit: thinking about this a little more, the SDM.apk rename will stop any further updates from downloading, but if your phone has already downloaded the update it may keep trying to install it. You may need to find the file and delete it as well. I'm not sure what directory it is stored in, might have to search around a bit for that info.
Ive still got root, but stock recovery was installed. Cant get cmw or casual to write over.
Tried Odin , but no go.
Sent from my SCH-I925 using xda premium
There is a procedure to fool OTA system in order to make it receive the OTA again. So you have a second chance to grab the filename and make a lot of people here happy
Update: Thanks to @Sleeepy2 we know this method works in the nexus 6 :good:
DISCLAIMER: It's an unharmed procedure, but be warned, you will change build.prop so anything (bad) should happen if you do it incorrectly, most probably a bootloop. If you have doubts, don't do it.
Needs to be rooted.
So if there is a brave enought one, the procedure is just to change two values of the /system/build.prop file to make it looks a previous android version for the OTA system.
For instance, If you have received to OTA to LMY47M your build.prop file will have these values:
ro.build.date.utc=1425686543
and
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
If you change these lines by the equivalent lines from another version of android, the OTA system will check the OTA availability with the other android version. So, If before receiving the OTA your android version was 5.0.1 LRX22C you can change both lines with:
ro.build.date.utc=1416527965
and
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
That are the LRX22C version lines.
Save build.prop file and reboot your nexus 6.
Once rebooted check for OTA updates (It will be checked as LMY47D) and download it, if it's not downloading yet (don't apply the OTA, just download it).
While it's downloading, or even after it's download, open a terminal emulator (for instance this one: https://play.google.com/store/apps/details?id=jackpal.androidterm) and execute these two commands (will ask for superuser permission):
su
logcat | grep zip
And wrote down the OTA link for us
When you finish just revert the build.prop changes done and delete the file /cache/update.zip (it's the OTA downloaded, and you don't need it), then reboot your system to leave it in it's normal situation.
Thank you very much in advance.
And, If you are kindly enough, you may check for the rest of OTAs from other android versions (the LMY47E OTA to LMY47M should be very useful too). Here are all known versions build.prop lines to play with:
Code:
LMY47M
ro.build.date.utc=1425686543
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
LMY47I:
ro.build.date.utc=1425442825
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47I/1767468:user/release-keys
LMY47E:
ro.build.date.utc=1424577649
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47E/1748839:user/release-keys
LMY47D:
ro.build.date.utc=1424322888
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys
LRX22C:
ro.build.date.utc=1416527965
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
LRX21O:
ro.build.date.utc=1415319727
ro.build.fingerprint=google/shamu/shamu:5.0/LRX21O/1570415:user/release-keys
LNX07M:
ro.build.date.utc=1414346119
ro.build.fingerprint=google/shamu/shamu:5.0/LNX07M/1543455:user/release-keys
-----
KXH21.6-F1.12:
ro.build.date.utc=1416355004
ro.build.fingerprint=motorola/shamu_factory/shamu:4.4.4/KXH21.6-F1.12/25:userdebug/release-keys
Most of them will give you old and known OTAs, but some will give new OTAs for all of us. And the final test build probably doesn't give any OTA
Thanks and best regards.
I changed by build.prop and rebooted and no update which I checked.
xpack90 said:
I changed by build.prop and rebooted and no update which I checked.
Click to expand...
Click to collapse
But you previously installed the LMY47M/E, no?
If yes, Please, wait several minutes and keep checking, you eventually must receive the OTA again before the rest of people.
Check too if build.prop file was correctly changed (sometimes a number is missing or something).
Thanks and best regards.
No sorry I thought this was for people who wanted the update not those who had it
xpack90 said:
No sorry I thought this was for people who wanted the update not those who had it
Click to expand...
Click to collapse
Don't worry and thanks for trying.
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Sleeepy2 said:
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Click to expand...
Click to collapse
First of all, thank you very much. Unfortunately that's one of the known OTAs.
You can see all known OTAs here:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
But as I said, thank you very much. You demonstrated the method works for Nexus 6 too
oops, yeah it is know. I didn't fully read and thought you just wanted confirmation that it works on the N6.
And yes it does
OK, I got the OTA you're looking for (47M) but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate for my data to get wiped for nothing ...
YankInDaSouth said:
OK, I got the OTA you're looking for but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate to for my data to get wiped for nothing ...
Click to expand...
Click to collapse
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
VivaErBetis said:
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
Click to expand...
Click to collapse
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
YankInDaSouth said:
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
Click to expand...
Click to collapse
Don't worry, the OTA will eventually show up, sooner or later. The real problem is our lack of patience
I've added the build.prop info for 5.1 LMY47I build. The OTA seems to be delivered for Australian users.
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.