My N6 is still on NBD91P from November...
It is the US model (XT1103) and I am using it in Europe.
I have also enrolled in the Android Beta Program more than 24hrs and still no new update?!?!
The phone is not rooted.
Any ideas why does it take so long to get and how can I OTA 7.1.1?
I also tried Opera VPN to switch the region to USA and still no update.
Any input is appreciated.
Many thanks!
I also have not received the 7.1.1 update. I did get a January update of NBD 91X which is still 7.0.
Sent from my Nexus 6 using XDA-Developers Legacy app
Yes but you received the January update I'm still on November...
Any thoughts?
Thanks
I really have no idea why people with a Nexus phone wait for the OTA update. You can download and install the OTA from here (instructions included at the top of the link) or download the image file from here and install it using fastboot by following the instructions under "==> Method 2 : (Long, but works always)" found here (Note: If flashing the image files using fastboot skip flashing userdata.img unless you want to lose your data).
There's no reason to wait for an OTA when you can get the factory OTA and Factory image directly from Google.
Looking for a way without having to go through all this...
I haven't installed ADB, drivers or anything on my PC and have no time to deal with this.
Had done it before on Xperia phones and took a bunch of time...
I agree with alryder. Since Google started issuing OTA full images about a year ago I've been using them on my rooted N6 with no problems and no data loss. Google have also just released separate Fastboot & ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) which make it incredibly simple. Plug in your N6 and Windows will automatically install the drivers (if not, you can use the driver functionality of Wugfresh's excellent Nexus Root Toolkit to install and check them). After that it's just a case of copying the OTA to your ADB/Fastboot directory, opening a command window, installing TWRP and using it to sideload the OTA. 15 minutes end to end.
Yes, I know that learning it is a bit of a rigmarole, but I'm guessing that your participation in this forum implies that you're at least minimally interested, and the time spent is well worth it to have the latest security updates.
Or, if you really can't be bothered, why did you comment at all rather than just waiting for the OTA to be delivered? I don't mean this unkindly, I just don't get why you post in a technical forum "I can't be bothered with all this"...
Make sure your not in the beta program. I didn't get Dec and Jan updates until I unenrolled.
I alos am on the november update, no avail with the ADB drivers, not even on linux, it detects the phone on after the procedure but once I boot adb reboot bootloader, nor linux or windows detect the phone, I tested on 2 windows 10 machines, a windows 7, and a Linux laptop
dahawthorne said:
I agree with alryder. Since Google started issuing OTA full images about a year ago I've been using them on my rooted N6 with no problems and no data loss. Google have also just released separate Fastboot & ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) which make it incredibly simple. Plug in your N6 and Windows will automatically install the drivers (if not, you can use the driver functionality of Wugfresh's excellent Nexus Root Toolkit to install and check them). After that it's just a case of copying the OTA to your ADB/Fastboot directory, opening a command window, installing TWRP and using it to sideload the OTA. 15 minutes end to end.
Yes, I know that learning it is a bit of a rigmarole, but I'm guessing that your participation in this forum implies that you're at least minimally interested, and the time spent is well worth it to have the latest security updates.
Or, if you really can't be bothered, why did you comment at all rather than just waiting for the OTA to be delivered? I don't mean this unkindly, I just don't get why you post in a technical forum "I can't be bothered with all this"...
Click to expand...
Click to collapse
As I said, Nexus Root Toolkit has an excellent walk-through of setting up Windows drivers. Many senior members don't approve of it, but it's a superb piece of work, and the driver setup is detailed and comprehensive.
shooter40sw said:
I alos am on the november update, no avail with the ADB drivers, not even on linux, it detects the phone on after the procedure but once I boot adb reboot bootloader, nor linux or windows detect the phone, I tested on 2 windows 10 machines, a windows 7, and a Linux laptop
Click to expand...
Click to collapse
Why cross post? I've answered you in the other thread you posted about this problem... (for the curious: use fastboot in bootloader mode, not ADB).
MrPib said:
Make sure your not in the beta program. I didn't get Dec and Jan updates until I unenrolled.
Click to expand...
Click to collapse
I was not enrolled in the beta program. I ended up enrolling in it to try and fix my phone. I had same as OP, last update showing in November.
I did not have a working PC at the time and had not rooted a phone since the Note 2. Called Google Fi support, and I was told that my phone was indeed a bit behind the times. I was on 6.x. Support told me to use a PC an push the most recent version...
Happily, I went to root it and used Wugfresh's sweet lil package. Easy as balls to root, and now running 7.1.1.
Kind of glad it worked out this way, I never would have rooted it if not for running into this problem.
I still have the same problem. I was in beta program and in December i was un-enrolled and i receive the November update only. Till then i didn't receive any update.
My phone is all stock not rooted. Why?
I bought my N6 second-hand and checked that it is not rooted (using app from playstore) also checked the IMEI (online) and it does correspond to XT1103 (N6 US). I also do not have the original USB cable that came with it.
My worry to sideload update it is that I might mess something up as I don't know what the previous owner had done to it. Is there a risk in this case to sideload and also doing so without the original USB cable?
Many thanks
P.S. N6 is US version I live in Europe
Make sure the cable isn't a charge-only cable. Other than that, if you're concerned you may run into an issue unlock the bootloader first, then update.
Strephon Alkhalikoi said:
Make sure the cable isn't a charge-only cable. Other than that, if you're concerned you may run into an issue unlock the bootloader first, then update.
Click to expand...
Click to collapse
How can i determine if a cable is charge only? If i unlock the bootloader and sideload will i still keep my data/settings?
Thanks!
That's the problem. You can't. However, a cable from another phone will be guaranteed to work. Unlocking the bootloader will wipe data.
@ursidae1
Is your phone now properly yours? I mean, is it your own Google account on it, not the previous owner's? If so, there should be no problem with unlocking the bootloader (as Strephon says, you'll completely wipe the phone, so back up photos, etc. to your PC before you do it), and then installing TWRP and sideloading the OTA from here: https://developers.google.com/android/ota#shamu
After that, root if you want to, and then start the long process of restoring & configuring...
I have the same issue that my Nexus 6 got no OTA notification for Dec and Jan monthly security OTA update or 7.1.1 OTA. I wonder whether I will not receive any Jan OTA since the monthly security patch is still on Nov? I thought it would be over for the Dec OTA patch rollout and Google should have already send Dec OTA for all Nexus 6 devices since the Jan OTA patch has been released. Can anyone explain the rule about OTA rolling out and why there was a delay in receiving it?
Just download the OTA and flash it yourself, as mentioned in post 4 of this very thread. Seriously folks, if you're waiting for updates on a Nexus device you're doing it wrong.
Related
hey guys, Im a total NOOB to all these things. was using iphone before now shifted to android. Let me start from first. i got a nexus 6 1 mnth bak. So as soon as i got it, i put it for 5.1 update. hours later update got downloaded and i clicked install. then halfway thru the updating it said error and it started to restart. then it kept on bootlooping to the android optmisation screen. I cudnt do anything else. tried doing wipe cache, factory reset- nothing worked. SO i replaced my phone for a new nexus 6.
Now iM Totally scared to update it to 5.1 OTA. iM Ccurrently running android 5.0 build- LRX21O. I Have not rooted my phone. sO Can u please tell me whether i can update to 5.1 directly from 5.0 thru nexus roottoolkit as i dont want to do the hard way by entering commands which i think i will mess it up. or rootkit is just for rooting and unrooting phone? CAN u please give me a guide on how to update it to 5.1. i dont want to root it.
please guys, im a total noob to all this. please excuse if i dont know stuff. i used to jailbreak my iphones and ipad and do all kinds of stuff. but since im knew i dont know many things in android.
thank u so much guys
First thing to do is to unlock your bootloader. That way, if anything goes wrong, at any point, you are almost 100% able to restore your phone again. It's also a good idea to flash TWRP (custom recovery).
You can update through NRT, or as a lot of us recommend fastboot. It's not as scary as it looks, and it's actually easier to mess stuff up with a toolkit if you have no idea what said toolkit does in the background (hint: it's using the commands).
It's a good idea to read, read and then read some more. If you have a basic understanding of things it's easier to get things done correctly. Start off by reading the FAQ-thread, lots of good info there.
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Didgeridoohan said:
First thing to do is to unlock your bootloader. That way, if anything goes wrong, at any point, you are almost 100% able to restore your phone again. It's also a good idea to flash TWRP (custom recovery).
You can update through NRT, or as a lot of us recommend fastboot. It's not as scary as it looks, and it's actually easier to mess stuff up with a toolkit if you have no idea what said toolkit does in the background (hint: it's using the commands).
It's a good idea to read, read and then read some more. If you have a basic understanding of things it's easier to get things done correctly. Start off by reading the FAQ-thread, lots of good info there.
http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Click to expand...
Click to collapse
thanks for ur reply. Wil do it in fastboot mode only. i will read more about it., One last question. Can i flash to 5.1 directly from 5.0? or to flash to 5.1 i need to update it to 5.0.1( since most of the forums said this). aLSO There are 3 shamu factory images for 5.1 LMY47D, 47E, 47I. Which one should i use?
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
yeshwanter said:
thanks for ur reply. Wil do it in fastboot mode only. i will read more about it., One last question. Can i flash to 5.1 directly from 5.0? or to flash to 5.1 i need to update it to 5.0.1( since most of the forums said this). aLSO There are 3 shamu factory images for 5.1 LMY47D, 47E, 47I. Which one should i use?
Click to expand...
Click to collapse
Didgeridoohan said:
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
Click to expand...
Click to collapse
I concur. Get all you drivers working. Figure out fastboot. There are many different ways to set up adb/fastboot. There is the right way or the fast way. Both work. Can always upgrade so the full SDK is available when you get hooked and have to have all the tools. lol There is a thread for 15 second fastboot. It works. Will at least be what you need to learn fastboot. When got adb/fastboot working we can walk you through the commands.
prdog1 said:
I concur. Get all you drivers working. Figure out fastboot. There are many different ways to set up adb/fastboot. There is the right way or the fast way. Both work. Can always upgrade so the full SDK is available when you get hooked and have to have all the tools. lol There is a thread for 15 second fastboot. It works. Will at least be what you need to learn fastboot. When got adb/fastboot working we can walk you through the commands.
Click to expand...
Click to collapse
ok guys, thanks for ur replies. I downloaded SHAMU lmy48i (5.1.1). im running 5.0, nexus 6 international version. let me just confirm what im going to do after this is right and tell me whether to proceed or not.
1)downloaded sdk tools. installed it. dint create a system wide directory. i opened platform tools and opened command window and typed adb version and it said android debug version 1.0.32 blh blah.
2)next i enabled usb debugging and oem unlock in developer settings of nexus 6.
3)connected my nexus 6.
4)went to platform tools and again typed adb devices. it showed my device serial number
5)then i have to enter bootloader. type fastboot devices and it should show my serial number.
6) then type command fastboot oem unlock
7)then have to run fastboot reboot
8) my bootloader is unlocked. Now i have to load it in bootloader mode.
9) then execute flash-all.
10) android will update to 5.1.1
thats all ryt? did i miss anything in this?
Didgeridoohan said:
Unless you're running T-Mobile or Project FI you should use LMY48I. Latest 5.1.1 with almost all the stagefright patches.
Edit: Oh yes... You can flash straight to the latest.
Click to expand...
Click to collapse
ok guys, thanks for ur replies. I downloaded SHAMU lmy48i (5.1.1). im running 5.0, nexus 6 international version. let me just confirm what im going to do after this is right and tell me whether to proceed or not.
1)downloaded sdk tools. installed it. dint create a system wide directory. i opened platform tools and opened command window and typed adb version and it said android debug version 1.0.32 blh blah.
2)next i enabled usb debugging and oem unlock in developer settings of nexus 6.
3)connected my nexus 6.
4)went to platform tools and again typed adb devices. it showed my device serial number
5)then i have to enter bootloader. type fastboot devices and it should show my serial number.
6) then type command fastboot oem unlock
7)then have to run fastboot reboot
8) my bootloader is unlocked. Now i have to load it in bootloader mode.
9) then execute flash-all.
10) android will update to 5.1.1
thats all ryt? did i miss anything in this?
Looks good. If going to use flash-all.bat make sure SDK platform tools are updated to Version 23+ in SDK Manager. Can also unzip the file a second time and do each image separately. Will find more use for the individual files later.
Looks good.
Quick advice: remember that unlocking the bootloader and flashing the factory image will completely wipe your device. If you've had time to accumulate some data on there that you want to keep, make sure to back it up first.
In the future, if you decide to root or use a custom recovery, you won't be able to take OTA updates (it checks for a tampered system). It's quite easy to update anyway... Just use the same knowledge you've earned doing this and follow prdog1's advice.
Unzip the factory image a second time and flash all images except userdata.img. That way you'll get a nice new updated system without wiping your stuff.
If jumping between roms or doing a major update, it can be good to let the entire factory image flash, though. Just make sure to backup your stuff first...
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Aniket Sarkar said:
I've just taken my phone out of box, this is October 2015, and the moment I opened the phone first it started overheating and second I checked for updates and it says "software upto date".
The software is stuck at 5.0 and I don't know why I'm not receiving a single update when it's the time people are getting Android M. I've a Nexus 5 too and it's up to date to Marshmallow while this one is still stuck at 5.0 Lollipop.
I guess this has got to do something with the OTA feature and I want to fix this instead of flashing OS manually. So please tell me what to do now.
Till now after many Google searches I did twice reset of my phone and cleared data cache everything of Google Services Framework, but still nothing is helping.
Just 1 day old nonrooted nothing ever did, everything's from my side fine, just not understanding what to do.
Please please help me soon, I'm regretting buying nexus 6 now!
Click to expand...
Click to collapse
seriously?? your regretting it ??
you need patience...
patience....
patience....
I think I've mentioned that I'm not even getting 5.1, okay not even 5.0.1
Can someone please understand the level of problem I'm facing?
I've already mentioned while others are at 6.0, I'm not going anywhere ahead of 5.0
Please help!
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
im on my 3rd day on my nexus.. but im not losing hope.. im still waiting for the ota.. its on 5.1 lmy47d...
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Same, stuck on 5.1 LMY47D
google gives us factory images for a reason. if you arent patient enough to wait for an ota, just flash a factory image yourself, instead of starting threads about how you arent getting an ota. whats the point of a thread about you not getting an ota?
snoprosledneck88 said:
....I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING.
Click to expand...
Click to collapse
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
jj14 said:
Sideloading the OTA using "ADB sideload" doesn't require you to unlock the bootloader.
Unlocking the bootloader is needed if you choose to flash the factory image file instead of the OTA file
Click to expand...
Click to collapse
Your right, I'm sorry. That's what I meant to say.
Sent from my Nexus 6 using Tapatalk
I got mine today and its on android 5 Doesn't want to update either, keeps saying its up to date. Haven't done anything yet with the phone. Looking now how ADB Sideload works.
jj14 said:
Where did you buy your phone from? Are you sure it is not running a custom ROM? Is the bootloader locked?
Keep the phone connected to the internet (WiFi or cellular data), and sign into your Google Account, and wait another day. It may take a day or two to get update notification.
Edit - depending on your build#, you can download the OTA files and sideload them using ADB (don't need to unlock bootloader if that is a concern), or the faster option would be to just unlock the bootloader, and flash the latest factory image.
Click to expand...
Click to collapse
I've bought it from an online retailer Flipkart in India.
I'm sure there's no changes made in phone and it's original and is as a new nexus 6 should be. Just this software update is causing me problems
snoprosledneck88 said:
So here is something funny. I was waiting and waiting for 6.0 on my nexus 6 for days. Never came. I have friends that have the same phone on the same carrier and they had already received their updates. So frustration and being impatient had gotten the best of me and I decided i was going to side load the update. In order to do so you need to unlock the boot loader which will wipe all of your data, EVERYTHING. When the phone rebooted completely wiped i went through the initial set up and it wasn't 5 min later the 6.0 update came rolling in like no big deal. WTF. I don't know why it wouldn't find it on its own but i wouldn't. Needless to day that is what I did and ended up getting it in a round about way. Maybe give that a try if you get to impatient and at that point if it doesn't show up just side load it. Hope this helps
Click to expand...
Click to collapse
Well I'm damn impatient, if I'd 5.1.1 and waited for 6.0 I'd have definitely had some patience, but waiting from 5.0 doesn't make sense.
Anyways to the point, after listening to your story, I tried same thing, clearing cache and reset from recovery mode, but still it didn't help
Hope there's some other resolution to this now.
I suspect it was your post that I responded to, at another forum - but you have two options really
1. Unlock bootloader (wipes data), and flash latest image
2. ADB Sideload OTAs one after the other in the right sequence (see http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 for OTA URLs) - check your current build and choose a path to get to the build you want
I am having the same problem.
I am having the same problem. Have you tried resetting the phone and starting it without the sim?
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.
The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.
Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app
Hello all, I have a Nexus 6 and I'm using it on Verizon's network. I have yet to receive the Android 7.0 OTA update. Should I have gotten this already or is there something possibly wrong with my situation? I've searched online and it seems like I should have gotten the update already. I appreciate any help.
You should have had it by now (unless you have modified your phone in any way that might interfere with the OTA process)
Your best bet would be to sideload the OTA from https://developers.google.com/android/ota
Yeah, it's a bone stock Nexus 6. I got it from Amazon around this time last year, and I received the 6.0.1 OTA update and I receive the android security patch updates. Just no update to 7.0.
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
I think that there are a lot of N6 (mine is on T-mobile) out there that have not seen an OTA. I got the 6.01 November secuity patch last week. Was expecting 7.0.
I went ahead and did a sideload of the OTA 7.0. This won't break any future OTA updates, will it?
xdatastic said:
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
Click to expand...
Click to collapse
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
russ4h said:
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
Click to expand...
Click to collapse
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
xdatastic said:
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
Click to expand...
Click to collapse
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
russ4h said:
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
Click to expand...
Click to collapse
Nope, the sideload doesn't break future OTA updates (however it theoretically could if you flashed a build not intended for your carrier, however usually Google just send a 'Full OTA' which a large download to your device to get it back on the correct build).
Enjoy.
I was offered 7.0 and it took rooted
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
tbared said:
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
Click to expand...
Click to collapse
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
I joined (then left) the Beta program so i can get a stable release of 7.0 Nougat a little over a month ago. Good so far but what I'm concerned about is security patches. Ever since I got on Nougat, my N6 no longer gets OTA security patches. I'm still on the October security patch. Anyone know what's going on?
Regardless, even with a mod'd phone, I got the 7.0 nag 2 weeks ago - which spurred me to wipe everything and flash it with NRT.
alryder said:
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
Click to expand...
Click to collapse
Thanks as soon as i have some time i will reinstall and flas..
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
Hi I create a post that might help you, check it out. https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
BTW the moderator will likely move this to the questions area.
AT&T Version ?
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
rrusek said:
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
Click to expand...
Click to collapse
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
jonchance_84 said:
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
Click to expand...
Click to collapse
Same phone/firmware but I cannot get it rooted. It boot loops or gets stuck at Powered by Android logo with fast boot so at least I can re flash the stock global firmware and boot that. Seems no rooted boot loader works nicely for me. If you have any advice I would appreciate it.
i did fastboot boot_a nd boot_b with reboot but now im stuck on razer loading screen. does this mean im stuck in a bootloop?
It did turn out pretty easy.
I wiped all data, flashed the global MR1 image, booted system and took OTA update to MR2, rebooted to bootloader and flashed Arter 12 kernel, rebooted to Arter TWRP recovery, wiped Dalvik, flashed Magisk 20.1, wiped Dalvik, rebooted system >>> Profit!
Got Edxposed, Gravitybox and Greenify running and all banking apps load perfectly. It's just like the old days of modding, LOL!
Wifi is noticeably improved compared to my previous experience with the phone as well.
Total noob question
gboybama said:
took OTA update to MR2
Click to expand...
Click to collapse
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Tincan17 said:
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Click to expand...
Click to collapse
Not at all. I totally factory reset my phone and wiped everything. Flashed the latest stock factory image from Razer that I could find at the time (March 2019?). That put me on the older stock ROM, non-rooted. From there, I just booted into the system and kicked off the (as you put it) "normal" check for updates in the system options. That got me to the September version. Next, I flashed Arter's root and custom recovery kernel IMG file with the bootloader and installed the Magisk zip from TWRP recovery.
Update: Actually, it looks like the build number I'm currently running is now available on the Razer site, so flashing back to an earlier version and taking the OTA update is no longer required. You could just flash their latest system image, which they're putting out there as December 2019. (has the same exact build number as my September build) Then the Arter boot.img and a compatible Magisk zip will complete the root.
Just remember that flashing a full Razer system image in this way will erase your internal (non-SD card) storage. I lost some photos doing this.
Is there any way someone can or has a video on ho wto do this. Or maybe a similar phone thats the same.. But i can just use the specific files for my phone instead... This compared to regualr jailbreaking is like reading chinese. I switched from apple to androd rp2 and i love android way better. But these act more computer based. As far as files and stuff like that
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
scottysize said:
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
Click to expand...
Click to collapse
Try running this tool and see if it helps with fastboot. Let it run it'll boot your phone into the bootloader automatically and install all drivers.
https://forum.xda-developers.com/an...astboot-installer-tool-windows-t3999445/page1