Database Users

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

Official CM13 for Nexus 9 is here

Who want official CM 13 rom for Nexus 9?
Official Cyanogenmod 13 rom for nexus 9 and nexus 9 lte is out.check out source link for download link.
So give it a try and share some bugs here.
Source:Download Official CM13 for Nexus 9

Not booting for me (Volantis Wifi)

Which bootloader is needed?
the lollipop one: bootloader-flounder-3.44.1.0123.img?
The marshmallow bootloader-flounder-3.48.0.0135.img from MRA58N is the wrong one?
This could be the problem...

I've been running this all day. First time I forgot to prevent encryption and so I had to wipe everything and start over. Next time used FED patcher. After testing a little I added ElementalX. So far I haven't seen any issues at all.

sejmand said:
Which bootloader is needed?
the lollipop one: bootloader-flounder-3.44.1.0123.img?
The marshmallow bootloader-flounder-3.48.0.0135.img from MRA58N is the wrong one?
This could be the problem...
Click to expand...
Click to collapse
I went from stock 6.0.1 (MMB29K) and had no problems.
---------- Post added at 05:38 PM ---------- Previous post was at 05:06 PM ----------
Bugs
1. Settings->Sounds->Vibrate section is buggy. Toggle is non-functional and clickable part crashes Settings.
2. Settings->Notifications->App notifications crashes Settings.
I am very impressed by this first nightly!

Works well
Sent from my Nexus 9 using Tapatalk

Iceman66 said:
Not booting for me (Volantis Wifi)
Click to expand...
Click to collapse
Flashed boot.img and vendor.img from stock 6.0.1, and now works well.
::highfive:

Latest build available on official cyanogen site.
Here is download link :
http://download.cyanogenmod.org/?device=flounder
Sent from my SM-G925I using Tapatalk

Hooray for fscking ForceEncrypt... Yep, forgot to disable it.

Guys I have a question!
Do I have to flash SuperSU after enabling root?

Superuser is a part of cm. Developer options -> enable root

Can i know which gapps you guys are using? I tried a few and they didn't work. Also, is there a way to check how large cm13 actually is? I might want to try twrp's resize partition with my 16gb model. One last question do i need to use the FED zip if i use a kernel that doesn't require encryption? Thanks
Edit: read chainfire's warning don't think i'll resize

whowatchlist said:
Can i know which gapps you guys are using? I tried a few and they didn't work. Also, is there a way to check how large cm13 actually is? I might want to try twrp's resize partition with my 16gb model. One last question do i need to use the FED zip if i use a kernel that doesn't require encryption? Thanks
Edit: read chainfire's warning don't think i'll resize
Click to expand...
Click to collapse
OpenGapps Pico with no problems.
I think the TWRP resize will only increase a partition's size, not decrease. I came across the following information from the official TWRP site here.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
Click to expand...
Click to collapse

pavan dudyala said:
Do I have to flash SuperSU after enabling root?
Click to expand...
Click to collapse
Yes, download supersu 2.62-3 from Chainfire, supersu 2.52 doesnt work in this ROM.

dmantilal said:
Hooray for fscking ForceEncrypt... Yep, forgot to disable it.
Click to expand...
Click to collapse
How do you disable force encrypt
And how do you remove encryption

Am I right?
I'm on 6.0.1 stock rom (open bootloader, wfi-version)
Can I flash cm13 like this:
reboot bootlaoder, flash twrp 2.8.7.1, boot recovery, flash cm13, gapps and reboot?
What is important with encryption because mine is encrypted?
Works this with encryption? (noob question!)

Iceman66 said:
Yes, download supersu 2.62-3 from Chainfire, supersu 2.52 doesnt work in this ROM.
Click to expand...
Click to collapse
Why supersu? Why not use the CM's built-in(Developer options->Root access-><your needs>)?
sejmand said:
Am I right?
I'm on 6.0.1 stock rom (open bootloader, wfi-version)
Can I flash cm13 like this:
reboot bootlaoder, flash twrp 2.8.7.1, boot recovery, flash cm13, gapps and reboot?
Click to expand...
Click to collapse
Yes:good:
sejmand said:
What is important with encryption because mine is encrypted?
Click to expand...
Click to collapse
You need to wipe /data:good:
sejmand said:
Works this with encryption? (noob question!)
Click to expand...
Click to collapse
Yes:good:

Anyone noticing any battery life improvements

jeff5891 said:
How do you disable force encrypt
Click to expand...
Click to collapse
FED-Patcher
jeff5891 said:
And how do you remove encryption
Click to expand...
Click to collapse
Format /data within TWRP.
PS - After formatting /data, you may want to switch the file-system back to F2FS, since formatting defaults to ext4.

