I have decompressed the Nexus 6P factory images and extracted the system.img and and converted it into a TWRP recovery flashable zip. Enjoy
Instructions:
Download ROM
Copy to phone
Boot into recovery (TWRP, etc.)
Make a backup
* Wipe system, data, delvik cache, and cache (if coming from non-stock ROM)
* Wipe devlik cache and cache (if coming from a stock ROM)
Flash ROM
Reboot
Downloads:
Latest Build: 6.0.0-MBD08K
Android 6.0.0
Build MDA89D: LINK
Build MBD08K: LINK
NOTE: These ROM are based on an UNMODIFED version of the stock factory images! NO CHANGES IN ANY WAY WERE MADE to the stock firmware
XDA:DevDB Information
[ROM]Nexus6P Stock ROMs, ROM for the Huawei Nexus 6P
Contributors
Shawn5162
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Stable
Created 2015-10-27
Last Updated 2015-10-26
Reserved
Reserved because I can
Probably never going to use this post but it seams to be a tradition by XDA devs
You've been busy in the XDA kitchen!
Thanks for the hard work! My 6P arrives tomorrow
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
What's the difference between the two? (I feel like I should know this already) ☺
Is TWRP out for nexus 6p?
Let the cooking begin!
bradputt said:
Is TWRP out for nexus 6p?
Click to expand...
Click to collapse
Nope ...Thought I would release this before though.
I am working on a custom TWRP build as we speak though. I will probably release it within a few days.
Also @Dees_Troy is working on official TWRP which should also be coming out within the next few days.
Shawn
kingmikel said:
Thanks for the hard work! My 6P arrives tomorrow
Click to expand...
Click to collapse
how long did yours say "pending"?
dontbeweakvato said:
how long did yours say "pending"?
Click to expand...
Click to collapse
It said "pending" for about a week, then it switched to "processing" for a little over a day, then finally "shipped" :good:
Danish2980 said:
What's the difference between the two? (I feel like I should know this already)
Click to expand...
Click to collapse
Yes please I'd like to know as well.....I've done some unsuccessful searching for this as well.
ggeralds said:
Yes please I'd like to know as well.....I've done some unsuccessful searching for this as well.
Click to expand...
Click to collapse
Ok. So basically when Google updates the AOSP sources (with multiple commits) they push a new build. These new builds also contain security patches and bug fixes (very minor ones). These updates don't add new features most of the time (if they are based on the same android OS version). I have added a new line in the OP where I write the build number for the latest build. This should help people find the latest build faster.
Shawn
Hah, glad to see Shawn here, developed such a good rom for Moto G 2014, hope you will continue your efforts for 6P as well
emiwonder said:
Hah, glad to see Shawn here, developed such a good rom for Moto G 2014, hope you will continue your efforts for 6P as well
Click to expand...
Click to collapse
Nice to see you here too
IS this 1 rooted?
New factory image with the November secruity patch :https://dl.google.com/dl/android/aosp/angler-mdb08m-factory-dbc17940.tgz
MDB08M
NovaSlim said:
New factory image with the November secruity patch :https://dl.google.com/dl/android/aosp/angler-mdb08m-factory-dbc17940.tgz
MDB08M
Click to expand...
Click to collapse
Question about these images from google (first time nexus user, long time crack-flasher here). If i'm running stock and simply want to update to the new build, can i just extract the system image from that package and just flash it via fastboot or will that break things?
Can't wait for latest build thanks for throwing these together!
Sent from my Nexus 6P using Tapatalk
djuniah said:
Question about these images from google (first time nexus user, long time crack-flasher here). If i'm running stock and simply want to update to the new build, can i just extract the system image from that package and just flash it via fastboot or will that break things?
Click to expand...
Click to collapse
That won't boot(you be stuck on the google screen forever), you need to fastboot flash the vendor.img as well. For details:
http://forum.xda-developers.com/nex...-cleancore-n6p-100-lean-stock-mbd08k-t3235306
Related
Main thread: OpenPDroid patches for CyanogenMod 11
WARNING: OpenPDroid is not compatible with ART for now. disable ART before flashing. enabling ART will cause the device to fail to boot. if you enabled ART and are unable to boot, flash official CyanogenMod temporarily to be able to fix (will cause privacy leaks). or if you have ADB access in android or recovery, you can disable ART by using setprop or editing a file.
these are i9100 builds of CyanogenMod 11 patched with OpenPDroid. find them here.
update: releases will now be distributed as overlays to the official CyanogenMod snapshots. first flash the official "M" snapshot corresponding to the OpenPDroid overlay you want to flash, then flash the overlay.
update: i have published an OpenPDroid overlay for the i9100 build of CM 10.1.3 here (made with old Auto-Patcher).
update: device-specific builds are being phased out in favor of the generic overlays. please refer to this post.
note: OpenPDroid does not affect the recovery nor the kernel, you can use whatever you want.
CM11-M6 broke OpenPDroid patches, so i forked OpenPDroid to restore compatibility, fix several bugs and clean up the code. sources are here.
XDA:DevDB Information
CM11-OpenPDroid-i9100, ROM for the Samsung Galaxy S II
Contributors
Lanchon
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2014-07-16
Last Updated 2014-10-08
rom is uploading now, please wait a bit...
Features and screenshots mate
george_shudi said:
Features and screenshots mate
Click to expand...
Click to collapse
lol
google openpdroid and pdroid
Some screenshots and battery life will be welcome.
Thanks, will try soon .
sorry! i just found out that Dropbox suspended my public links due to too much traffic, i didn't know this could happen. i'll arrange an alternative asap.
danielk68 said:
Some screenshots and battery life will be welcome.
Click to expand...
Click to collapse
this is just nightly CM11 with openpdroid! screenshots and battery are exactly like CM's.
mate your roms are not working ,, even ur links are not working anymore.
george_shudi said:
mate your roms are not working ,, even ur links are not working anymore.
Click to expand...
Click to collapse
lol did you even read my previous to last post?
Lanchon said:
lol did you even read my previous to last post?
Click to expand...
Click to collapse
yes i did .. i have downloaded ur roms since today morning and i've flashed them but none of them are working.
george_shudi said:
yes i did .. i have downloaded ur roms since today morning and i've flashed them but none of them are working.
Click to expand...
Click to collapse
ok thanks. i only posted one rom for the i9100. are you sure you didnt flash one of the nexus 5 images? they have hammerhead on the filename.
Lanchon said:
ok thanks. i only posted one rom for the i9100. are you sure you didnt flash one of the nexus 5 images? they have hammerhead on the filename.
Click to expand...
Click to collapse
no hammerhead won't accept to flash ... i've flashed the one one with the date 16/7/2014 and done flashing then reboot but nothing happened just black screen.. i'm using Biftor slim rom now ... i just want to report ur rom to u.
george_shudi said:
no hammerhead won't accept to flash ... i've flashed the one one with the date 16/7/2014 and done flashing then reboot but nothing happened just black screen.. i'm using Biftor slim rom now ... i just want to report ur rom to u.
Click to expand...
Click to collapse
ok thank you. i dont have an i9100 so i can't test. that's why this rom is not in ALPHA but TESTING stage. i pulled the blobs from a non-local friend's phone over VPN and built. but i am running the hammerhead version and it works just fine (and so does openpdroid). i don't know why it may not be working. maybe that CM's nightly is bad. maybe there's something bad with my building (i strongly suppose nothing's wrong with openpdroid). maybe you didn't wipe or the download was busted. (there is *no* need to wipe coming from CM11.) if someone else confirms i will sync and rebuild and maybe build without patching to see if the output works. thank you!
Dropbox error 509
matias6142 said:
Dropbox error 509
Click to expand...
Click to collapse
files are now live again, sorry for the outage!
Lanchon said:
files are now live again, sorry for the outage!
Click to expand...
Click to collapse
images i don't see
new build is up!!!
this time i reproduced the official M8 snapshot, so it should be more stable. enjoy!
Lanchon said:
new build is up!!!
this time i reproduced the official M8 snapshot, so it should be more stable. enjoy!
Click to expand...
Click to collapse
the package is bad.
chuangdi said:
the package is bad.
Click to expand...
Click to collapse
crap!!! can you please describe in more detail?
i don't have an i9100, so i havent tested this build.
EDIT: i had a friend with an i9100 remotely connect to to my VPN, then had him enable root adb over net, then i picked the blobs from his phone with the standard script. there were no errors reported. maybe something went wrong???
2ND EDIT:
i think i know what can have gone wrong. he's running CM but infected's CM10.2 modded build. maybe i need to pick the blobs from someone running standard CM11.
does anybody running "stock" CM11 want to help? i'd need brief remote adb access. i think root is required to pick the blobs, but not sure.
Here are the bootloader/radio/vendor images ROMs with Google's flashing scripts.
This is all you want if your running a ROM.
If your running stock, you will want to get the images directly from Google.
If your not sure, ask your ROM's dev team.
Folder
http://www.emccann.net/dho/9-Experimental-physics-lab/angler/
7.X Releases: Most recent on bottom
NRD90U
NBD90X
NBD91k
NMF26F <-- All carriers except Verizon (per Google)
N4F26I
N4F26J
N4F26O <-- All carriers except Verizon
NUF26K <-- Verizon
N4F26T <-- All carriers except Verizon
NUF26N <-- Verizon
N4F26U
N2G47H
N2G47O
N2G47W
N2G48B
N2G48C
6.0 Releases: Most recent on bottom
MMB29P
MMB29Q
MMB29V
MHC19I
MHC19Q
MTC19T
MTC19V
MTC19X
MTC20F
MTC20L
FLASHABLE 6.0 Releases: Most recent on bottom
*** Flashable images are from NuclearMistake. This is NOT how Google intended you to flash, but works.
MTC19X
MTC20F
MTC20L
NBD91K
What does each release do?
Google Security Bulletin
If your not sure how to flash them:
http://lmgtfy.com/?q=How+to+flash+bootimages+on+android
The real question is why would we flash it?
Sent from my Nexus 6P using Tapatalk
DHO said:
Here are the bootloader/radio/vendor images for mhc19q AKA 6.0.1_r24
This is all you want if your running a ROM. If your running stock, you will want to get the images directly from Google. If your not sure, ask your ROM's dev team.
http://www.emccann.net/dho/9-Experimental-physics-lab/angler/angler-mhc19q.zip
If your not sure how to flash them:
http://lmgtfy.com/?q=How+to+flash+bootimages+on+android
Click to expand...
Click to collapse
Good to have a collection. You could do one thing, rename the thread to [Collection] Bootloader, Radio, and Vendor Images for Angler.
Sent from my Nexus 6P using XDA-Developers mobile app
borisb said:
The real question is why would we flash it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's the latest and greatest of course! I'm on stock, so I'll just wait for OTA but if you're bootloader unlocked it's best to flash these via adb so your device stays up to date at least with the BL, radio, and vendor.
farfromovin said:
It's the latest and greatest of course! I'm on stock, so I'll just wait for OTA but if you're bootloader unlocked it's best to flash these via adb so your device stays up to date at least with the BL, radio, and vendor.
Click to expand...
Click to collapse
Ohh nice.
Thanks
I'm actually locked. When is the OTA scheduled to arrive?
Sent from my Nexus 6P using Tapatalk
DJBhardwaj said:
Good to have a collection. You could do one thing, rename the thread to [Collection] Bootloader, Radio, and Vendor Images for Angler.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Agreed. I have all the previous ones for backup, just in case one day I were to flash a ROM developed at a past date. Having a collection thread for that from you (@DHO ) would be nice.
borisb said:
Ohh nice.
Thanks
I'm actually locked. When is the OTA scheduled to arrive?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The OTA roll-out has begun already for MCH19Q, but may take a few days, to one or two weeks to cover worldwide.
DHO said:
Here are the bootloader/radio/vendor images for mhc19q AKA 6.0.1_r24
This is all you want if your running a ROM. If your running stock, you will want to get the images directly from Google. If your not sure, ask your ROM's dev team.
http://www.emccann.net/dho/9-Experimental-physics-lab/angler/angler-mhc19q.zip
If your not sure how to flash them:
http://lmgtfy.com/?q=How+to+flash+bootimages+on+android
Click to expand...
Click to collapse
Forget what the user above said. You have all the rights to post external links on XDA-Developers. If he (The XDA fanatic who cannot tolerate other websites on the internet) feels that your or mine or anyone else's work is a piece of junk, then he should just write it by himself.
@DHO you go on with your work, and maintain the forum's spirit. Ignore such criticizers. At least some of us here can act mature and ignore such useless discussions. Off-topic ended here, mods can clean-up if they want.
DJBhardwaj said:
Forget what the user above said. You have all the rights to post external links on XDA-Developers. If he (The XDA fanatic who cannot tolerate other websites on the internet) feels that your or mine or anyone else's work is a piece of junk, then he should just write it by himself.
@DHO you go on with your work, and maintain the forum's spirit. Ignore such criticizers. At least some of us here can act mature and ignore such useless discussions. Off-topic ended here, mods can clean-up if they want.
Click to expand...
Click to collapse
Thanks
We move 15 terabytes of ROMs on a slow month, XDA wants nothing to do with that bandwidth
But I do see the wisdom in a collection type post....
Maybe after work I can a make something a bit more unified.
DHO said:
Thanks
We move 15 terabytes of ROMs on a slow month, XDA wants nothing to do with that bandwidth
But I do see the wisdom in a collection type post....
Maybe after work I can a make something a bit more unified.
Click to expand...
Click to collapse
Looking forward to that.
As recommended this is now a collection thread.
And the latest and greatest:
MTC19T
DHO said:
As recommended this is now a collection thread.
And the latest and greatest:
MTC19T
Click to expand...
Click to collapse
Adding the link to the security bulletin would be a nice idea. What do you say?
For MTC19T: https://source.android.com/security/bulletin/2016-05-01.html
Good idea,
Done
What information/purpose does this 'collection' offer aside from what is already being offered by Google at https://developers.google.com/android/nexus/images#angler
hacksome said:
What information/purpose does this 'collection' offer aside from what is already being offered by Google at https://developers.google.com/android/nexus/images#angler
Click to expand...
Click to collapse
This is meant for custom ROM users - we no longer need to download the *full* factory image even if we're just updating our /vendor monthly.
I personally am grateful for such a collection, not only because of the data flow it saved me, but also because of its convenience (Google is not accessible by normal means in China).
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Does it meant that if I want just to get security updates (running stock rom) I just need to flash vendor.img? No system.img is needed?
adam_pl said:
Does it meant that if I want just to get security updates (running stock rom) I just need to flash vendor.img? No system.img is needed?
Click to expand...
Click to collapse
Nope. ROMs and the partitions supplied here needs to be updated hand in hand. It's the ROM itself (the kernel) that contains the patches.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
Nope. ROMs and the partitions supplied here needs to be updated hand in hand. It's the ROM itself (the kernel) that contains the patches.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Click to expand...
Click to collapse
Thanks
Wysłane z mojego Nexus 6P przy użyciu Tapatalka
AndyYan said:
Agreed. I have all the previous ones for backup, just in case one day I were to flash a ROM developed at a past date. Having a collection thread for that from you (@DHO ) would be nice.
Click to expand...
Click to collapse
I thought they were backwards compatible?
VanillaCracker said:
I thought they were backwards compatible?
Click to expand...
Click to collapse
Radio and Bootloader are backward compatible. However, for some, an older radio version could work better than the most recent one, on the latest update. So you may regard Radio as subjective.
As for vendors, they should be flashed corresponding to their build numbers, so you could say that these are NOT backward compatible
I hope I got your question right. :good:
Project on hold for a moment - my phone didn't like what I built. Going to fix it, then re-open.
So, I got tired of needing my PC to update my phone every month just because I'm rooted. So I used SuperR's Kitchen and took the stock images from Google and made them into flashable zips. These are flashable in TWRP. They are rooted and includes the vendor partition. If enough people request it, I will cook some non-root versions. I plan to add flashable bootloader and radios as well (TBD). I will try to get N zips up and going tonight.
The intention is to keep this up to date every month (until I get a new phone, not likely within the next year or two).
Advice, guidance, and requests are welcome. Doesn't mean I'll follow or fulfill them.
Directions for upgrading from a previous version:
Custom recovery (TWRP) required
Boot into recovery
Flash AOSP-[version]-angler-[build]-bootloader-signed.zip
Flash AOSP-[version]-angler-[build]-radio-signed.zip
Flash AOSP-[version]-angler-[build]-[date]-kernel-signed.zip
Flash AOSP-[version]-Rooted-angler-xxxxxx-[date].zip
OPTIONAL: Flash AOSP-[version]-angler-[build]-recovery-signed.zip (This will replace your custom recovery with the Stock recovery)
Flash any other packages you may want (such as Xposed)
Wipe cache/dalvik
Reboot
Your phone may reboot a time or two during the first boot (mine did). I am the only one that has tested this thus far. Use at your own risk. I am not responsible if this bricks your phone, kills your cat, or your house gets foreclosed on.
If you don't know how to fastboot flash the stock images, you probably should not flash these (just in case).
DOWNLOADS
Please keep in mind: these are hosted on my shared hosting account.
Download speeds will be limited by how many concurrent downloads are happening.
Please let me know if you have any issues downloading and I'll host elsewhere.
6.0.1
May 2016 (MTC19T)
AOSP-6.0.1-Rooted-angler-mtc19t-20160524-signed.zip - 913.7 MB
AOSP-6.0.1-angler-mtc19t-20160524-kernel-signed.zip - 10.1 MB
AOSP-6.0.1-angler-mtc19t-20160524-recovery-signed.zip - 11.1 MB
AOSP-6.0.1-angler-mtc19t-bootloader-signed.zip - 2.3 MB
AOSP-6.0.1-angler-mtc19t-radio-signed.zip - 28.1 MB
N
May 2016 (NPD35K)
COMPLETELY UNTESTED! TRY AT YOUR OWN RISK! ALWAYS PERFORM A NANDROID BACKUP
AOSP-N-Rooted-angler-npd35k-20160524-signed.zip - 1.1 GB
AOSP-N-angler-npd35k-20160524-kernel-signed.zip - 10.4 MB
AOSP-N-angler-npd35k-20160524-recovery-signed.zip - 16.0 MB
AOSP-N-angler-npd35k-bootloader-signed.zip - 2.3 MB
AOSP-N-angler-npd35k-radio-signed.zip - 28.1 MB
XDA:DevDB Information
Pure AOSP Factory, ROM for the Huawei Nexus 6P
Contributors
jparnell8839
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Testing
Created 2016-05-23
Last Updated 2016-05-23
Changelog
2016-05-24
angler MTC19T (6.0.1 - May 1, 2016)
System/Vendor
Kernel
Bootloader
Stock Recovery
Radio
angler NPD35K (N - May 1, 2016)
System/Vendor
Kernel
Bootloader
Stock Recovery
Radio
2016-05-23
Initial Post
angler MTC19T (6.0.1 - May 1, 2016)
System/Vendor
Kernel
reserved again
Thanks for your contribution. Looking forward to this.
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
Thank you for your contribution.
Thanks man. This will come in handy.
Thanks! Didn't even know this is what needed to be done to be able to update with TWRP. Feels good
Great stuff! Kudo's
eagerly waiting for your ANDP3. keep it up mate!
Thanks for this. Could you do the same for Android N preview images? I keep wanting to check it out, but never have time while at a PC.
rainabba said:
Thanks for this. Could you do the same for Android N preview images? I keep wanting to check it out, but never have time while at a PC.
Click to expand...
Click to collapse
Read 3rd and 4th lines of OP. There is a surprise waiting for you..
great contribution for the community! Can't wait for the N zips and more goodies. What version of superSU are they rooted with? The newest 2.74-2 version? Thanks again!
Does Android Pay work on these builds?
Sent from my Nexus 6P using XDA-Developers mobile app
Maybe you should relabel the title. These are just flashable factory images right? It is not the same as AOSP. The changes are minimal but they are there.
Sent from my Nexus 6P using Tapatalk
Smallsmx3 said:
Maybe you should relabel the title. These are just flashable factory images right? It is not the same as AOSP. The changes are minimal but they are there.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Will do. Thanks.
OP Updated. New instructions, new links for 6.0.1, and added N, all the stock images flashable (except userdata and cache).
Please be careful with N. I uploaded, but have not yet tested them myself.
yung40oz84 said:
great contribution for the community! Can't wait for the N zips and more goodies. What version of superSU are they rooted with? The newest 2.74-2 version? Thanks again!
Click to expand...
Click to collapse
BETA-SuperSU-v2.74 is the one used. Pretty sure I renamed to remove the -2 at the end, but whatever was latest as of yesterday. BTW, N zips are up, but untested. I cannot express how new to this I am, and it's possible it could soft brick your phone. I'm testing the new 6.0.1 zips now, I'll test the N once I'm comfy knowing that the others work
So, I don't know what I did, but my phone did not like what I cooked. May have hard bricked it, which means I did something wrong in the bootloader. For the love of God, if you happened to have downloaded anything in the 5 minute window I had it live, don't flash it.
Thanks for this! Just out of curiosity, how often is the radio being updated?
Sent from my Nexus 6P using XDA-Developers mobile app
After getting permission from the OP I decided to post this.
Android N - these are all from/for preview 3
Flashable bootloader: https://www.androidfilehost.com/?fid=24545065934258631
Flashable radio:
https://www.androidfilehost.com/?fid=24549084345926390
Flashable system:
https://www.androidfilehost.com/?fid=24549084345926426
RatchetPanda said:
After getting permission from the OP I decided to post this.
Android N - these are all from/for preview 3
Flashable bootloader: https://www.androidfilehost.com/?fid=24545065934258631
Flashable radio:
https://www.androidfilehost.com/?fid=24549084345926390
Flashable system:
https://www.androidfilehost.com/?fid=24549084345926426
Click to expand...
Click to collapse
Coming from mm we can just flash via twrp and good to go? Do we need to still be decrypted? Is this pre rooted or do we need to flash su? Thanks
Sent from my Nexus 6P using Tapatalk
Hey XDA!
This is just a quick build of AOSP Nougat that I though I should upload and share. It's just pure AOSP with a modified fstab and a bunch of the useless apps removed. While it does boot, the main problem is that there aren't any gapps available, so there is little functionality.
Instructions:
1. Flash vendor.img
2. Flash ROM zip
3. Boot up
Downloads:
Unofficial vendor.img: http://oceighty.co/ Created and uploaded by @xanaxdroid
ROM zip: https://basketbuild.com/ Build and uploaded by me.
DISCLAIMERS:
I'm not responsible for any mishaps you have.
This is simply a courtesy upload, do not expect updates.
The vendor.img was pulled from the OTA and is not an official factory image.
is it rooted?
The latest TWRP version functions with Android N, it now correctly decrypts the phone (yes, I'm aware this ROM is pre-decrypted). You can flash SuperSU through that and then download most of the needed GApps from APKMirror, I know Android N preview GApps were uploaded there.
confused... so I could just flashed this like a regular rom? would my internal disk erase? is this rooted?
you guys need to read the OP and stop asking senseless questions
"It's just pure AOSP with a modified fstab and a bunch of the useless apps removed"
Lol, this is why I wish rooting wasn't just a click away. I miss the old days where you actually had to know what you were doing to root the damn thing like actually being familiar with adb I doubt half the people that root haven't used shell period. Point being that the people that did it knew the ins and outs of what they were doing and there wasnt all this clutter. people used to actually do the time to research and educate themselves on what was going on now it's all entitlement give me give me i don't understand oh blah blah won't work fix it for me anyway this isn't helpful or constructive please delete goodnight
Sent from my Nexus 6P using Tapatalk
Interesting ROM. :good:
Opengapps.org should have 7.0 gapps very shortly. The August 24th build for arm has 7.0, but 8/24 hasn't built for arm64 yet.
Sent from my Nexus 6P using XDA-Developers mobile app
First to market ROM nice!
hibby50 said:
Opengapps.org should have 7.0 gapps very shortly. The August 24th build for arm has 7.0, but 8/24 hasn't built for arm64 yet.
Click to expand...
Click to collapse
ARM64 builds for 7.0 are now available for flashing.
Why do people prefer decrypted roms, what is the advantage?
rest0ck said:
Why do people prefer decrypted roms, what is the advantage?
Click to expand...
Click to collapse
One reason should be faster "iops" I presume.
Skickat från min Nexus 6P via Tapatalk
That was fast, OP your pic looks alot like this dude.
Hm okay I see, thanks.
Can I encrypt it again if I want to?
Also I thought the Source of Android N is not released yet (delevopers.google.com) so where is this source from exactly?
.. Okay I just looked it up. So is there a difference between this one and the official OTA update? I really want to flash another ROM because my Dirty Unicorn is just a mess at the moment.
Iceburn1 said:
That was fast, OP your pic looks alot like this dude.
Click to expand...
Click to collapse
Oh wow! I've never seen that guy around the forums, but you're right!
rest0ck said:
Why do people prefer decrypted roms, what is the advantage?
Click to expand...
Click to collapse
Faster boot, slightly faster I/O (although there isn't too much of a difference).
Thank you for the answer.
Can someone confirm that flashing the lastest SuperSU beta works? http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So basically flashing this ROM + Vendor + ARM64 GApps + SuperSU = Android N, decrypted, rooted, with gapps?
How'd you even build this? I synced r1 and tried a build last night and it wouldn't build (for the 6p). The website doesn't show 6p as included in r1 yet
rest0ck said:
Thank you for the answer.
Can someone confirm that flashing the lastest SuperSU beta works? http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So basically flashing this ROM + Vendor + ARM64 GApps + SuperSU = Android N, decrypted, rooted, with gapps?
Click to expand...
Click to collapse
The latest Beta SU works with 7 NRD90M
rest0ck said:
Thank you for the answer.
Can someone confirm that flashing the lastest SuperSU beta works? http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So basically flashing this ROM + Vendor + ARM64 GApps + SuperSU = Android N, decrypted, rooted, with gapps?
Click to expand...
Click to collapse
Not really, no. The ROM isn't technically decrypted at all. It just doesn't force encryption. So if you were encrypted prior to flashing you would still be encrypted. The only way to decrypt is to format userdata. The advantage of a ROM not forcing encryption (or being incorrectly labelled as decrypted in this case) is that if you were previously decrypted the kernel won't encrypt your storage on the first boot.
This LineageOS 14.1 ROM is built from source for Blu R1 HD.
Some features of this LineageOS 14 rom are:
- Hardware rendered LiveDisplay (no UI lag in night mode)
- Android security patches up to October
- Security hardened kernel (including BlueBorne bluetooth patches)
- Kernel patched for Nougat (Nougat compatible SELinux)
- No Chinese spyware
Credits:
zhaofengli (major thanks for getting the rom booting + hotspot/GPS fix, among other things!)
vampirefo
danielhk (GPS fix)
DeckerSu(Initial device tree, MTK patches)
Sources:
Code:
[URL=https://github.com/blumonks/android_device_blu_p6601]Device Tree[/URL]
[URL=https://github.com/blumonks/android_kernel_mediatek_mt6735]Kernel Source[/URL]
[URL=https://github.com/blumonks/android_p6601]Build Manifest[/URL]
[URL=https://github.com/blumonks/twrp_device_blu_p6601]Recovery device tree[/URL]
Downloads:
LineageOS 14.X Downloads
TWRP Recovery
Click to expand...
Click to collapse
Installation Guide:
1) Flash TWRP recovery (See downloads)
Code:
fastboot flash twrp-3.1.1-0-p6601.img
This TWRP recovery has a different device name than previous versions of TWRP.
2) Boot into recovery (Hold vol up when booting and use vol keys to select recovery)
3) If coming from a non lineageOS rom, please format system, data, and cache in recovery before flashing this rom. Otherwise stale files from previous roms may cause bugs.
5) Flash lineage rom
6) Flash gapps (obtain here: http://opengapps.org/)
Current bugs:
Camera does not work. It is still under active research and development.
Bluetooth
Github Issue Tracker (Please do not open duplicate issues)
Please note that support will be limited.
UPDATED BUILD 24 AUG 2020.
If anyone is still using this device, here is an updated build with the August 2020 Android Security Bulletin & all merged LineageOS changes since October 2017. MAKE SURE YOU FLASH USING THE TWRP IN THE ORIGINAL POST! You can flash over any builds in this thread, the camera still doesn't work and I have no interest in fixing it.
https://www.mediafire.com/file/dbdmk...p6601.zip/file
https://gofile.io/d/vTddMJ
Vulnerability said:
Nice! Can't wait to test it! Any screenshots?
Click to expand...
Click to collapse
It's the same as any other lineage rom. Updated OP.
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Is enforcing SELinux supported? Or only permissive?
EDIT: Don't worry I saw the issue tracker post
I'm gonna try this rom
It's nice to see development alive!!!
Hope you could a finally fix the broken camera
Does anyone know anything about the KRACK vulnerability?
zombie_ryushu said:
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Click to expand...
Click to collapse
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
zombie_ryushu said:
Does anyone know anything about the KRACK vulnerability?
Click to expand...
Click to collapse
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Thanks for the updated version.
Urg, but I just finished downloading the original release
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Does this fix also apply to the LineageOS 13.x Rom? I need the Front facing camera working, and that works under Marshmellow and not Nougat.
Just wanted to thank you for your hard work and dedication on this ROM project and wish you good luck with the camera as well.
Not that I find the camera on the R1 HD all that useful as it takes pretty lame photos, but the lack of camera is basically the only thing keeping me from ditching Blu software altogether.
I really hope you manage to get a 100% operational LineageOS for the R1 HD.
Yesterday I called Amazon and complained about the software that collected our personal information and data and submitted it to Blu headquarters in China. They said that I could return the phone for a full refund so at this point I am seriously contemplating doing that. The only problem is that I don't have a backup phone.
The lack of resources from MTK based processors is such a deal breaker. I was not aware it would be so difficult to get development going for it when I bought my phone last year.
Now I'm contemplating getting an used phone with better development support after I return my R1 HD.
I really wanted to wait until OnePlus released their new device with a better display and hopefully a near bezel less display and at least IP67 water resistance. That's the reason why I didn't go for the OP5. The upside-down screen was also another one.
If you could get the camera working in LOS than I'd hold on to my R1 HD for a a while longer. But I'm not keeping my hopes up... Just being realistic. Haha!
Thanks again!
Thanks for your support!
As of now, I've been studying the leaked MTK camera sources for other devices and using IDA to see what extra symbols and logic the stock libcameraservice.so and libcamera_client.so has. It appears that replacing these two libs was the key to fixing camera in cm-13 ports.
Thank you!
Oh, I didn't know camera support was fixed for CM 13 on the R1 HD. Maybe I didn't see it here. But I'd much rather have a non Blu version of Android with all security patches even if it's just on marshmallow.
Three days ago I just realized that Blu had a frigging app collecting my personal data and sending it back to China.
It had sent over 5.9MB of data since July 21st. I think it's a lot of data for text only transmissions.
Anyhow, I've been seeing people using Footej on other ROMs in which they could not get the camera working with stock camera app. Is that what you mean by getting the camera to work?
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Dang! That's old! I guess devs should be more organized in doing a walk through with links to the files and recoveries needed to flash their awesome work.
Here's mine that I've just uploaded to zippy. I think it's the latest available and should be compatible with all ROMs.
Please report back with your findings and opinions on the ROM.
Please try to use both SIM cards to see if they work okay.
http://www8.zippyshare.com/d/p4HMiDRq/41954/R1_Port_3.1-TWRP.img
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Which version of the ROM is installed on it now? Modified or stock? Which recovery is on the phone? Stock or TWRP?
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
frosted.efizzle said:
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
Click to expand...
Click to collapse
Did you download and flash the image I've just shared above?
AndroidBR said:
Did you download and flash the image I've just shared above?
Click to expand...
Click to collapse
Same error
With they recovery You provided above
Thanks for your support!