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).
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
DougYITBOS said:
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
Click to expand...
Click to collapse
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Thanks a bunch TheAxman
You said...
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
Click to expand...
Click to collapse
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
DougYITBOS said:
Thanks a bunch TheAxman
You said...
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
Click to expand...
Click to collapse
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
And btw, if this person xBeerdroiDx gives me a thanks, he is saying I did ok... If you seem to have anymore questions, his guide is one of the best....
[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]
http://forum.xda-developers.com/show....php?t=2314494
Thanks to xBeerdroiDx - For this great Startup Guide
Thanks again!
DougYITBOS said:
Thanks again!
Click to expand...
Click to collapse
Your quite welcome, if you have any other questions, feel free to ask them in the thread I gave you or mine.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
btw..this is cool, name please.
Dog: [Pitbull Sharpei Mix] Rom: Stock
TheAxman said:
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
Click to expand...
Click to collapse
ah good idea. i suppose airplane mode would accomplish the same thing as well
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
CamFlawless said:
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
Click to expand...
Click to collapse
Thank you sir, appreciate the help, and yes, good idea.
TheAxman said:
Thank you sir, appreciate the help, and yes, good idea.
Click to expand...
Click to collapse
might have been a placebo effect for me, lol.
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Click to expand...
Click to collapse
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
lilbigdude1 said:
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
Click to expand...
Click to collapse
somewhat, but as soon as you root, your phone status is custom correct? therefor how can it update? Yes, it is better to do a custom rom, but you can still stay on MDL and never get updates, freezing the samsung update will work, but I gave the easiest way in his situation.
TheAxman said:
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
Click to expand...
Click to collapse
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
texasniteowl said:
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
Click to expand...
Click to collapse
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
TheAxman said:
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
Click to expand...
Click to collapse
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
texasniteowl said:
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
Click to expand...
Click to collapse
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
TheAxman said:
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
Click to expand...
Click to collapse
if you are paranoid then there are 3 files you can freeze. i cant remember which ones, but one is att update something something, thats all i can remember.
im no help
I think everyone gets the picture.
Sent from my GT-I9505 using xda premium
I'm on the first release of 4.4. Now an update has appeared and wants me to restart. Should I do it? Can I ignore (remove) the warning? If I let it update will it screw up my well functioning ROM? Will I just have to re/root? What is the meaning of life?
Skip the last question, I was getting carried away.
It came out yesterday...its safe to go ahead and update, its only a couple MB in size...You won't lose data or anything however some people have had to re-flash superSU as well as re-flash custom recovery...nothing too difficult
This thread may be of interest to you
bobbytomorow said:
It came out yesterday...its safe to go ahead and update, its only a couple MB in size...You won't lose data or anything however some people have had to re-flash superSU as well as re-flash custom recovery...nothing too difficult
This thread may be of interest to you
Click to expand...
Click to collapse
I went to do it...got to part where CWM warned me that it was unsigned...and I chickened out. I have no idea what the update even was. Does anyone have a flashable zip (or know where the update download is stored)
You can get a flashable zip here
bobbytomorow said:
You can get a flashable zip here
Click to expand...
Click to collapse
Hey! That's very nice of you sir
Edit: what's in the update anyway?.
Nothing that I've noticed, everything seems the same...here is the official changelog
bobbytomorow said:
Nothing that I've noticed, everything seems the same...here is the official changelog
Click to expand...
Click to collapse
Anyone notice constant buffering issues.... Like in YouTube?
Anyone receive this update yet?
I took the update and my build number updated, but my baseband and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
churchey360 said:
I took the update and my build number updated, but my modem and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
Click to expand...
Click to collapse
Did you have root? Retain root after the update?
No I was unrooted stock NAE
churchey360 said:
No I was unrooted stock NAE
Click to expand...
Click to collapse
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
troyboytn said:
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
Click to expand...
Click to collapse
Were you able to obtain root after the update?
chico1983 said:
Were you able to obtain root after the update?
Click to expand...
Click to collapse
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
Worked just like you said. I tried CF-autoroot and did not work for me. Have you been able to get the hot spot mod to work?
churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
but No baseband downgrade on NG2?
Philz still the bomb?
I want to do the reverse
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
rastapapa said:
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
Click to expand...
Click to collapse
Read this might help
http://forum.xda-developers.com/showthread.php?t=2840591
This is probably stupid and already answered in another thread but I'm a noob, don't flip out on me... Let's say, theoretically, I was to accept the
NG2 update. I'm rooted with Towelroot, using Supersu and Titanium backup. I've backed up then delete almost all of my bloatware with TB and have no further use for root at the time. If I were to break root with the update, will all that stuff stay the same and be safe until I can root again? I.e. If I break root, touch none of those root apps, then root again later, will they even "know" anything happened?
Since you can't take an OTA while rooted, that won't work.
frostedunit said:
Since you can't take an OTA while rooted, that won't work.
Click to expand...
Click to collapse
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
tamiller said:
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
Click to expand...
Click to collapse
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
2WhiteWolves said:
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
Click to expand...
Click to collapse
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
Read this, might help with the upgrade. Read all of the thread.
http://forum.xda-developers.com/showthread.php?t=2840591
So far from what I have read, I have know idea where the HD Voice Icon is, and no one else does either, not unless it is known in another thread that I don't know about.
johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
You will have to first install the stock NAE tar file with odin to return your phone to a stock unrooted condition with the stock recovery. Then you can take the ota. After that you can reroot again with cf autoroot.
Now the question is can you keep the domestic sim unlock if you do this?
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.