I got a weird issue with this. Flashing works (used arm64 gapps mini, though pico or stock makes no difference) and the latest CM13 nightly (but the earlier ones made no difference):
Whenever I try to log in a google account, no matter whether via trying to type in the mail address or via remote-device-setup, it crashes Google Play Services.
I checked the permissions - GPS has all of them.
I checked the keyboard, doesn't matter which I use (since it crashes the moment the keyboard comes up when trying to type in the mail address). Though since remote setup didn't work either, I was expecting this to not be the cause.
Tried different CM versions, tried different Gapps, no change whatever I try. Everything else seems ok, just cannot log in a google account.
Anyone else had this?

OTA Update with systemless root

I just received a notification on my 6P saying that the january security update is available. The thing is that I'm rooted with systemless root, xposed, EX Kernel and TWRP. Can I update using the update button?

With systemless I believe you should be able to.

I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol

Pain-N-Panic said:
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Click to expand...
Click to collapse
No.
If you have TWRP installed you will not be able to take an OTA.
Why bother?
Just flash what you want.

Ok, so if I reboot and my phone tries to install the OTA, what happens?

I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition

This update message won't go away. Can I flash it myself through TWRP with Xposed installed?

You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.

dratsablive said:
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.

Pain-N-Panic said:
Ok, so if I reboot and my phone tries to install the OTA, what happens?
Click to expand...
Click to collapse
Nothing happens. it'll just fail to flash the update. It'll reboot to twrp, attempt to flash the update, and it'll fail the flash. So it just won't flash. Then you'll just reboot the system and nothing will be changed. I think you can flash these minor changes, but if you try to flash a major update through OTA it won't work with out stock recovery because that's part of the flash I think
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
regenwurm16 said:
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
Click to expand...
Click to collapse
It does not bored because of mismatched kernel. Because I tried flashing the stock kernel and then OTA and it still did not work

kirkgbolton said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Click to expand...
Click to collapse
This. At this time it's the only fix. I did it as well. Never flashed a factory image via fastboot before so I was a little intimidated but Heisenberg's guide is so smooth and easy to follow I did it in about 5 minutes lol. Plus it was a great learning experience for me.

Is it likely that eventually TWRP flashable zips will make this process easier? Or is there some sort of restriction with these updates for Nexus phones that will always require fastboot?

Not sure. I do know that the above method only took me about 10 minutes. Yeah it sucks you have to utilize a PC to do it but its really not that bad. Maybe in the future someone will figure out how to implement the updates via flashable zip in recovery.

