guys
on a verizon nexus 6, who provides OTA updates - verizon or google?
also, if I root the phone and use xposed, will I be able to get ota updates or should be avoided?
Thx
Google, but Verizon have to approve them first.
No, you cannot OTA with any modification to /system, including root.
Xposed is in alpha testing. It's for experienced testers only. Only use it if you are very familiar with recovering devices and proper bug reporting.
https://developers.google.com/android/nexus/images
You don't have to wait, you can download LYZ28E, that's what am using without any issues.
And am on Verizon.
has anybody been using xposed and is it far more buggy than simply putting a ROM like chroma on?
Also, is there a dedicated xposed link for nexus 6 on xda or any central page or is this my only resource
http://repo.xposed.info/module/de.robv.android.xposed.installer
Thx
if you are rooted and want the OTA you have to do a few steps to make it work.
flash the stock system image of whatever build you are currently on. just the system image, nothing else. grab the OTA zip file then sideload it. once sideloaded, reroot the phone.
Related
My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
...
Sent from my XT1058 using XDA Premium 4 mobile app
kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.
I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)
Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app
I have a Nexus 6 with a lot of mods: unlocked, rooted, decrypted, twrp installed, franco-kernel, double-tap to wake and xposed. I'd like to upgrade my phone to 5.1 but with all these mods, which is the best solution? Waiting for a flashable 5.1 zip?
I don't want to lose all my settings and saves. And since in a future i'd like to update to a new android version, I ask to understand how you (nexus users) usually do upgrades with mods inside..
mouse100 said:
I have a Nexus 6 with a lot of mods: unlocked, rooted, decrypted, twrp installed, franco-kernel, double-tap to wake and xposed. I'd like to upgrade my phone to 5.1 but with all these mods, which is the best solution? Waiting for a flashable 5.1 zip?
I don't want to lose all my settings and saves. And since in a future i'd like to update to a new android version, I ask to understand how you (nexus users) usually do upgrades with mods inside..
Click to expand...
Click to collapse
You can either wait it out to not lose anything, or you can lose your mods and update, that's about it, that's why I usually stay pretty stock and if I ever want to upgrade, I'm not really losing anything worth having
Sent from my Nexus 6 using XDA Free mobile app
Ask yourself what's going to change in your life if you go to 5.1 today? Some people do have good reasons.
I am waiting a few days myself as my phone runs perfectly fine.
Sent from my Nexus 6
i have the exact same question as well lol and have no idea what to do next...
i am rooted, bootloader unlocked, with twrp and decrypted
i guess i will have to flash a 5.1 rom and bootloader/kernel/radio??
I believe you leave out the kernel as that is what allows you to have a decrypted device.
My advice - wait until there is a decrypted 5.1 zip and flash that.
Personally, I use a new version of Android as a reason to wipe and start fresh. Look at all the bootlooping and junk that's happening to people right now who are quick to want to update. I doubt Xposed works on 5.1 as well.
No it doesn't
I am on T-Mobile Nexus 6 with 5.0.1, rooted with NRT (used Chainfire + TWRP Recovery). I have been expecting to get a notification to update to 5.1 within the device, but haven't gotten anything, even when I manually check for updates from the device (Settings > About > Update). Do I need to do something manually since I am rooted? I also looked for the 5.1 M build on Google's repository and couldn't find it. Thanks for the help!!
Over the air will not apply with a custom recovery. you can be patient and wait for M (NRT will update < 12 hours after Google does) or you could flash a stock recovery and OTA.
If you wait and use NRT there will be an option for the M version and then you can just do a flash to that version with the retain user option
Sent from my Google N6 on VZ
theres a stock, rooted T-Mobile build in the development section. Just flash that
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
OGMCVilleTC said:
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
Click to expand...
Click to collapse
Except the method posted immediately before your post.
I'll look for it. Thanks for the info.
Anyone know if we'll be able to keep root one the lollipop ota comes out on the 10th? If not will a prerooted IMG become available? I do like lollipop but I like having WiFi tether and v4a is awesome. Anyone have an idea what will happen taking the ota while rooted.
Sent from my Nexus 7 using XDA Free mobile app
graymonkey44 said:
Anyone know if we'll be able to keep root one the lollipop ota comes out on the 10th? If not will a prerooted IMG become available? I do like lollipop but I like having WiFi tether and v4a is awesome. Anyone have an idea what will happen taking the ota while rooted.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If you take the OTA, it will replace your rooted image with one that does not have root, and you will lose it. It will also update your bootloader and likely patch whatever exploit that mofo uses, rendering it useless. You will be stuck with a rootless, locked down lollipop for the foreseeable future. Should you decide not to take the OTA, there is a chance that you will be able to flash a rooted lollipop image and get the best of both worlds. Easy choice in my opinion. Computerfreak (the guy who makes the awesome modded images in the development forum) has said that he will support a rooted lollipop image assuming that it is compatible with mofo.
graymonkey44 said:
Anyone know if we'll be able to keep root one the lollipop ota comes out on the 10th? If not will a prerooted IMG become available? I do like lollipop but I like having WiFi tether and v4a is awesome. Anyone have an idea what will happen taking the ota while rooted.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
You won't be able to get update with a modded device, it'll show up but not flash.
Sent from my XT1254 using XDA Free mobile app
With kingeoot you will be able to get root but of course it will be temporary
meanmug said:
You won't be able to get update with a modded device, it'll show up but not flash.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I've read reports that you can use moforoot to flash an unmodified image and set the firmware status back to unmodified. That may allow you to take the OTA. Or it may not. Even if it doesn't, you should still be able to update it via PC and Motorola's update software. But again, why would you want to?
does this image have the kernel included. i thought that was the big difference between kitkat and lollipop is the kernel change. if we cannot overwrite the kernel than what kinds of lollipop image would we be getting? i may be completely misunderstanding this
johnbravado said:
does this image have the kernel included. i thought that was the big difference between kitkat and lollipop is the kernel change. if we cannot overwrite the kernel than what kinds of lollipop image would we be getting? i may be completely misunderstanding this
Click to expand...
Click to collapse
What image are you referring to? If you're talking about the hypothetical image that I mentioned, I was talking about the stock KitKat image. Once you flash a stock, unrooted KitKat image using mofo, it removes the system modified status, which theoretically means you can then OTA to lollipop. But, as I mentioned before, there's a 99.9999% chance that this OTA will update the bootloader and patch the mofo exploit, which means you would lose mofo functionality permanently.
If you're referring to a hypothetical rooted lollipop image that we could flash with mofo, I'm fairly sure that the kernel resides in the system partition, which is the partition that mofo flashes, therefore we shouldn't have any issues flashing a new kernel.
Disclaimer: I'm not a developer. My education is limited to tinkering and Google University.
Until the update is available, nobody knows anything for sure. This is all just speculation, as nobody has the update yet!
Most likely you won't be able to take the update without first reverting to the stock image. I did that when I got a screen replacement
Whether MOFO will work after the update, nobody knows. Someone will have to be the guinea pig.
Personally I would not attempt to install any OTA update unless you don't mind that you will likely lose root and may not be able to get it back.
Once the update is available, and someone is able to dump an image of it and modify it to be rooted, then we will be able to see if MOFO can still be used to flash it to the phone.
PittAussie said:
Until the update is available, nobody knows anything for sure. This is all just speculation, as nobody has the update yet!
Most likely you won't be able to take the update without first reverting to the stock image. I did that when I got a screen replacement
Whether MOFO will work after the update, nobody knows. Someone will have to be the guinea pig.
Personally I would not attempt to install any OTA update unless you don't mind that you will likely lose root and may not be able to get it back.
Once the update is available, and someone is able to dump an image of it and modify it to be rooted, then we will be able to see if MOFO can still be used to flash it to the phone.
Click to expand...
Click to collapse
mofo WILL NOT work once the lollipop update is applied, and you will not be able to downgrade. The only chance is if you are able to update just the kernel(boot)(using fastboot) and system image(using mofo) from the stock image, and not the bootloader
so, this may be perposterously dumb, but how possible would flashing a boot.img be using Flashify? It made a stock backup just fine. Maybe it is a dumb question bc i dont think it would stick on reboot, but thought id ask.
edit: okay...somewhere along the way flashify stopped working. i do still have my backup, though.
edit 2: a titanium backup restore revealed version 1.8.4 is what i used that worked.
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
joshpdavis80 said:
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
Click to expand...
Click to collapse
Hopefully you know how to use ADB and Fastboot. If not, here's a good tutorial > http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
From where you are at, you will start by downloading the latest factory image (MMB29Q) from here > https://developers.google.com/android/nexus/images
Then fastboot flash the bootloader.img, radio.img, boot.img, and system.img. Use Method 2 (Long Method). The "flash_all" script doesn't work. Here's a tutorial for that > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
joshpdavis80 said:
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
Click to expand...
Click to collapse
Take your time and make sure you have everything set up right. Macs are known for causing issues when working with android devices. Also never use a root kit. They only cause more issues then they fix. This is the reason people wont help others that have used one of the kits. You do yourself a great injustice by using them.