Related
Not sure if wrong forum section but was wondering if there was a way to block all Verizon updates without root. I keep getting notifications to install the latest update (the one that gives Advanced Calling 1.0) but I don't want to install it in case it causes issues. Is there a way to remove/block this update feature without root?
You can disable all the Verizon's apps. In the app section in settings I don't get any notifications.
mdcowby said:
You can disable all the Verizon's apps. In the app section in settings I don't get any notifications.
Click to expand...
Click to collapse
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
jgowell said:
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
Click to expand...
Click to collapse
Not without root unfortunately. You can only keep declining the install and that's it but eventually your phone will bend to big red's will when you're not paying attention
jgowell said:
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
Click to expand...
Click to collapse
I've never gotten those update notifications so my disabling a lot of stuff from Verizon and moto must of prevented something.
Just curious then what is your current firmware version? Want to see if you unknowingly updated already or if your update was actually blocked
mdcowby said:
I've never gotten those update notifications so my disabling a lot of stuff from Verizon and moto must of prevented something.
Click to expand...
Click to collapse
Is your system 21.44.8 or 21.21.15?
jgowell said:
Is your system 21.44.8 or 21.21.15?
Click to expand...
Click to collapse
221.44.8 if it updated it did it without me knowing. I'm getting rid of this phone anyway. Came from insurance cause they didn't have any razr maxx in Stock. I really don't like it.
Okay it sounds like it didn't update as your firmware version matches as one without the update Advanced Calling feature. Still curious to know what you disabled so I could get rid of my notification too
I think this newer ota app came from the Turbo, it stops it on the ultras. Check the md5 against yours. Pull it with Super Manager, apk manager, bAPK. Use Explorer free to read the md5.
I posted the md5 on my Op.
http://forum.xda-developers.com/showpost.php?p=56708101&postcount=1
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
I wanted to check where it came from anyway. If not from Turbo then you may be able to benefit too.
aviwdoowks said:
I think this newer ota app came from the Turbo, it stops it on the ultras. Check the md5 against yours. Pull it with Super Manager, apk manager, bAPK. Use Explorer free to read the md5.
I posted the md5 on my Op.
http://forum.xda-developers.com/showpost.php?p=56708101&postcount=1
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
I wanted to check where it came from anyway. If not from Turbo then you may be able to benefit too.
Click to expand...
Click to collapse
What? Not sure what you are trying to say. Can you reword?
lafont28 said:
Not without root unfortunately. You can only keep declining the install and that's it but eventually your phone will bend to big red's will when you're not paying attention
Click to expand...
Click to collapse
actually you can block OTA's without root.
go here and use this method. without root
http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
jgowell said:
What? Not sure what you are trying to say. Can you reword?
Click to expand...
Click to collapse
I still have the old Maxx. I found that installing a newer moto ota app (my link) I could stop the ota. I have yet to determine which new moto system dump I got it from. If not from the Turbo then it may stop it too.
Md5 is unique to any app. I posted it for the unknown app.
When you boot your phone, wait until the download notification comes up then go into settings and force stop MotorolaOTA. It'll cancel the download and it won't try again until you reboot.
Cobra04 said:
When you boot your phone, wait until the download notification comes up then go into settings and force stop MotorolaOTA. It'll cancel the download and it won't try again until you reboot.
Click to expand...
Click to collapse
Look two post above by me. you can block without root
the_rooter said:
Look two post above by me. you can block without root
Click to expand...
Click to collapse
A few questions about this. Let me know if it is easier to PM you or post here
the_rooter said:
Look two post above by me. you can block without root
Click to expand...
Click to collapse
jgowell said:
A few questions about this. Let me know if it is easier to PM you or post here
Click to expand...
Click to collapse
Try this blocking method out, I believe it will work for the Turbo. It's easier than using the script. http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Misterxtc said:
Try this blocking method out, I believe it will work for the Turbo. It's easier than using the script. http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
thanks MisterXTC. The tool seems to work like a charm, esp with the search function.
One question: the OTA is already downloaded on my phone and i keep getting a notification to install it but I have been been 'delaying' the install. When I block the "MotoralOTA" but then reboot the phone the phone, the notification comes back. Is there a way to permanently block the OTA or will I have to block it each time the phone restarts?
jgowell said:
thanks MisterXTC. The tool seems to work like a charm, esp with the search function.
One question: the OTA is already downloaded on my phone and i keep getting a notification to install it but I have been been 'delaying' the install. When I block the "MotoralOTA" but then reboot the phone the phone, the notification comes back. Is there a way to permanently block the OTA or will I have to block it each time the phone restarts?
Click to expand...
Click to collapse
Try entering recovery mode and wipe the cache. That will delete the downloaded update file. As for permanently blocking the OTA it should stay blocked until you factory reset. It's probable nagging you because of the downloaded update file. You might have to re-block the OTA after clearing cache, I'm not positive. You might need to enter your app manager and manually stop the OTA, try that first.
Misterxtc said:
Try entering recovery mode and wipe the cache. That will delete the downloaded update file. As for permanently blocking the OTA it should stay blocked until you factory reset. It's probable nagging you because of the downloaded update file. You might have to re-block the OTA after clearing cache, I'm not positive. You might need to enter your app manager and manually stop the OTA, try that first.
Click to expand...
Click to collapse
I went ahead and cleared cache and it seems to have worked. No notifications to install so far despite reboot.
Thanks again for the link and help afterwards!
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.
Hey all,
Thought I'd let those of you that have an AT&T Tab S 8.4 know that Lollipop has been released today. Happened to be on the AT&T Software update page here: http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425812&cv=820 and noticed it listed the update.
Manually checked for updates on my tablet, it's downloading now. My 8.4 on AT&T is totally stock.
Downloading now... 1.1GB
manually checking shows nothing for me
Mine wasn't too laggy after the upgrade. But as I know from places like XDA usually a very good idea to do a full system wipe which I did.
What I am most thankful for is there is now an option to remove that Samsung screen that has those Samsung widgets that go full page. Can't recall what it is called. Yeah I know could have got rid of that using a 3rd party launcher in 4.4 but so happy Samsung put option there to disable it finally. To get rid of it, long press blank space like you were going to add a widget, then click Home Screen Settings, then uncheck "Content Home Screen".
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Not sure it will work.
Maybe try to adapt the method given by ashyx here: http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484
It worked successfully for me on the T800
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
fleabeard said:
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
Click to expand...
Click to collapse
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Has any kingroot user tried triangle away, unroot via kinguser, and take the OTA?
Also just realized that if I can fail the OTA, I can obviously download it... Where do I grab it from if I wanted to flash it with odin or sideload?
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Russ77 said:
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Click to expand...
Click to collapse
OTA came down successfully while not rooted. The reflash at Best Buy didn't wipe it.
As far as I know, the factory images for the AT&T versions aren't available anywhere, or at least I've been unable to find them. They obviously exist because I'm pretty sure the guy at Best Buy used Kies to flash with an image that's available to him from Samsung.
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
im not rooted, performed a factory reset, and my device still doesn't see any updates. Can somebody provide a link to the ROM?
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Same Thing Here Also
bshaw100 said:
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Click to expand...
Click to collapse
I've got the same thing: no root, no mods, no update available! Darn!!!!
I've got the same thing: no root, no mods, no update available!
Russ77 said:
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
Click to expand...
Click to collapse
The OTA gets downloaded to /cache. If you are rooted you can see it. But the OTA is not a complete ROM, just a differential to the ROM you have.
Sent from my SM-T707V using XDA Premium HD app
still nothing
gshaw_nash said:
I've got the same thing: no root, no mods, no update available! Darn!!!!
Click to expand...
Click to collapse
gshaw1967 said:
I've got the same thing: no root, no mods, no update available!
Click to expand...
Click to collapse
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
---------- Post added at 08:58 AM ---------- Previous post was at 08:11 AM ----------
gshaw1967 said:
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
Click to expand...
Click to collapse
Turns out there is a imei problem with the tablet that is preventing the download. My imei number is paired with a IPhone 4. Anyway will take a few day to fix then the upgrade should work.
I get the same. I wiped my device hoping for a different outcome, and still no update.
I found this in the thread below.
It is an old tread but I'll comment anyway. SM-T807 is the 3G version while SM-T805 is the LTE version. Both Hardware (CPU/GPU) and comms modules are different. So 805 LTE (which has Lollipop) firmware won't work for 807 (no Lollipop is currently available nor Samsung plans to release soon).
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t805-sm-t807a-t2961117
John.
After not being able to take the OTA after rooting, even after un rooting, not being able to find the OTA and sideload (not in /cache), and not able use Kies or Odin I finally took it to the Samsung kiosk at my bestbuy.
They reflashed 4.4.2, didn't wipe anything, and immediately downloaded and successfully installed the lollipop update after getting home and on WiFi.
Just don't mention that you rooted ;')
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
I just bought an AT&T N6 from Swappa. I plan to use it on Fi when my invite comes, for now I will transfer my Straight Talk service to it. It came with LMY47Z on it, then downloaded an update and ended up on LMY48I. Now, LVY48E says it is "For Project Fi ONLY", which leaves me to ask, will I have to flash LVY48E when I switch to Fi? If I flash LVY48E now will it work on ST? Any helpful insights would be appreciated.
Mostlyhrmlss said:
I just bought an AT&T N6 from Swappa. I plan to use it on Fi when my invite comes, for now I will transfer my Straight Talk service to it. It came with LMY47Z on it, then downloaded an update and ended up on LMY48I. Now, LVY48E says it is "For Project Fi ONLY", which leaves me to ask, will I have to flash LVY48E when I switch to Fi? If I flash LVY48E now will it work on ST? Any helpful insights would be appreciated.
Click to expand...
Click to collapse
As proven elsewhere, once you get your Fi sim card, either you will get the Fi update via OTA, which you can flash successfully if you're 100% stock. You could also sideload while stock.
Personally, I recommend unlocking your bootloader, if you haven't already. It makes recovering from bootloop and such, much easier. You can stay 100% stock, OTA capable, with an unlocked bootloader. Then, when a factory image is released, you can update that way too, without losing data. All of this, is IF you plan on staying stock.
I plan to remain close to stock anyway, I just want to root so Titanium Backup and Busybox can do their magick. This sounds like a great plan of action, I appreciate the prompt response!
Mostlyhrmlss said:
I plan to remain close to stock anyway, I just want to root so Titanium Backup and Busybox can do their magick. This sounds like a great plan of action, I appreciate the prompt response!
Click to expand...
Click to collapse
If you're rooted, you can't take OTA's anyway, so definitely keep that bootloader unlocked.
Really? I loaded a rooted stock 4.1.2 on my current phone (AT&T Galaxy Note II) and got tired of the OTA notifications so I froze the AT&T Software Update app. Is no-OTAs-if-rooted a new thing or a Nexus thing?
Mostlyhrmlss said:
Really? I loaded a rooted stock 4.1.2 on my current phone (AT&T Galaxy Note II) and got tired of the OTA notifications so I froze the AT&T Software Update app. Is no-OTAs-if-rooted a new thing or a Nexus thing?
Click to expand...
Click to collapse
It's a lollipop thing. OTA's won't flash with any modified system, boot, and recovery images. Most of the users that stay stock rooted, just update by flashing system and boot images from the factory image. Also, you can update your bootloader and radio if needed.
---------- Post added at 11:57 PM ---------- Previous post was at 11:55 PM ----------
http://forum.xda-developers.com/showthread.php?t=2992919