Hi!
Some days ago I unlocked my 6P, installed TWRP and flashed Chroma ROM. Now I wanted to download the factory images and back them up (just to be sure). My build number is MMB29U. According to this page, it's the build number of a Nexus player and not a 6P... Is that a problem? Which factory image should I download?
I have no problems with Chroma so far...
Thank you!
muEcke* said:
Hi!
Some days ago I unlocked my 6P, installed TWRP and flashed Chroma ROM. Now I wanted to download the factory images and back them up (just to be sure). My build number is MMB29U. According to this page, it's the build number of a Nexus player and not a 6P... Is that a problem? Which factory image should I download?
I have no problems with Chroma so far...
Thank you!
Click to expand...
Click to collapse
Totally normal. Chroma is based on the latest AOSP branch. For each OTA, the AOSP code is more up to date but is still compatible with your 6P. OTAs and latest AOSP share the same base at time of release. MMB29Q is the February firmware for your 6P.
Sent from my Nexus 5X using Tapatalk
So everything is fine, thank you!!
I noticed mine is MMB29U too. I just wanted to check what version I had prior to updating my baseband through rapid fire. Didn't see it on the list either. My phone had system errors after flashing though, so I'm still on MMB29U.
Related
Hey everyone. I recently started messing with ROMs on my Oneplus Two, and for some reason I keep getting error 7 after trying to install ROMs.
I'm doing everything the exact same for every ROM I try, but it seems a third of the time I get error 7. I was wondering if there's something specific with my phone that could be causing this?
I've asked my friend to try out some of the same ROMs on his Nexus 6 and they seem to work fine.
One ROM in particular I'm having this problem with is Resurrection Remix.
I'm fairly sure I'm installing everything correctly, so any feedback on this issue would be great.
Thanks!
You need to use hybrid recovery. Look for garak twrp hybrid 3.0.2.0 and flash within twrp. Bootloader is set on lollipop and marshmallow ROM conflicting.
Change the Twrp version or go for Grarak's Twrp that will be fine
Akash1998 said:
Change the Twrp version or go for Grarak's Twrp that will be fine
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904 is this a working recovery that will flash all ROMs to the oneplus 2? Or is Grarak's the only solution as of now? Thanks
I'm in Garak version on TWRP (Orange one) and currently on CM13. Now I'm trying to clean flash AOSPA but getting Error 7, Any way to fix this?
Edit : Tried flashing Official firmware OOS 3.0.2 and then flash again AOSPA but still same error.
Edit 2 : Flashed TWRP 3.0.2.0 and all is fine now.
FIXED!
Alright cool I ended up installing the hybrid twrp and it works great now! Thanks guys.
Hey guys, I've been using CM13 builds on my Nexus 6p for last few months. Generally, i flash new builds after 3/4 days from the last one. Everything's works fine, no big issues; but recently from last months build which ever update i flash on the device, the WiFi seems not working. It shows, it's on - Searching for Networks; but not able to connect or even find any network at all. And i tried to flash back to the older builds of CM13, the WiFi works fine on those builds quite fine. Beside this, I've tried Paranoid Android ROM on this device, WiFi works fine on that rom. So, have any of you faced such problem on CM13? And, please can anyone help me out on this matter?... Thanks in advance...
rudra_666 said:
Hey guys, I've been using CM13 builds on my Nexus 6p for last few months. Generally, i flash new builds after 3/4 days from the last one. Everything's works fine, no big issues; but recently from last months build which ever update i flash on the device, the WiFi seems not working. It shows, it's on - Searching for Networks; but not able to connect or even find any network at all. And i tried to flash back to the older builds of CM13, the WiFi works fine on those builds quite fine. Beside this, I've tried Paranoid Android ROM on this device, WiFi works fine on that rom. So, have any of you faced such problem on CM13? And, please can anyone help me out on this matter?... Thanks in advance...
Click to expand...
Click to collapse
I've been successively flashing the nightlies from 07/24 until today and have had no issues with Wi-Fi. Sounds like yoh crossed over drom June to July build. Flash the July vendor image then re-flash latest cm and you should be good to go. If you use a custom kernel also make sure you are using the latest version made for this month.
blitzkriegger said:
I've been successively flashing the nightlies from 07/24 until today and have had no issues with Wi-Fi. Sounds like yoh crossed over drom June to July build. Flash the July vendor image then re-flash latest cm and you should be good to go. If you use a custom kernel also make sure you are using the latest version made for this month.
Click to expand...
Click to collapse
Thanks a lot, brother. I've just flashed the latest vendor image, and it's working smoothly...
So I have my nexus 6p for a few days now.. it's so good to have my nexus toy again. I use to have a nexus 5 but it died and lived with a samsung s4 for a while.
Anyway, my nexus 6p, I wanted to flash CM13 on it as 7.1 is great, but some root-apps don't work yet and CM13 has some good stuff I want.
After flashing it, it got stuck on the google logo and after googling and searching the forums, it seems like I need 6to flash the latest vendor.img... Still stuck..
So now I'm reading that I don't need the latest vendor.img, but the vendor.img coresponding with the ROM you wish to install..... which is where I'm stuck
How do I figure out which vendor.img I need to flash the latest CM13 on my nexus 6p?
S.Phrenic said:
So I have my nexus 6p for a few days now.. it's so good to have my nexus toy again. I use to have a nexus 5 but it died and lived with a samsung s4 for a while.
Anyway, my nexus 6p, I wanted to flash CM13 on it as 7.1 is great, but some root-apps don't work yet and CM13 has some good stuff I want.
After flashing it, it got stuck on the google logo and after googling and searching the forums, it seems like I need 6to flash the latest vendor.img... Still stuck..
So now I'm reading that I don't need the latest vendor.img, but the vendor.img coresponding with the ROM you wish to install..... which is where I'm stuck
How do I figure out which vendor.img I need to flash the latest CM13 on my nexus 6p?
Click to expand...
Click to collapse
When you go to settings, about phone, what does it say under security patch or build number? That should help you with finding what vendor you need. Or if you go to the thread where you downloaded cm13 sometimes they mention what vendor you should flash. Which version are you on? If latest stable release I think it's the August vendor img you need. The latest nightly may be on October's.
For CM13 you would need to flash the 6.0.1 MTC20L vendor.img
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
I would also ask in the SPRINT forum .
JJEgan said:
I would also ask in the SPRINT forum .
Click to expand...
Click to collapse
Good idea, thanks.
jdd1960 said:
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
Click to expand...
Click to collapse
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
ShaDisNX255 said:
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
Click to expand...
Click to collapse
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
jdd1960 said:
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
Click to expand...
Click to collapse
You're welcome. Happy flashing!
Hi,
My axon 7 (A2017G) is currently running LOS 14.1-20170203-UNOFFICIAL. I was reading up on updating it and gathered that I need to flash an experimental build and then update to the latest nightly to get the latest official version, but I cant seem to find the latest experimental build for the axon 7. Where can I find this?
King Norman said:
Hi,
My axon 7 (A2017G) is currently running LOS 14.1-20170203-UNOFFICIAL. I was reading up on updating it and gathered that I need to flash an experimental build and then update to the latest nightly to get the latest official version, but I cant seem to find the latest experimental build for the axon 7. Where can I find this?
Click to expand...
Click to collapse
I'm guessing it's on the unofficial LOS thread? I remember doing that back then. The experimental build has an overlay all over the screen.
I don't know if it's actually needed anyways but if you don't find it I guess you can go back to stock and install the latest nightly manually
Choose an username... said:
I'm guessing it's on the unofficial LOS thread? I remember doing that back then. The experimental build has an overlay all over the screen.
I don't know if it's actually needed anyways but if you don't find it I guess you can go back to stock and install the latest nightly manually
Click to expand...
Click to collapse
Would going stock and then back to LOS be easier do you think?
King Norman said:
Would going stock and then back to LOS be easier do you think?
Click to expand...
Click to collapse
Lol if you can't find the experimental build I assure you it would be safer...
Use EDL Tool by djkuz, and obviously use an A2017G package (B09 for example). After that flash TWRP and install Lineage with the univ. bootloader, A2017G modem and Magisk, plus gapps i guess