Related
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Is there a new update? post/after asa14?
Checked around but after seeing the old do this if you cant upgrade threads pop up I was curious.
Seen some traces of the 9.8.2Q JellyBean update for the Q, but don't know it's current status.
Interesting and good news, Just checked and mine stated not update available sadly..
Gxkon said:
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
Click to expand...
Click to collapse
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
swintec said:
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
Click to expand...
Click to collapse
I dont know it dont look like a new os. One was around 60 mb then i had a small 7 mb update
arrrghhh said:
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Click to expand...
Click to collapse
Yeah, the motofail2go exploit to root works only if you haven't updated. After rooting, you can save root by Voodoo OTA rootkeeper, temp unroot, install any updates, then restore root with OTA rootkeeper. Works great, and you keep your warranty. But of course you can't flash any ROMs or anything, but you can still use Titanium backup, other programs that require root.
see this thread:
http://forum.xda-developers.com/showthread.php?t=2053444
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
esjames said:
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
Click to expand...
Click to collapse
Literally one thing: http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3-4.30.14.pdf
Well, then. Thats a worthy update lol
esjames said:
Well, then. Thats a worthy update lol
Click to expand...
Click to collapse
by all means, if you're traveling to Canada then update away haha
Lmao wow. That's the most pitiful update ever. Seriously, couldn't they have waited until there was something more substantial and then included Canadian roaming in THAT update. As always though, Verizon is dumber than a bag of hammers...
Sent from my iPhone using Tapatalk
Might be worthwhile to extract the modem package and see if the SMS bug is rectified.
wow
i was so sure this was a KK upgrade. been looking around for how to retain root if you take it. thanks for the info!
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
EddieK23 said:
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
Click to expand...
Click to collapse
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
landshark68 said:
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
Click to expand...
Click to collapse
Ah, I see, next time I'm around her I'll re-root it and backup all her stuff with titanium backup, flash the VRUCML1 and factory reset, then restore everything and see if it works.
Strangely enough, when the same update for my Verizon Note 2 came out, I was able to update while rooted even though I unsinatalled theexact same system apps I did on her phone. How strange.
Nonetheless, thank you so much.
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Joe R said:
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Click to expand...
Click to collapse
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Ok thanks. I will try to find an ML1 download.
Sent from my Samsung Galaxy S III using Tapatalk
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
pnuker said:
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Maintained root
twistedillutions said:
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was able to maintain root on the OTA update by having OTA Survival Mode checked on SuperSU.
SlimSnoopOS said:
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
smalco44 said:
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
Click to expand...
Click to collapse
Apparently I need a refresher on how to properly copy and paste Here's the link again: http://forum.xda-developers.com/showthread.php?p=52515244#post52515244
I have not yet updated to this new patch yet, am I still able to install saferoot as directed on the thread for it or do I need to do something special first?
So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
I Have H950 G Flex2, But i didnt get android 5.1.1 , i love this phone even it get hot somethimes, its good for me.
I want to know if maybe someone can help me to update to 5.1.1 because i dont have ota Update avalible and if is possible, try a stock or international room of 5.1.1 for the H950 Because att have a lot of bloatware.
Thanks all!
Yes
The various threads around here are quite helpful. If you're rooted, you're going to have to go back to stock. The OTA update should then kick in.
There's a thread over in the Android Development Section (It's at the top) that is exactly what you're looking for.
So, yes there are certainly methods by which you can update to 5.1.1!
Cmcarboni said:
The various threads around here are quite helpful. If you're rooted, you're going to have to go back to stock. The OTA update should then kick in.
There's a thread over in the Android Development Section (It's at the top) that is exactly what you're looking for.
So, yes there are certainly methods by which you can update to 5.1.1!
Click to expand...
Click to collapse
Can you help me with the link please? im searching since i buy it. Thank you
Of course I can help
kiscvik said:
Can you help me with the link please? im searching since i buy it. Thank you
Click to expand...
Click to collapse
This is a detailed tutorial on how to return your phone to stock. You'll end up with a data wipe, so make sure to back up anything you want to keep. You'll want to do this first. Nothing should go wrong (no guarantees though, as always), just make sure you pick up the H950 version of the system file (and put this in the root directory of your internal storage, and rename it to "system.img" if isn't already.)
Easy Restore/Recovery/Unbrick Tool for LG G Flex 2
You'll reboot to your bloated stock system, and you should be able to get the OTA update. If you come across the "Please wait 24 hours and try again" message, just go manually set your date and time ahead, that should get it working.
Then you'll want to use this link to update to flash a 5.1.1 (rooted) system file (similar to the way you did it before).
http://forum.xda-developers.com/g-flex2/development/root-easy-root-att-flex-2-5-1-1-t3178354
After a great deal of tediousness, you can install Titanium Backup and remove all of the bloatware. Obviously, be cautious, you might break things (and then you'll need to factory reset, yet again). In the near future I'll post a thread of all the bloatware I removed without any issue.
EDIT: I've created a freezable bloatware list for those of you unsure what's safe and what's not. The thread is here:
Ti Backup Bloatware Freeze List
Once you're done with that, if you're brave enough, you can install the XPosed framework (even though the bootloader is locked) using this link:
XPosed G Flex 2
The process is a bit sketchy, the extended periods of black screen are a bit foreboding, but it worked like a charm.
I am also in the same boat. Not receiving OTA, tried factory reset and date+1 doesn't work
Has anyone outside the US or AT&T network been able to update? Perhaps it works with a VPN? I haven't been able to update my brand new phone with zero modifications.
Im outside US, and i haven't got the OTA, i been trying changing the date and factory reset every now and then...
I will try a VPN and see how it goes.
Yes
When I returned to stock 5.0.1 I got the ATT OTA update. I'm in the US.
I don't claim to know the intricacies of flashing, but there are H950 5.1.1 system images floating around these boards. Could you flash one of those while on stock 5.0.1? I'm not sure. We do have an unbrick tool though so you'd probably be able to recover.
Let me know if anyone skips the part where they let the phone update itself, and go straight to flashing 5.1.1.
I just bought this phone brand new in the box because I heard the update was out on ATT, not for me I guess.
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Tikerz said:
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Click to expand...
Click to collapse
Sounds like a direct flash upgrade is a no go then. I also set my device forward a few days (like a week) to get the update.
I Just ordered this phone and will be using it on cricket wireless, does anyone know if I'll need an active at&t sim card to get the 5.1.1 update or will I be able to get the update with my cricket wireless sim card?
Nope
Using a Straight Talk SIM myself and I got the OTA update just fine.
Tikerz said:
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Click to expand...
Click to collapse
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
errcyco86 said:
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
Click to expand...
Click to collapse
Did you already update?
if not wait!! and send me a mp
Sj12345 said:
Did you already update?
if not wait!! and send me a mp
Click to expand...
Click to collapse
Sorry I am new as of today.. I just bought the xda app. I don't know what an mp is. Please tell me what I did wrong tho now I am paranoid
errcyco86 said:
Sorry I am new as of today.. I just bought the xda app. I don't know what an mp is. Please tell me what I did wrong tho now I am paranoid
Click to expand...
Click to collapse
Nothing is wrong, (pm is private message), did you already update your phone?
Sent from my Z812 using Tapatalk
Sj12345 said:
Nothing is wrong, (pm is private message), did you already update your phone?
Sent from my Z812 using Tapatalk
Click to expand...
Click to collapse
Yes, went from 5.0.1 to 5.1.1
I used the method above of changing the date a month forward.. It went from saying up to date to giving me the ota
I hope the update isn't crop because I don't know much of rooting and roming. Hoping to learn stuff here as xda is full of some smart folks.
errcyco86 said:
Yes, went from 5.0.1 to 5.1.1
I used the method above of changing the date a month forward.. It went from saying up to date to giving me the ota
I hope the update isn't crop because I don't know much of rooting and roming. Hoping to learn stuff here as xda is full of some smart folks.
Click to expand...
Click to collapse
No, you're fine. I think he just wanted the OTA file.
Sent from my LG-H950 using Tapatalk
??
errcyco86 said:
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
Click to expand...
Click to collapse
So how? Just change the date and what? i didnt understand, im outside US
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
You won't be able to update while rooted. Actually updating with a factory image is probably safer than taking an ota update. Personally, I think the update is worth it.
Sent from my SM-T530NU using XDA-Developers mobile app
hexr96 said:
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
Click to expand...
Click to collapse
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
acejavelin said:
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
Click to expand...
Click to collapse
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Tel864 said:
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps stability is not the real argument here... both are stable, as are most production ROMs, I have been using Marshmallow since early December and never had any real problems. But there are pros and cons to both and depending on your situation one may be better than the other, but I guess that wasn't really the point of this thread so I will say I half agree with your statement.
I would also have to relock the bootloader, correct?
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
No
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
Nope, in fact, you can't relock the bootloader even if you want to. The bootloader lock state is not relevant to taking an OTA.
Thank you everyone