I struggle with this too. I really hope that someone will find a solution to flash it via .zip (sadly I'm more a programmer than an Android-hacker, otherwise I would try my very best right now ).

Just to point it out, it looks like the article you are referring to has been updated since it was linked. I wouldn't want to wipe userdata, so I think 11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact) is what you were referring to at the time. Apologies for the resurrection.

I just used the FlashFire app to update my Nexus 6p with the February update and it worked like a charm.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/

Android N Preview 4 beta npd56n (flashable & image, no encryption & dm verification)

Android N Preview 4 beta npd56n (flashable & image, no encryption & dm verification)
** DISCLAIMER: APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview 4 image released by Google on 6/16/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2 **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 or higher installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 4 beta. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N 4 beta with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.74 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.

If coming from MM is method 1 an option?
Sent from my Nexus 6 using XDA-Developers mobile app

MrMiami81 said:
If coming from MM is method 1 an option?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Both methods work regardless of what android version you start with.

MrMiami81 said:
If coming from MM is method 1 an option?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You have to be on N bootloader and radio, but, yes the method 1 is for MM to N

gothy.gothy said:
You have to be on N bootloader and radio, but, yes the method 1 is for MM to N
Click to expand...
Click to collapse
In either method that I have posted here you can be on any radio, any bootloader, or any kernel. It will always work regardless.

najoor said:
In either method that I have posted here you can be on any radio, any bootloader, or any kernel. It will always work regardless.
Click to expand...
Click to collapse
That means that your zip contains already the new N bootloader and radio. Bye the way, are they different from N3?

gothy.gothy said:
That means that your zip contains already the new N bootloader and radio. Bye the way, are they different from N3?
Click to expand...
Click to collapse
Yes, my zips include both radio and bootloader. As far as I can tell N4 radio and bootloader are the same as N3.

Android Pay

lioryte said:
Android Pay
Click to expand...
Click to collapse
It broke? I finally was able to confirm pay was working fully for me on dp3.
Sent from my Nexus 6 using Tapatalk

angiest said:
It broke? I finally was able to confirm pay was working fully for me on dp3.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
WAS working great. Ain't working now, just FYI before upgrading

It was for preview 3
Sent from my Nexus 6 using XDA-Developers mobile app

I´m on marshmallow with a custom kernel, what is the best metod for me?

any mirrors yet?

I tired to Root with Nexus root Tool kit Preview 4 and Got The Dead Android No Command

is skype working or library problems , can someone check if gdmss hd lite is working when connecting to a camara ? in dp3 fails with library problems

Can't even Flash it, twrp(3.0.2-0) is stuck on "trying decryption"?

No problems with install.
1. System Restore
2. Flash ROM,kernel,adaway fix and SU2.74
Only problem I find now is TiBu won't restore APP's it will restore some settings and call logs though.
Found a few other things that are not working correctly. Not sure if it's ROM related. Root Explorer and Explorer lock up when opened.
I have wiped and tried everything twice all with same results.
3rd time is the charm. Did a full wipe and install now these apps are working.

Does this work for Verizon? HD calling

Slingbox app didn't work on preview 3 that's my main reason I'm back on MM
Sent from my Nexus 6 using XDA-Developers mobile app

You'll most likely will need to go back into secret menu and turn it back on.. That's what you do when you flash new radios
ncwildcat said:
Does this work for Verizon? HD calling
Click to expand...
Click to collapse
Sent from my Nexus 6 using Xparent Cyan Tapatalk 2

Android N Preview 5 beta npd90g (flashable & image, no encryption & dm verification)

Android N Preview 5 beta npd90g (flashable & image, no encryption & dm verification)
** DISCLAIMER: APPLY AT YOUR OWN RISK **​** The following are instructions for installing Android N Preview 5 image released by Google on 7/18/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2 **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 or higher installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 5 beta. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N Preview 5 beta with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.76 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.

Cool thanks.. Will android pay still work?

The link doesn't work for me (method 1). Brings up a blank page.
edit - sorry, I see it's still being uploaded. When I first looked on my phone it said this was posted at 5:37 am. When I logged in on my computer just now it says 11:37 pm (25 min ago).

Thanx! Just got the OTA Update available message - can I flash the OTA as well when I am coming from your unencrypted Android N4?

yeticomes said:
Thanx! Just got the OTA Update available message - can I flash the OTA as well when I am coming from your unencrypted Android N4?
Click to expand...
Click to collapse
If you take the google OTA your phone will be encrypted and your recovery will be replaced with google's. If you want to keep the recovery and unencrypted sdcard then flash the flashable file above (method 1) that I just finished uploading.

do you have to be on N already, to flash using method #1, and also, are the normal wiping methods required?

i4cbj45 said:
do you have to be on N already, to flash using method #1, and also, are the normal wiping methods required?
Click to expand...
Click to collapse
You can be on whatever rom you want. Just do a full wipe (data,system etc) and don't wipe sdcard. Then make sure you have TWRP 3.0+. And just flash the zip from method 1. I just did and it's working perfect.
Thanks @najoor !

Why is it always after I post that I realized what I did wrong? LOL edited and deleted.
Sent from my Nexus 6 using XDA-Developers mobile app

Can someone post a direct browser link, as yet again, I cannot download the file. Thanks.

can somebody upload the flashable no-encrypted zip ? i only want to flash that after the clean reinstall.

Works great thanks bud
Sent from my Nexus 6 using XDA Free mobile app

I'm currently on preview 4 with twrp and root with elemental. Do I need to restore the stock kernel before flashing method 1?
Thanks for your work on this, najoor!
Edit - Autocorrect mis-correcting my spelling
Sent from my Nexus 6 using XDA-Developers mobile app

a8ksh4 said:
I'm currently on preview 4 with twrp and root with elemental. Do I need to restore the stock kernel before flashing method 1?
Thanks for your work on this, najoor!
Edit - Autocorrect mis-correcting my spelling
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
No but your kernel will be replaced with N kernel and if any of your apps depend on the elemental kernel they will stop working.

ronaldheld said:
Can someone post a direct browser link, as yet again, I cannot download the file. Thanks.
Click to expand...
Click to collapse
SamS1989 said:
can somebody upload the flashable no-encrypted zip ? i only want to flash that after the clean reinstall.
Click to expand...
Click to collapse
https://zenety.stackstorage.com/index.php/s/8l9jCllpEIaaEMa/download

Can someone report the baseband version on this? Is it the 5.39R?
Thanks. And thank you OP!
Edit/Update :
It is indeed 5.39R. Thanks again.

Hotspot works after adding build.prop line

Thank you najoor, for making this process easier and possible for us to get a run at the preview

Hotspot works?
Sent from my Nexus 6 using Tapatalk

ArieleGiron said:
Hotspot works?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Look 2 posts up^^^

yankeesfan714 said:
Look 2 posts up^^^
Click to expand...
Click to collapse
Thanks buddy!!
Sent from my Nexus 6 using Tapatalk