I know AT&T hasnt released the 6.0 update yet but I just got the November LMY48Y security update. Is there anyways I can flash or manually update to 6.0? I'm on the international N6 so its not carrier locked or anything, I'm just not sure which build of Marshmallow to flash as all of them come from different builds (LM48T - MRKxxx)
none
Are you rooted? If your rooted you shouldn't be getting, nor receiving any OTA. I don't know much about the International version but as long as your rooted with an unlocked bootloader flash the version you want to. The great thing about the Nexus 6 is all the developement you see. Any other questions shoot me a PM if you want to
USMC retired said:
Are you rooted? If your rooted you shouldn't be getting, nor receiving any OTA. I don't know much about the International version but as long as your rooted with an unlocked bootloader flash the version you want to. The great thing about the Nexus 6 is all the developement you see. Any other questions shoot me a PM if you want to
Click to expand...
Click to collapse
Not rooted right now but bootloader has been unlocked since the day I got it. I just didnt know if I can flash any 6.0 build. Will have to give a try tomorrow, any problems I'll be sure to PM you. Thanks for the info man, take care.
CavyS, I'm in the same boat as you... Also, I was told that flashing from the wrong OTA could cause problems. Please let me know if you tried flashing something. I'm stuck on LMY48Y...
Thanks!
There is no OTA to flash, for the Nexus 6 that has an AT&T sim. It hasn't been released yet. If you want to go to MM (6.0), you should flash the full 6.0 image that Google released back on October 5th, which was MRA58K and then let the security updates install WITHOUT the AT&T sim installed. "N" and "R" have since been released that contain the security updates. You could probably go directly to "R" without an issue. I'm backing up all of my data tomorrow morning and flashing "MRA58R" and if I run into problems, I'll flash back to LMY48Y. From what I gather, there is no issues with FULL IMAGE of MM on the Nexus 6 with AT&T, it's that there is no OTA yet available to go from 5.1.1 LMY48Y to 6.0 MRA58? because Google or AT&T is still trying to figure it out. Personally, I'd rather flash a full, clean image than get an OTA and still have to do a factory data reset (FDR) to fix all the issues that seems to come with an OTA update, especially one as comprehensive as going from Lollipop to Marshmallow.
UPDATE: I used the NRT (Nexus Root Tool Kit) from Wugfresh and following this video, I unlocked my bootloader and installed MRA58R. It installed quickly and painlessly, although I did a complete backup of all my data using Helium before I started the process. So far, so good. I'll report back if I have any issues.
https://www.youtube.com/watch?v=Emyd6od3tGs
http://www.wugfresh.com/
BEFORE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AFTER:
And here is another tip...once you install MM on your N6, if you want to re-lock your bootloader, lock it BEFORE you put back all of your user data. On previous versions of Android, locking the bootloader did not wipe user data, but on MM, it does! I wish I had known that before I set everything up. See this thread for more info: http://forum.xda-developers.com/nexus-6/general/locking-bootloader-wipes-data-t2947916
Doesn't really matter which build.
CavyS said:
I know AT&T hasnt released the 6.0 update yet but I just got the November LMY48Y security update. Is there anyways I can flash or manually update to 6.0? I'm on the international N6 so its not carrier locked or anything, I'm just not sure which build of Marshmallow to flash as all of them come from different builds (LM48T - MRKxxx)
Click to expand...
Click to collapse
Just use any build you like from the Google Developers page https developers.google.com/android/nexus/images
On the site are various instructions on how to flash the image(s). Not that you need your bootloader unlocked (if it isn't, doing so will delete all your data, so make a backup first).
Have fun with Marshmallow!
BartmanJax said:
UPDATE: I used the NRT (Nexus Root Tool Kit) from Wugfresh and following this video, I unlocked my bootloader and installed MRA58R. It installed quickly and painlessly, although I did a complete backup of all my data using Helium before I started the process. So far, so good. I'll report back if I have any issues.
https://www.youtube.com/watch?v=Emyd6od3tGs
http://www.wugfresh.com/
BEFORE:
AFTER:
And here is another tip...once you install MM on your N6, if you want to re-lock your bootloader, lock it BEFORE you put back all of your user data. On previous versions of Android, locking the bootloader did not wipe user data, but on MM, it does! I wish I had known that before I set everything up. See this thread for more info: http://forum.xda-developers.com/nexus-6/general/locking-bootloader-wipes-data-t2947916
Click to expand...
Click to collapse
@BartmanJax, is your N6 on AT&T still working smoothly. I heard of some issues with reboots and/or dropping connection when going to MM. If you are not having issues I'm going to use the WUG RootKit and do the same!
Genghis1227 said:
@BartmanJax, is your N6 on AT&T still working smoothly. I heard of some issues with reboots and/or dropping connection when going to MM. If you are not having issues I'm going to use the WUG RootKit and do the same!
Click to expand...
Click to collapse
Working perfect! No issues at all!
And I learned a trick this morning when I flashed my N7 (2013) with a fresh image. You don't have to do an OEM Unlock first by clicking the OEM Unlock button on NRT. It will be done for you automatically if you follow the steps below.
First, make sure your have USB Debugging turned on on your N6 AND have your USB connection set to PTP. (Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check PTP box).
With your N6 connected, launch NRT, answer the questions about YOUR model and the current build (probably Nexus 6 (Moto XT1100, XT1103) for your device and for the build, probably SHAMU-SHAMU: Android 5.1.1 - Build LMY48Y). Make sure your information is correct for what is CURRENTLY on your phone). NRT will want to download some files. Let it. It only take a minute or so on a high speed connection.
When you get to the main NRT window as shown here, click on "Flash Stock + Unroot" shown here highlighted.
On this next screen, just click OK.
Assuming you're on the AT&T network using a Nexus 6, on this screen, select MRA58R (MMB29K if you want to go straight to 6.0.1) in the drop down and in the "Choice" section, select Automatically download and shown in this image. This is what you will be adding to your phone. The new image. Then click OK.
That's all you have to do. If the phone is connected to your computer correctly and is communicating with the computer, it will automatically launch the bootloader and ask you if you really want to unlock the phone, That takes an action from you (Volume up button once to "Yes" and then the power button to select). When you do this, you have to go back into the phone (skip all those annoying steps) to get to the home screen and go back to Settings > About Phone > press on the Build 7 times to get the Developers Options and turn on USB debugging again and your also have to go back to PTP. NRT will guide you through the steps. It will then automatically download the MRA58R .tgz file, unzip it, push it to your phone and install the new image. It's truly painless.
Once everything is done, if you want to OEM Lock your phone, do it BEFORE you start putting your data back.
One side note. After you unlock the phone the first time and you have to go in to turn on USB debugging AND after you install 6.0, both of the those boot times are long (maybe 5-10 minutes). Don't worry. After 6.0 is installed and booted up the first time, subsequent boots are much faster. And shutdown is very fast in 6.0.
Will give it a try tonight probably. Thank you!
Sent from my Nexus 6 using Tapatalk
Genghis1227 said:
Will give it a try tonight probably. Thank you!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you do, let me know how it goes. Good luck! :good:
BartmanJax said:
Working perfect! No issues at all!
And I learned a trick this morning when I flashed my N7 (2013) with a fresh image. You don't have to do an OEM Unlock first by clicking the OEM Unlock button on NRT. It will be done for you automatically if you follow the steps below.
First, make sure your have USB Debugging turned on on your N6 AND have your USB connection set to PTP. (Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check PTP box).
With your N6 connected, launch NRT, answer the questions about YOUR model and the current build (probably Nexus 6 (Moto XT1100, XT1103) for your device and for the build, probably SHAMU-SHAMU: Android 5.1.1 - Build LMY48Y). Make sure your information is correct for what is CURRENTLY on your phone). NRT will want to download some files. Let it. It only take a minute or so on a high speed connection.
When you get to the main NRT window as shown here, click on "Flash Stock + Unroot" shown here highlighted.
On this next screen, just click OK.
Assuming you're on the AT&T network using a Nexus 6, on this screen, select MRA58R in the drop down and in the "Choice" section, select Automatically download and shown in this image. This is what you will be adding to your phone. The new image. Then click OK.
That's all you have to do. If the phone is connected to your computer correctly and is communicating with the computer, it will automatically launch the bootloader and ask you if you really want to unlock the phone, That takes an action from you (Volume up button once to "Yes" and then the power button to select). When you do this, you have to go back into the phone (skip all those annoying steps) to get to the home screen and go back to Settings > About Phone > press on the Build 7 times to get the Developers Options and turn on USB debugging again and your also have to go back to PTP. NRT will guide you through the steps. It will then automatically download the MRA58R .tgz file, unzip it, push it to your phone and install the new image. It's truly painless.
Once everything is done, if you want to OEM Lock your phone, do it BEFORE you start putting your data back.
One side note. After you unlock the phone the first time and you have to go in to turn on USB debugging AND after you install 6.0, both of the those boot times are long (maybe 5-10 minutes). Don't worry. After 6.0 is installed and booted up the first time, subsequent boots are much faster. And shutdown is very fast in 6.0.
Click to expand...
Click to collapse
I remembered I had to do OEM unlock in developer menu... Did you do this before anything?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:35 PM ---------- Previous post was at 10:42 PM ----------
Just finished the update to MM and everything so far is very smooth. The only thing I would say is to enable the Allow OEM Bootloader Unlock before pushing the Flash Stock + Unroot. Makes it that much quicker so that you don't have to boot back into the device and enable it later. Otherwise, setting up the apps and then going to put the SIM back on. Will report back if I get any issues while using it on the AT&T network when I put my SIM back on.
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
---------- Post added at 07:49 AM ---------- Previous post was at 07:36 AM ----------
Genghis1227 said:
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
Click to expand...
Click to collapse
After a second reboot I now have LTE.
Genghis1227 said:
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
---------- Post added at 07:49 AM ---------- Previous post was at 07:36 AM ----------
After a second reboot I now have LTE.
Click to expand...
Click to collapse
Excellent! :good:
Anybody try the 6.0.1 update and use the no wipe mode?
Looks like the 6.0.1 released https://developers.google.com/android/nexus/images
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Genghis1227 said:
Anybody try the 6.0.1 update and use the no wipe mode?
Looks like the 6.0.1 released https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Perhaps will it OTA with pulling the SIM?
Genghis1227 said:
Anybody try the 6.0.1 update and use the no wipe mode?
Click to expand...
Click to collapse
Yep! I did yesterday morning. I went from MRA58R to MMB29K using the No Wipe Mode and it seems to have worked fine. Luckily, I had not locked my bootloader from the previous install of 58R. If I had, then it wouldn't have mattered since you wipe the phone as soon as you unlock the bootloader.
29K is working fine on my N6 on AT&T.
Genghis1227 said:
Perhaps will it OTA with pulling the SIM?
Click to expand...
Click to collapse
Probably not. AT&T is driving the release of OTA's, just like Verizon, Sprint and T-Mo is driving the release of OTA's of phones on their network.
So because you left the bootloader unlocked it just basically upgraded (aka sideloaded the OTA) right? Data and everything else intact? I'm just going to keep it unlocked from now on. AT&T is horrible at updating.
Genghis1227 said:
So because you left the bootloader unlocked it just basically upgraded (aka sideloaded the OTA) right? Data and everything else intact? I'm just going to keep it unlocked from now on. AT&T is horrible at updating.
Click to expand...
Click to collapse
Correct! Just be sure and select the "No Wipe Mode." I decided to leave mine unlocked as well. Makes updates easier. I don't really want to leave the bootloader unlocked, but like you said, AT&T is horrible at updating.
Related
Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse
lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse
OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse
lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse
and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.
There are a lot of people joining xda on daily basis, and there are a lot of repetitive questions being asked which fill up Development threads. Point them here. Feel free to ask or answer questions. Idea of this thread is to get users to help other users with their problems/questions. Please do not spoon feed, but rather point in the direction where that user can find an answer and educate himself
First thing first. I strongly advise you to read THIS thread before posting ANYTHING on XDA.
Then, have a quick look at the names of threads in post no2, you might find what you need right away.
For ROM issues please do mention in your post about:
ROM name
ROM version and base
kernel version and its settings
any mods applied on top of it
flashing "style" aka dirty or clean
something like this
...and be sure you have asked before on the ROM thread unless you have less than 10 posts on XDA
Third. Even if you do get your question answered, please, do come back and read threads in post no2 (coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time and frustration it will save you in the future.
ASK ANY QUESTION HERE,adb, drivers, superCID etc...... You will either get an answer or will get pointed in the right direction.
No abuse towards noobs tolerated here! No question is stupid in this thread.
***I feel that a little OT is healthy to the success of this type of thread. The people here who help the most will develop a comradery therefore OT is allowed within reason. Common sense will be applied ***
Credits to @xanthrax who made the original nexus 4 thread where i got inspired! :highfive:
Great idea!!! And well needed! :good::good:
Darth said:
Great idea!!! And well needed! :good::good:
Click to expand...
Click to collapse
Thanks i hope we can fill this up quickly! Just share it!
Enviado desde mi XT1060 mediante Tapatalk
Sorry I am a noob.
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
yes, you will get the update. but the installation fails
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
4yush said:
Currently i am using kitkat 4.4.4.
I wanted to know if i Root my phone will i get the lollipop update that will be officially launched for the phone ??
Click to expand...
Click to collapse
To root on 4.4.4 you need an unlocked (or unlockable) bootloader. An unlocked bootloader phone roots by flashing custom recovery.
If you try to take an OTA without stock recovery on your phone, you'll get stuck in a bootloop (fastboot earase cache will get you out of it), and can not apply an OTA. Further, if while rooted you modify /system, certain files, or other parts of the phone too much while rooted, the OTA could fail its pre-flash validation checks, thus preventing it from installing.
Then again, those who use SlapMyMoto/RockMyMoto/PwnMyMoto or other HACKS to root their phone with locked bootloader, could also run into issues with the OTA's pre-flash validation checks causing the OTA Update to fail too. However, those old processes don't work on 4.4.4 as the vulnerabilities they used are patched.
If you have an unlocked bootloader, root your phone by flashing TWRP (or CWM, etc) and installing SuperSU, then flash stock recovery back on, and run rooted with apps installed that use root, like RootExplorer, Wifi Tether for Root, Greenify, etc. You can take the OTA just fine.
Note: If you install something like Xposed, it will cause the Pre-flash vaildations to fail because it does modify things the pre-flash checks look for. You'd have to disable it, which involves having 3rd party recovery, and flashing the disable.zip (on your phone as /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip), then put stock recovery back on.
adity said:
I have got tired of waiting for official update and have decided to root my moto x on 4.4.4.
This is what I understood.
1 . unlock bootloader
2. Install twrp
3. Install rom.
I would want to know if I can flash BlissPop directly after the above steps.
Also can kernels be flashed directly from recovery or they have to be flashed using pc like my xperia did
Click to expand...
Click to collapse
If BlissPop is a custom ROM then yes after all of those steps you can flash it directly, I'll suggest to make a nandroid backup before. And then to get some gapps for that ROM. And kernels can be flashed directly on recovery too! Good luck!
Enviado desde mi XT1060 mediante Tapatalk
Should this have to be sticky?
Enviado desde mi XT1060 mediante Tapatalk
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adity said:
Using blisspop which is based on cm12 and mobile standby is using abnormal amounts of battery(75%)
Click to expand...
Click to collapse
I think battery life on custom ROM is very bad compared to stock, I'm back at it because of that and for moto features.
Enviado desde mi XT1060 mediante Tapatalk
Making a bump to everyone can see this post!
Enviado desde mi XT1060 mediante Tapatalk
Moto X - No Signal?
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
NadirChaudhry said:
So I got the Verizon XT1060 a couple of days back, put my SIM in and everything was working fine for a couple of days. Made a few calls, texted a bunch. Everything was good.
Never really got a chance to check how data worked since I was always on WiFi but yesterday when I tried making the mobile internet work it just wouldn't . I have a 3G connection, so I thought might as well give it a shot and started putting in the APNs in according to what my provider said. I came across a post that said you can't select just 3G for the XT1060 and you'd have to install this app called PhoneInfo(Ad) to make 3G only work.
So I installed the app. Set it to WCDMA only. And restarted the phone. Ever since then my phone has been on no-signal. Can't make calls/texts. No bars. I can read stuff on the SIM card just fine though. Today I went and got a new SIM Card hoping it'll work. But nothing. Zilch. Factory reset multiple times. Just no signal at all. In About Phone, in status information, the network shows up as unknown.
I don't exactly know what the problem is here. I talked to my provider and they said everything was fine on their end and I should check if my model is compatible. Which it is. At least for EDGE, if not for 3G. If phone was receiving signals and all before, then that definitely means it was compatible, right?
Any way. I'm based in Islamabad, Pakistan. And the phone is a Verizon XT1060 16GB. This is the only phone I have right now and I REALLY need to get this phone working asap.
I'm going to try and flash the stock image onto it. The phone was running stock VZW 4.4.4 and is not the dev edition. So I can't root.
Any suggestions or ideas are welcome.
Thank You.
Click to expand...
Click to collapse
Do you know which exactly are the bands your network uses? And I have stock ROM too and I get the 3G only option without the use of an external app. See here.
Enviado desde mi XT1060 mediante Tapatalk
Used Moto X What to look at.
Hello! (second post after saying hello on the corresponding post).
Please my native language is spanish so forgive my mistakes if any.
Going to the point and abusing the "ask ANY question" theme,
¿What to look in a Used Moto x?
In other words, here in Argentina phone are really expensive, and i have the chance to buy a Moto x really cheap.
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Also i ad one more question.
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Thanks for all your answers!
Kind Regards!
cabe72000 said:
Besides the obvious scraches, marks, screen details, and checking battery status and life. What else should i look? Any specific serial, date of production? any data?
Click to expand...
Click to collapse
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
cabe72000 said:
As far as i understood with this post http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 if i have a 4.4.4 Phone all will be useless since there is no Rooting or bootunlock.
In any other cases there is some way to get root acess and also could get bootunlock (did i understood correctly?)
Also Unlocked boot would give me the chance to install a new operating system (Cyanogen mod or whatever)
Root would only give me the chance to uninstall app and so.
Click to expand...
Click to collapse
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
KidJoe said:
I've seen no evidence that any date range or serial number range is better than another.
One thing i would look for is... If you have the option to find out what ROM and bootloader is on the phone, that is helpful.
ROM: On the phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
Bootloader: check by Booting the X into Bootloader/Fastboot mode, and make note of the second line on the screen.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
The android version and bootloader version should match, otherwise it means someone was experimenting when they were flashing, and if you buy that phone you definitely make sure you fully flash the correct SBF onto the phone to bring everything in line. (I would ask the owner to do it BEFORE you buy, so if something goes wrong while flashing, you aren't the one bricking the phone).
Read further in that thread... like what I posted -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
So when you get your X, try to get the unlock code from Moto's web site. Then.... If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
Moto gives the bootloader unlock code for most 2013 X's, its only a few carriers they don't give them for.
For Example: While Moto doesn't give out the Unlock Code for the ATT XT1058, they do give out the unlock code for the XT1058 from Rogers in Canada. So if you are buying a used Rogers XT1058 you can unlock the bootloader for free. The same holds true with nearly every XT1052, XT1053, and XT1056 I've seen (moto gives the bootloader unlock code on their web site).
Another thing to keep in mind, IF you get a model from a carrier that Moto doesn't give out the bootloader unlock code for, If the phone and its bootloader are still on 4.4.2/30.B4 or below, you can use Sunshine to unlock the bootloader.
Unlocking the bootloader will allow you to flash 3rd party or custom Recoveries, Roms, parts, etc. (so CM12, etc) With a locked bootloader, you can only flash ROMS/Parts which have been digitally signed by Moto and are for your particular Phone Model and Carrier combo. (The CID comes into play).
Rooting will allow you some access and control over /system and other files that are usually inaccessible to normal users. It doesn't allow you to flash 3rd party roms and pieces,etc. If you have a LOCKED bootloader, you basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It , if you want root. Right now, with 4.4.4 and a locked bootloader, there are no vulnerabilities which can gain root, that is why having an unlocked or unlockable bootloader is so important. For more see -> http://mark.cdmaforums.com/MotoX-Locked.html
Click to expand...
Click to collapse
Thanks for your answer!!
Im sure that the actual owner knows nothing about Android, what im trying to say is that he didn't even know how to root or check software updates.
Besides that, what you answered to me is what i was looking for. On monday i have access to the phone so i will check everything you told me.
Tell you the news on Monday.
Muchas gracias!! (Thank you very much)
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
cabe72000 said:
EDIT: Kidjoe Where do you work to have such a list of phones??? I work on Automotive industry and i drive maybe 5 o 6 cars but your's is incredibly long! hehe (sorry offtopic but i was amazed with the list )
Click to expand...
Click to collapse
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
KidJoe said:
I've been using cell phones since 1992... There was a period in there, for personal, that I was part of a Verizon Wireless customer "focus group" known as the VerizonWireless Customer Council, so many of my PERSONAL phones were acquired that way (for free).
Long story short... I worked for one global company for just a week shy of 20 yrs. While always a field employee needing mobility to do my job, for about the last 7 or 8 years, my focus was shifted to doing a lot of work in the mobility support space. The current company I'm working for (also global), I've been a part of the Tier 3/4 Mobility Support team, supporting our network, MDM solution, etc for our employees. We also take part in the design... so I have to have all, or as many as I can, of the devices we allow our employees to have. I often times joke that my job is being paid to play with my toys
Click to expand...
Click to collapse
My wife has forbid me to get another phone for a couple years.... Lol
Moto X, N5 and M8 in a year. Though, she's in love with the hand me down moto X... It finally got her off her iPhone 4s. So she benefited from my whims.
So I'm stuck for awhile. ?
I did find a solution to the battery problem.
Thing is google keeps data on even when wifi is connected for the handofff feature. So I make sure that I turn off data while at home.
Since then I have been having great battery life.. Even better than stock, more than 4 hours screen time
[Edit 4/4/2015]: Solved: Apparently the previous owner installed a custom kernel (without changing the kernel version) in order to disable encryption. Fixed via unlocking/wiping/rooting/installing a 5.1 ROM from XDA, and setting up my phone again from scratch. Thank you to everyone who posted. See this post for my process.
-------------------------
Original post:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
This is the second time I've, personally, seen this reported. Was your device purchased from T-Mobile or another source?
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
simms22 said:
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
Click to expand...
Click to collapse
He couldn't have changed any system files. He's not rooted.
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Paul22000 said:
The picture explains all.
http://i.imgur.com/C9GhN3y.jpg
WHAT in the F!!!!!!!!!!!!????????????????
Click to expand...
Click to collapse
Which drivers are you using. Are you using mfastboot for sideload. I've heard that works better.
Evolution_Freak said:
This is the second time I've, personally, seen this reported. Was your device purchased from T-Mobile or another source?
Click to expand...
Click to collapse
I purchased it from Amazon in "Like New" and "Perfect condition", which indeed it was. I've been using it for a month now without a single issue whatsoever.
A) What does the above error message mean, and how can I install 5.1 without wiping?
Edit: B) What was the solution for the other case that you saw this?
simms22 said:
if you have changed any system files, any at all, then you cant flash the ota, not even if you sideload it.
Click to expand...
Click to collapse
I have not changed a single thing. Absolutely nothing. How do I install 5.1 without wiping?
toknitup420 said:
He couldn't have changed any system files. He's not rooted.
---------- Post added at 02:53 PM ---------- Previous post was at 02:53 PM ----------
Which drivers are you using. Are you using mfastboot for sideload. I've heard that works better.
Click to expand...
Click to collapse
Exactly. I haven't changed anything. Recovery is stock as well.
I was using "adb sideload" and I installed the newest drivers straight from Google as of 45 minutes ago. "Adb devices" in recovery was clearly showing my device right before entering the "adb sideload" command.
What is mfastboot? And do you think it will overcome this error?
Paul22000 said:
I purchased it from Amazon in "Like New" and "Perfect condition", which indeed it was. I've been using it for a month now without a single issue whatsoever.
A) What does the above error message mean, and how can I install 5.1 without wiping?
Edit: B) What was the solution for the other case that you saw this?
I have not changed a single thing. Absolutely nothing. How do I install 5.1 without wiping?
Click to expand...
Click to collapse
Here's the link to the other thread:
http://forum.xda-developers.com/showthread.php?t=3069402
What is your current software version? Is it LRX22C or something else? I'm asking because I want to be sure that when you tried to sideload, you used the proper one for the software version you have/want.
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Also, it is possible that the person who owned it before you made alterations that were not completely removed before you purchased it.
Evolution_Freak said:
Here's the link to the other thread:
http://forum.xda-developers.com/showthread.php?t=3069402
What is your current software version? Is it LRX22C or something else? I'm asking because I want to be sure that when you tried to sideload, you used the proper one for the software version you have/want.
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Also, it is possible that the person who owned it before you made alterations that were not completely removed before you purchased it.
Click to expand...
Click to collapse
Yes LRX22C. I used this one: LRX22C to LMY47M for T-Mobile http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
How can I investigate to see what the first owner changed? I don't want to wipe and find out it still doesn't work. And just for my knowledge, I do want to find out exactly what is the cause or changed files.
can always flash the factory img via fastboot, while the device is in its bootloader.
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
It's also possible that the prior owner unlocked, rooted, changed something and then unrooted+relocked, but seems a low probability.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time . . . btw, I took both the OTA and did a fastboot process - the latter process was easy, just took some time to do safely.
- ooofest
simms22 said:
can always flash the factory img via fastboot, while the device is in its bootloader.
Click to expand...
Click to collapse
This would also be my suggestion. However there is no factory image for LMY47M so you would have to use LRX22C and then apply the "M" version again via sideload.
ooofest said:
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time, so I suppose checking to ensure you have the correct image for sideloading is your next step (per Evolution_Freak).
- ooofest
Click to expand...
Click to collapse
na.. you could buy a n6 from verizon, put in a tmobile sim, and get the update(for tmo). updates are related to your sim card, not to where you bought the n6. the ota is still controlled by google, not the carrier.
ooofest said:
I wonder if this might partly be related to having a T-Mobile SIM and being purchased from Amazon - because the OTA is controlled by the carrier but perhaps they still have an IMEI check during the process. It seems unlikely, but my only guess at this time.
It's also possible that the prior owner unlocked, rooted, changed something and then unrooted+relocked, but seems a low probability.
A good test might be to remove the SIM, factory wipe and then bootup to see if the current Google OTA (to 5.1 "D") happens during the impending setup. But, you don't want to wipe at this time . . . btw, I took both the OTA and did a fastboot process - the latter process was easy, just took some time to do safely.
- ooofest
Click to expand...
Click to collapse
I'm also wondering if this is a possibility. If you check the other thread I linked, the user was on T-Mobile with a Google play purchased device.
Evolution_Freak said:
This would also be my suggestion. However there is no factory image for LMY47M so you would have to use LRX22C and then apply the "M" version again via sideload.
Click to expand...
Click to collapse
Can you link me to the proper method for doing this? Will this cause a wipe?
simms22 said:
na.. you could buy a n6 from verizon, put in a tmobile sim, and get the update(for tmo). updates are related to your sim card, not to where you bought the n6. the ota is still controlled by google, not the carrier.
Click to expand...
Click to collapse
Maybe it's a terminology thing for me, then: Google controls their OTA (at "D" for the Nexus 6 right now, it appears), but the Verizon SIM was apparently holding my phone back from getting an update notification. So, I think you said the same thing and maybe I didn't express myself clearly before.
However, doesn't the T-Mobile OTA put their enabled phones at 5.1 "M"?
- ooofest
ooofest said:
Maybe it's a terminology thing for me, then: Google controls their OTA (at "D" for the Nexus 6 right now, it appears), but the Verizon SIM was apparently holding my phone back from getting an update notification. So, I think you said the same thing and maybe I didn't express myself clearly before.
However, doesn't the T-Mobile OTA put their enabled phones at 5.1 "M"?
- ooofest
Click to expand...
Click to collapse
m is "supposedly" for tmobile devices, but it seems as any of the updates work on any carrier. right now im on the 47I version, while on tmobile, while volte is working on my device properly. i was on m last week though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simms22 said:
m is "supposedly" for tmobile devices, but it seems as any of the updates work on any carrier. right now im on the 47I version, while on tmobile, while volte is working on my device properly. i was on m last week though
Click to expand...
Click to collapse
Yeah, I had "D" (via no-SIM+factory reset OTA) before E (via fastboot) on Verizon with the same general capabilities.
I was just wondering out loud if these supposedly carrier-specific updates might actually be installing to phones on their respective networks via OTA, because the T-Mobile Nexus 6 page seems to imply that their subscribers get "M". In that case, that might lend further credence to the idea that OTAs are more particular, based on your SIM (at the very least), but maybe there's other criteria at this time, too (like, white-listed IMEI).
- ooofest
Paul22000 said:
Can you link me to the proper method for doing this? Will this cause a wipe?
Click to expand...
Click to collapse
Yes, installing a factory image requires unlocking the bootloader which wipes your device. There's a thread in the general forum that explains all of this.
---------- Post added at 03:41 PM ---------- Previous post was at 03:38 PM ----------
Based on the info that @simms22 provided above, I would suggest first trying to sideload LRX22C to LMY47I first. If it fails again, then I would suggest the factory image route.
Paul22000 said:
Can you link me to the proper method for doing this? Will this cause a wipe?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59853083&postcount=6
thacounty said:
http://forum.xda-developers.com/showpost.php?p=59853083&postcount=6
Click to expand...
Click to collapse
The user in this thread requesting help has a locked bootloader and is stock. Using fastboot to flash the images separately is not an option at this point because he doesn't want to wipe to unlock.
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