Related
I just bought an unlocked 9023 nexus s for my sister in India. I am a flash-junkie on my verizon droid inc, but she is not tech savvy. I wanted to load up a good stable system for her before handing over the phone so she could use it as a daily machine. I was thinking about applying the stock 4.0.3 full update but then i saw some issues about wifi and signal and google halting it, so now im having second thoughts. if i do the 4.0.3 full update from recovery, can i go back to gb if i have problems?
will the phone keep getting all future ics upgrades through google?
is 4.0.3 stock rootable? and will root stay in upgrades? (so if i root and give her, Id like her to use titanium and stuff and not have to worry about losing root in future OTA.)
Thanks.
How about reading the stickies.
k.electron said:
I just bought an unlocked 9023 nexus s for my sister in India. I am a flash-junkie on my verizon droid inc, but she is not tech savvy. I wanted to load up a good stable system for her before handing over the phone so she could use it as a daily machine. I was thinking about applying the stock 4.0.3 full update but then i saw some issues about wifi and signal and google halting it, so now im having second thoughts. if i do the 4.0.3 full update from recovery, can i go back to gb if i have problems?
will the phone keep getting all future ics upgrades through google?
is 4.0.3 stock rootable? and will root stay in upgrades? (so if i root and give her, Id like her to use titanium and stuff and not have to worry about losing root in future OTA.)
Thanks.
Click to expand...
Click to collapse
Nexus devices can always have their bootloaders unlocked and then install superuser afterward. When unlocking the bootloader all of her data will be lost.
Root is disable on OTA updates because permissions get adjusted. You can run a fix permissions in CWM or reflash a superuser zip file after the OTA to get root again.
You can go back to GB by flashing an old system image using fastboot if you don't like ICS.
superm1 said:
Nexus devices can always have their bootloaders unlocked and then install superuser afterward. When unlocking the bootloader all of her data will be lost.
Root is disable on OTA updates because permissions get adjusted. You can run a fix permissions in CWM or reflash a superuser zip file after the OTA to get root again.
You can go back to GB by flashing an old system image using fastboot if you don't like ICS.
Click to expand...
Click to collapse
thanks.
exactly what i needed to know. i might just put ics and give it to her without root so she can keep getting OTAs because i dont think she really needs root.
Hi all,
can anyone advise where the OTA updates are saved on the phone? Our provider has issued an OTA update to ICS (Telecom NZ) and I look after 40 odd Atrix2 handsets....don't really want to download the update 40 times.
I want to try coying it to each hanset or install using the same tools used for fxz files.
Thanks
IceFragmatic said:
Hi all,
can anyone advise where the OTA updates are saved on the phone? Our provider has issued an OTA update to ICS (Telecom NZ) and I look after 40 odd Atrix2 handsets....don't really want to download the update 40 times.
I want to try coying it to each hanset or install using the same tools used for fxz files.
Thanks
Click to expand...
Click to collapse
It's stored in the "Cache" folder on the root of your phone. Obviously you need to be rooted to access the folder itself.
Thank you
Further to my post above,
I have approx 75 Atrix2 phones that I am contemplating upgrading to ICS (official Telecom NZ release) from GB. They are all setup identically.
What would be the easiest way? I have tried setting up a phone and making a backup using bootstrap version of CWM, then 'recovering' this onto a GB phone - unfortunately it is not that easy.
Any other suggestions?
Currently, some of the phones have the bootstrap files on them so I am likely going to need to remove this to allow the update to occur.
About 50 of the phones are brand new and do not have any bootstrap or changes from original.
First off, I know there's no Droid Maxx section, but this is the closest place to post this.
As the title states, I have the Verizon Maxx on 4.2.2 (software version 12.15.15) and it is completely stock (never rooted or anything else). I'm thinking of rooting it and putting it on the 4.4 Kit Kat update. I plan on using RockMyMoto 1.1 to root first using DG4FREE's guide. Then I will use MotoWpNoMo 0.0.4 as needed for SlapMyMoto 1.0.
I think I can do everything up to SlapMyMoto just fine. I just have a few questions about using SlapMyMoto:
1) Before using SlapMyMoto you have to "restore to the 4.2.2 Camera update." This can be done with RSD Lite (or House of Moto), right?
2) If I use RSD, I would use the first file listed here (Blur_Version.12.7.7 ...), correct? (Yes, I do understand Verizon's naming scheme for updates...)
3) Towards the end of SlapMyMoto process, what does "Once the device has rebooted, please take the 4.4 OTA" mean? Do I use the update.zip method to install the 4.4 OTA from the stock recovery or some other method? If so, where can I find a reliable 4.4 OTA zip for the Maxx that won't brick my phone?
4) Going along with question 3, as I have come to understand reading forum posts I will have to run the install update from sdcard using the update.zip twice for Kit Kat to be finally installed. Is that correct? If so, will SlapMyMoto actually keep root from 4.2.2 or not after the second install!?
5) After doing this and successfully getting root on 4.4, will I be able to receive OTA updates in the future after flashing back to stock 4.4 with RSD?
6) Anybody having issues with root on their Ultra/Maxx and Kit Kat 4.4 making it unusable? I don't use other mods at all (i.e. Xposed, etc.), but I do plan on using ART.
If it seems likely that I might brick my phone, I might just stick with updating to 4.4 without root. I don't know yet. Thank you in advance for your help.
PonchoPicasso said:
First off, I know there's no Droid Maxx section, but this is the closest place to post this.
As the title states, I have the Verizon Maxx on 4.2.2 (software version 12.15.15) and it is completely stock (never rooted or anything else). I'm thinking of rooting it and putting it on the 4.4 Kit Kat update. I plan on using RockMyMoto 1.1 to root first using DG4FREE's guide. Then I will use MotoWpNoMo 0.0.4 as needed for SlapMyMoto 1.0.
I think I can do everything up to SlapMyMoto just fine. I just have a few questions about using SlapMyMoto:
1) Before using SlapMyMoto you have to "restore to the 4.2.2 Camera update." This can be done with RSD Lite (or House of Moto), right?
2) If I use RSD, I would use the first file listed here (Blur_Version.12.7.7 ...), correct? (Yes, I do understand Verizon's naming scheme for updates...)
3) Towards the end of SlapMyMoto process, what does "Once the device has rebooted, please take the 4.4 OTA" mean? Do I use the update.zip method to install the 4.4 OTA from the stock recovery or some other method? If so, where can I find a reliable 4.4 OTA zip for the Maxx that won't brick my phone?
4) Going along with question 3, as I have come to understand reading forum posts I will have to run the install update from sdcard using the update.zip twice for Kit Kat to be finally installed. Is that correct? If so, will SlapMyMoto actually keep root from 4.2.2 or not after the second install!?
5) After doing this and successfully getting root on 4.4, will I be able to receive OTA updates in the future after flashing back to stock 4.4 with RSD?
6) Anybody having issues with root on their Ultra/Maxx and Kit Kat 4.4 making it unusable? I don't use other mods at all (i.e. Xposed, etc.), but I do plan on using ART.
If it seems likely that I might brick my phone, I might just stick with updating to 4.4 without root. I don't know yet. Thank you in advance for your help.
Click to expand...
Click to collapse
Just to clarify, it's RockMyMoto while on stock 4.2...then MotoWPNoMO...then you need to RSD back to the 12.15.15 camera update...then you run SMM...then you update to 4.4...then you finish SMM commands in ADB...install supersu or superuser...done.
1. Yes
2. Second file, 12.15.15 is the camera update.
3. That means that after SMM and the reboot, you boot to stock recovery and update zip will run just fine. http://forum.xda-developers.com/showthread.php?t=2577977
4. The update runs twice...sort of...it installs the new recovery (no turning back) and then you will run it again for the update. SMM needs to be finished off with the ADB commands in 4.4 to get root. SMM already planted all the seeds in 4.2.
5. Not so simple, generally speaking...once you have root, especially on a Moto...you'll have to flash back to stock to get any OTA...or just wait a while for someone around here to get a fix...it's usually out by the time a public OTA get's around anyway. If you want to keep root, I would recommend that you never take an OTA from VZW unless you read up on XDA firs and understand the implications.
6. I am rooted 4.4 on my Maxx following this exact process and using the ART runtime...not having any issues at all, I even have SafeStrap re- installed for back ups.
Hope that helps
Lebowski13 said:
Just to clarify, it's RockMyMoto while on stock 4.2...then MotoWPNoMO...then you need to RSD back to the 12.15.15 camera update...then you run SMM...then you update to 4.4...then you finish SMM commands in ADB...install supersu or superuser...done.
1. Yes
2. Second file, 12.15.15 is the camera update.
3. That means that after SMM and the reboot, you boot to stock recovery and update zip will run just fine. http://forum.xda-developers.com/showthread.php?t=2577977
4. The update runs twice...sort of...it installs the new recovery (no turning back) and then you will run it again for the update. SMM needs to be finished off with the ADB commands in 4.4 to get root. SMM already planted all the seeds in 4.2.
5. Not so simple, generally speaking...once you have root, especially on a Moto...you'll have to flash back to stock to get any OTA...or just wait a while for someone around here to get a fix...it's usually out by the time a public OTA get's around anyway. If you want to keep root, I would recommend that you never take an OTA from VZW unless you read up on XDA firs and understand the implications.
6. I am rooted 4.4 on my Maxx following this exact process and using the ART runtime...not having any issues at all, I even have SafeStrap re- installed for back ups.
Hope that helps
Click to expand...
Click to collapse
Thank you so much! That really answered all my questions!
I have just one question to clarify your answer: are you sure it is the second file? I was under the impression that Verizon named their updates for the version from which you are updating from, so the first file there would actually be the 12.15.15 software even though it is named 12.7.7.
PonchoPicasso said:
Thank you so much! That really answered all my questions!
I have just one question to clarify your answer: are you sure it is the second file? I was under the impression that Verizon named their updates for the version from which you are updating from, so the first file there would actually be the 12.15.15 software even though it is named 12.7.7.
Click to expand...
Click to collapse
Happy to help! You are correct in the VZW OTA naming conventions...but the files in that link are actually the FXZ files to flash with using RSD, et al...not an OTA zip file, so they are named correctly by their version. 12.15.15, the second file, is definitely the camera update and the correct one to use.
Lebowski13 said:
Happy to help! You are correct in the VZW OTA naming conventions...but the files in that link are actually the FXZ files to flash with using RSD, et al...not an OTA zip file, so they are named correctly by their version. 12.15.15, the second file, is definitely the camera update and the correct one to use.
Click to expand...
Click to collapse
Thanks for the clarification on that.
I just wanted to follow up on this thread for anybody else out there who might have been in the same boat as me. After completing this whole process a couple days ago, everything has been running smoothly now that I'm on 4.4 with root. I did not enable ART as I mentioned earlier I would since it turns out I needed to install Xposed to get a particular app that performs a root check to work. Other than that, smooth sailing except having to redo some steps manually.
I'm currently on NI1, and I just had a update notice. It's about 392mb in size. Didn't see anything about any updates so figured I'd post.
Did you take the update? Did it install? If so what is the firmware listed as?
Since it is 392mb I would assume it is an update, rather than a full version increment? Probably still 4.4.2 Let is know
It's almost done downloading now at 81%. I'll post back with a version once installed.
Are you rooted right now? If so it may not install, or try and fail. If you are rooted immediately after it finishes downloading you can copy the update file to your sdcard/external sdcard and upload it to a file sharing site. If it is in fact a newer version of firmware you could make devs happy. If you need to know how/where the update is located I can help you out
BEFORE IT INSTALLS open up a file browser (if rooted possibly) and navigate to \cache\fota\2400258.cfg. Should be the name or something similar. Long press on it and choose copy. Then navigate to you sdcard and paste it where you can find it. Then upload it to a sharing site.
Not rooted on this S4. The update went through and it was updated to NJ1 4.4.4
dankhar said:
Not rooted on this S4. The update went through and it was updated to NJ1 4.4.4
Click to expand...
Click to collapse
Thanks, hopefully SOMEONE will pull it soon.
Yeah. Been having random issues with my phone since the previous. All seems to be good now. The update does add a few new programa. Nothing worth using except maybe keeper. But so far so good.
Phones definitely a lot snappier now.!
I would love to see a screenshot of the about to confirm.
There you go.
Update failed on my rooted device
I just tried it, It failed to update and I lost root.
Here is a screen of the few apps it put on once completed. It also added a kids mode app.
If ANYBODY is rooted it most likely WILL FAIL. It is only 300+ MB sobitbis not a complete ROM and most like just has mostly PATCH files inside. I would recommend users that are rooted WAIT until a dev can do something with it, and check it out. Each update has locked our phones down harder.
On that note if ANYONE is rooted and downloads it, do NOT install it. But go to the location I listed above to pull the file from the phone and upload it to a sharing site. Then a dev can look into it first and incorporate it for our rooted phones WITHOUT updating the bootloader
After looking around the forums it looks like Samsung has pushed a few updates to phones ( S4 getting 4.4.4, S3 4.4.2 patch files, and the Note has gotten an update as well). I think these updates are probably going to be the final updates before they phase out old devices and possibly start porting 5.0 on our device (S4). I really wish there wasn't new At&t bloat, but hopefully these are new services that phase out all the old outdated bloat At&t had in the past :good: also to each his own I just never use those apps.
Thanks for posting this, I would've enjoyed this if I hadn't already flashed Goldenfinger and nandroided all my apps over... to lazy to use Safestrap again.
DON'T INSTALL IF YOU'RE ROOTED!
Nice. Wasn't doubting the OP. I see att has updated their support page to reflect the NJ4 update.
RockRatt said:
Are you rooted right now? If so it may not install, or try and fail. If you are rooted immediately after it finishes downloading you can copy the update file to your sdcard/external sdcard and upload it to a file sharing site. If it is in fact a newer version of firmware you could make devs happy. If you need to know how/where the update is located I can help you out
BEFORE IT INSTALLS open up a file browser (if rooted possibly) and navigate to \cache\fota\2400258.cfg. Should be the name or something similar. Long press on it and choose copy. Then navigate to you sdcard and paste it where you can find it. Then upload it to a sharing site.
Click to expand...
Click to collapse
If no one else does, I will try when I get to work tomorrow. We have numerous S4's that people traded in for the S5. I can see if I am able to root one and do the update using your instructions. If not I can check to see if onw of our Kiosks can allow me to pull the update. Not sure if they have that one yet for self updating. Will let you know in the AM.
dankhar said:
If no one else does, I will try when I get to work tomorrow. We have numerous S4's that people traded in for the S5. I can see if I am able to root one and do the update using your instructions. If not I can check to see if onw of our Kiosks can allow me to pull the update. Not sure if they have that one yet for self updating. Will let you know in the AM.
Click to expand...
Click to collapse
Thanks. Hopefully a dev can create a ROM for us all
Rooted S4
RockRatt said:
Thanks. Hopefully a dev can create a ROM for us all
Click to expand...
Click to collapse
Wish I had read this before. I am rooted so it said install interrupted after download. So do I have to unroot and return to stock? I am on NI1 4.4.2. Maybe you or someone can get copy for us to install it by. Let us know what to do if rooted to get the OTA. Thanks
Downloading now. I'll post when done. Rolled back to NB1 before updating so this is a 489MB download.
guut13 said:
Downloading now. I'll post when done. Rolled back to NB1 before updating so this is a 489MB download.
Click to expand...
Click to collapse
Guess I will roll back to NB1 also Friday. Got NB1 downloading now. Do I need to wipe or Anything before I flash file in Odin 3.09????
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
If she is rooted it will break root, If she has a custom recovery (twrp) than it will cause a boot loop.
advice: if she wants lollipop she's gonna have to follow these steps.
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
Going to pass the link on to her now.
There is no custom recovery. She used Stump Root originally to get her phone route, if that makes any difference.
martinezma99 said:
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
Click to expand...
Click to collapse
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
SGE_DEW said:
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
Click to expand...
Click to collapse
You would still lose root
2SHAYNEZ
Yep.. I went through the whole process of going completely back to stock and then rooted before updating to Lollipop hoping it would stay. It didn't and Stump Root says it's already rooted.
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Rayvin56 said:
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Click to expand...
Click to collapse
I read somewhere the LG Flashtool had to be modified at installation to avoid what you are going through.
You're right, it's just a matter of overwriting the megalock.dll file after you install the tool. It was a step I didn't miss. But good news for me, I used another pc and when I installed the flashtool it again gave me the three choices (not sure, but the title bar of the window was something like 'DMB').
This time I chose the 'global' selection and ran the tool as before and it completed for me. I'm currently DL'ing the lollipop update right now. Thanks for the quick reply, netomel.
partylikeaninjastar said:
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
Click to expand...
Click to collapse
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
hitekredneck said:
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
Click to expand...
Click to collapse
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update.
Click to expand...
Click to collapse
+1
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
Click to expand...
Click to collapse
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Lolipop upgrade
Hi iam very new on this forum . I got LGg3 AT&t version D85010f and i cannot upgrade to LOLIPOP always i have com that i have latest soft and need to wait 48h to next check ......plz help me
hitekredneck said:
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Click to expand...
Click to collapse
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Vess69 said:
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Click to expand...
Click to collapse
Call Bull**** all you want, I don't lie. To be honest, I can't even remember what method I used to root when on KitKat. Then I used TiBu to freeze a bunch of apps that I didn't want or need. Shortly thereafter the update hit me so I went ahead and let it do its thing. As stated, I did lose root afterwards but the apps I had frozen with TiBu remained frozen and everything still worked as it should. I waited patiently for a few weeks until the one click root script became available and used it to root lollipop, then installed TWRP and flashed Cloudy G3 stock ROM which is where I am happily at at this moment.
It could possibly have successfully updated due to the fact that I had not installed a custom recovery, that's the only thing I can think of that would have allowed it to happen on mine, yet not on others that were rooted.
EDIT: After reading back through this thread it jogged my memory. I used the Stump Root method to root while on KitKat.
You'd be the first person reported to be able to do this.
It would be a boon to the AT&T G3 community if you could remember the precise details of how you pulled this off as it would save loads of time and hassle for everyone else who has to restore to KK (which means a full wipe), then take the OTA to L, then root there.
Thanks in advance.
*edit
I think you're L is version 20f, not the latest 21l, based on the date of your posts above.
Further, I'd suppose that what may have happened to you, is that the deivce had already downloaded the L update (from 10f to 20f) before you pulled off the root on KitKat. Then you simply acknowledged the install, which perhaps KK would allow to continue through.
Reports are the L will not allow this. So, going forward, someone rooted on L would not be allowed to complete the install even if the package is already downloaded on the device.
Still, it is, interesting.