Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.
Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.
OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.
Related
Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.
I updated to 4.4.2 on my Verizon Developer Edition today and now I'm having issues updating Cloud Print. The Play Store keeps telling me that the package wasn't signed correctly. Do I have any other options besides rooting, uninstalling and then reinstalling it, because it's a system app? Any clues would be really appreciated. I'd post an image, but I'm too new of a user to link to one.
FinalBabality said:
I updated to 4.4.2 on my Verizon Developer Edition today and now I'm having issues updating Cloud Print. The Play Store keeps telling me that the package wasn't signed correctly. Do I have any other options besides rooting, uninstalling and then reinstalling it, because it's a system app? Any clues would be really appreciated. I'd post an image, but I'm too new of a user to link to one.
Click to expand...
Click to collapse
I recommend the basics. Going to the settings and clearing the app cache for the play store, try factory reset (yeah i know it sucks) try downloading the app again on wifi on LTE, etc. etc.
drago10029 said:
I recommend the basics. Going to the settings and clearing the app cache for the play store, try factory reset (yeah i know it sucks) try downloading the app again on wifi on LTE, etc. etc.
Click to expand...
Click to collapse
I've tried all of it and can't seem to sort it out. Think I'll just leave it alone, seeing as I've yet to print from any if my mobile devices. I did apply the update myself and I wonder if that has anything to do with it.
Sent from my XT1060 using Tapatalk
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
jpizz said:
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
Click to expand...
Click to collapse
droid-developers doesn't even have a Verizon 4.4.2 sbf file.
Steve-x said:
droid-developers doesn't even have a Verizon 4.4.2 sbf file.
Click to expand...
Click to collapse
Sorry, I was referring to the GSM Dev Edition. Same exact problem.
jpizz said:
If you applied 4.4.2 from the files available here at XDA unfortunately you don't have the equivalent to a true OTA. The Cloud Print included with it had been modified and you will not be able to update it unless you root, delete it and reinstall it from the play store. The full image file from droid-developers.org has the exact same issue. Very frustrating punishment for those of us who weren't patient enough to wait for the OTA.
Click to expand...
Click to collapse
Alright I figured it had something to do with the fact I installed it from Zip instead of waiting for the OTA. I tried that solution and that didn't work either. When I installed it with root and the tried to install from the Play Store, it just told me "Invalid Package." So I'll wait a little while, until it's solidly rolled out and then go back to 4.4 and then flash the OTA the official way. Thanks for the confirmation on the Zip being the issue. Not having any other issues though, so I might just stick it out.
FinalBabality said:
Alright I figured it had something to do with the fact I installed it from Zip instead of waiting for the OTA. I tried that solution and that didn't work either. When I installed it with root and the tried to install from the Play Store, it just told me "Invalid Package." So I'll wait a little while, until it's solidly rolled out and then go back to 4.4 and then flash the OTA the official way. Thanks for the confirmation on the Zip being the issue. Not having any other issues though, so I might just stick it out.
Click to expand...
Click to collapse
If you have updated to 4.4.2 then you cannot downgrade back to 4.4.
Steve-x said:
If you have updated to 4.4.2 then you cannot downgrade back to 4.4.
Click to expand...
Click to collapse
Have a dev edition with an unlocked bootloader. I've already done it once to try and fix this issue.
FinalBabality said:
Have a dev edition with an unlocked bootloader. I've already done it once to try and fix this issue.
Click to expand...
Click to collapse
Well you must have manually flashed 4.4 without the 4.4 bootloader then, because RSD wont allow you to flash from 4.4.2 down to 4.4.
Be careful because if you take an update while back on 4.4 you will hard brick your phone.
mastarifla said:
Well you must have manually flashed 4.4 without the 4.4 bootloader then, because RSD wont allow you to flash from 4.4.2 down to 4.4.
Be careful because if you take an update while back on 4.4 you will hard brick your phone.
Click to expand...
Click to collapse
Yeah that's exactly what I did, that's a good point. So should I wait for Motorola to post the recovery files, and then flash that when it comes out? Would that be safer?
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
did you disable any of the bloat? that might be your issue.....
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
I did! I'll re enable it all and see if it fixes the issue
jaideng123 said:
So i keep being prompted to get the new OTA update and whenever i try to download and install it, it reboots goes to the install screen, gets about 1/4 of the way through, says error and then reboots to an update unsuccessful page
After digging around my phone i also noticed it says my software was modified on the status page
But obviously ive never rooted this phone as its pretty much impossible at the moment
Has anyone experienced something similar and found a way to fix it?
Click to expand...
Click to collapse
Try a factory data reset but you will wipe your phone and lose all data and apps.
xbxjunkie said:
did you disable any of the bloat? that might be your issue.....
Click to expand...
Click to collapse
That's odd, I even blocked the OTA via adb and mine says official.
OK i tried both, neither worked, also when i boot into recovery i get qe 1/1 at the bottom left side of my screen
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
jaideng123 said:
Decided to just get a replacement from motorola since I'm still under warranty, but thank you for the suggestions!
Click to expand...
Click to collapse
You could just flash the stock ROM again!
Gundabolu SC said:
You could just flash the stock ROM again!
Click to expand...
Click to collapse
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
LatencyXXX said:
I am unable to obtain the moforoot util to do this. When I put in my ID on the moforoot page, it says my device is not supported. I know for a fact the model and current OS on it. Its 5.1 updated already which is probably why the website is rejecting my request to obtain the util.
I do not think the bootloader will allow me to downgrade. If anybody has a solution, please let me know.
Note: Using XT1254 w/ latest 5.1 update from Aug-Sept.
Click to expand...
Click to collapse
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
TheSt33v said:
If you want to flash an official update that is greater than or equal to the version you're on now, you don't need mofo. You could use fastboot, rsdlite, Motorola device manager or the Verizon upgrade assistant. The upgrade assistant is probably the easiest way to go. That's the annoying pop up software you get whenever you plug your phone into your computer.
Click to expand...
Click to collapse
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
LatencyXXX said:
I tried all 3 different options and none of them work. Then I went into Verizon store and asked them to do it and they told me that they don't do that anymore. Only contacts, photos, etc.
The store told me to send it to Motorola for them to do it. I'm sure there is an ISP somewhere or some trick button internally for them to unlock the bootloader, but nobody is saying.
I am out of options, and I am ready to send it to whomever can fix it for me. PM me if you can guarantee to do it and send it back.
-Thanks
Click to expand...
Click to collapse
Send it to Motorola then. If your phone is less than a year old, they will send you a new one for free.
guys
i have the verizon nexus 6 which I rooted and first had chroma but now run stock ROM. Can I accept ota updates - seeing 5.1.1 available if I'm running xposed module? I actually went ahead and accepted the upgrade but it rebooted into twrp and gave an error
What's the right way of doing this?
Thx
sam008 said:
guys
i have the verizon nexus 6 which I rooted and first had chroma but now run stock ROM. Can I accept ota updates - seeing 5.1.1 available if I'm running xposed module? I actually went ahead and accepted the upgrade but it rebooted into twrp and gave an error
What's the right way of doing this?
Thx
Click to expand...
Click to collapse
Have to be totally stock. No root,recovery or any other system mod. Best to just fastboot the current 5.1.1 image and forget about OTA's. Makes no sense to fastboot 5.0 then OTA when can fastboot 5.1.1 and be done with it.
how do i disable the prompts on the ota updates in the future
Also, anybody got a link for the verizon images? don't see them listed on the google site
https://developers.google.com/android/nexus/images
sam008 said:
how do i disable the prompts on the ota updates in the future
Click to expand...
Click to collapse
I never had too. Always stayed up with newest factory image. Only takes 5 minutes to update once used to doing it. Just don't flash userdata.image unless have to and will keep data like OTA. Instead of "fastboot flash userdata.img" just "fastboot format userdata". Have seen once where we lost the VOLTE option and had to flash userdata but they say it is not normal.
---------- Post added at 07:53 PM ---------- Previous post was at 07:45 PM ----------
The Sprint/USC is also the Verizon, ATT and International Versions. I'm on Verizon also using the Z image.
sam008 said:
how do i disable the prompts on the ota updates in the future
Also, anybody got a link for the verizon images? don't see them listed on the google site
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
To disable the notifications, long press on the notification, select app info, and untick the box that says "show notifications".
Evolution_Tech said:
To disable the notifications, long press on the notification, select app info, and untick the box that says "show notifications".
Click to expand...
Click to collapse
HaHaa. I knew there was a way I saw earlier but I have never waited long enough to see one. Especially running a Verizon sim. Will be months before it will pop up.
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
electrojas said:
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
Click to expand...
Click to collapse
If it was mine, I'd RMA this one too.
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
prdog1 said:
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
Click to expand...
Click to collapse
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
electrojas said:
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
Click to expand...
Click to collapse
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
electrojas said:
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
Click to expand...
Click to collapse
If able to put music on your driver is good. Need ADB/Fastboot working or you are already dead in the water.
prdog1 said:
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
Click to expand...
Click to collapse
15 minute adb? What is that like a tool that does all of that for you?
electrojas said:
15 minute adb? What is that like a tool that does all of that for you?
Click to expand...
Click to collapse
It the lazy man ADB/Fastboot for those that don't want to install full SDK and edit the environmental path.
http://forum.xda-developers.com/showthread.php?t=2588979
So I just follow the unlock procedure in the how to post like normal now right
electrojas said:
So I just follow the unlock procedure in the how to post like normal now right
Click to expand...
Click to collapse
Enable unlock in developers options. Boot to bootloader. in command prompt type "fastboot devices" to make sure your device id shows up. If shows device type "fastboot oem unlock". Will see prompt on phone to agree.
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
I suppose now I can take the downloaded one or do you recommend a better file. I really would like to keep this Damn phone
electrojas said:
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
Click to expand...
Click to collapse
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock. DO NOT use toolkit. Do it manually with fastboot commands.
prdog1 said:
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock.
Click to expand...
Click to collapse
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
electrojas said:
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
Click to expand...
Click to collapse
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
prdog1 said:
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
Click to expand...
Click to collapse
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
electrojas said:
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images