Database Info

[Q] Noob - Help on Sense 5 by Turge

Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!

+1 i have same questions

You might get more responses if this was in the question thread. Mod please move this to the correct area.
Sent from my HTC One XL using xda premium

watswidme said:
Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!
Click to expand...
Click to collapse
1. The firmware update will update the hboot, radio, and some WiFi and media modules.
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
2b. A nandroid backup doesn't backup the partition that is updated by a firmware package. It only backs up the OS/data/boot partitions, so restoring a backup won't change your firmware, use the RUU as suggested above if you need to revert.
3. Restoring your backup will return you to the Sense 4 ROM. Like I mentioned above though it will not change your firmware.
You are s-off so the chance of bricking while running an RUU is minimal. There is always a small chance of bricking no matter what you're doing, whether it be flashing a ROM/kernel, changing hboot (higher risk), flashing a radio, running an RUU. With your current setup, you have no greater risk than anyone else though.
PS. Questions go in the q&a section (for future reference).
Sent from my Evita

I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251

timmaaa said:
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
Click to expand...
Click to collapse
This^ I was gonna ask about it in Q&A thank goodness I read this thread first. Thank you!
Sent from my HTC One X using Tapatalk 4

Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.

watswidme said:
Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.
Click to expand...
Click to collapse
I can't see any reason why reverting to Sense 4 wouldn't be ok on the newer firmware.
Sent from my Evita

Newbie Question.
rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
Hey bro
I'm from Venezuela and I'm having the exact same problem as you guys have.
I readed your post and downloaded Beastmode 3.5 and flash it, but i got caught in a bootloop.
I'm using the VIPER 4.2.2 Rom.
Since this is not a solution for me, i was wondering which Rom are you using exactly?

Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita

rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
timmaaa said:
Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you my friend!
I downloaded Turge's ROM and install it, and actually didnt have to flash the New kernel; i used the one in the Package and it Worked! i almost sold my phone because i couldnt find a ROm taht works but, so far, its been passed one day only and i havent had any signal drop, nor battery fast draining!
Sorry for my english BTW.
Thank you once again!
PS: If u find a way to fix VIPER ROM let me know, cause i've read a lot and cant find a way to fix it, but im to shy to ask in a new post hahahahahhahahahahahahaha.
Let me know if you need my phone specs. (as bootloader version, software version etc.)

The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita

timmaaa said:
The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, i'm already S-OFF.
Actually, all this problems came out when i was 1.14 FW, but when i checked for the first time this post, i decided to change the FW and now i'm @ 2.15 FW, S-OFF and CID-11111111.
I haven't checked what is gonna happen if i install VIPER ROM, but in the meanwhile, i'm gonna try this ROM which runs smooth.

Quick question about going from 4.1 to 4.4 (Been gone for a while)

So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol

aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck

dandydon414 said:
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
Click to expand...
Click to collapse
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar

aholeinthewor1d said:
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
Click to expand...
Click to collapse
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.

dandydon414 said:
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
Click to expand...
Click to collapse
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you

aholeinthewor1d said:
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
Click to expand...
Click to collapse
that recovery is fine. i've only used cwm and twrp.. had some problems with philz recovery so I ditched it. basically they're all the same. twrp lets you name your back where as cwm just uses some default name which of course you can change with a file manager. twrp also wipes all 3 (system, cache and dalvik) with one swipe where as cwm requires 3 separate operations. I really haven't done much in recovery other than wiping and flashing. I'm actually on the latest twrp and have had no problems flashing kk roms. keep in mind that you can't backup in cwm and restore it using twrp and vice versa. it's really more a personal preference as far as I'm concerned.

[q] Upgrading from Custom 4.4.4 Rom to Custom 5.0 Rom

Hello folks, how are you? I'm sorry if this is a duplicate post, but I've been searching for a clear answer to this and haven't found one.
I'm currently on a Nexus 5 running a custom 4.4.4 rom based on Purity. While I've no problems with this rom, I'm kinda itching to try 5.0. However, I'm not entirely clear on the upgrade path. I've read that to go to 5, I'd have to revert to stock, upgrade to 5.0 stock, THEN install a custom rom after that, but that sounds like quite a few steps.
Now if that's what I have to do, that's fine, but I'm curious if I can simply flash a new 5.0 rom after doing a wipe like I would with any other rom, or do I have do do anything different like flashing radios or revert to stock or anything along those lines.
Therefore, if some could just simply lay out what I best course of action is, that would be wonderful. Thank you for your time.

Hopefully I've covered all your options
http://forum.xda-developers.com/showthread.php?t=2947144
It doesn't cover wipes but do take the usual titanium backup and be prepared to.wipe.

Ahhh, so it looks like:
Method 5 (You are rooted 4.4.x with custom recovery)
1. Flash from recovery, an existing packages ROM.zip
2. Flash from recovery, a flashable custom boot.img (@Chainfire for basic root, @sykopompos for full permissive mode)
3. Flash from recovery, SuperSU (Please note BETA 2.27+ May mean you do not need a modified boot.img)
You can get the boot.img's and SuperSU from here: [ROM] N5 Lollipop + Stock IMG Mirrors & More! (by @vomer)
You can get a ROM.zip from here: [ROM] [STOCK] Android 5.0 LRX21O - Stock/Flashable (11/12/14) )by @bigxie
Click to expand...
Click to collapse
Is probably the best way for me to go! Awesome, thank you!!!

Just to ease your mind a bit, I was just like you.
I too have came from Purity 4.4.4 , I upgraded to cataclysm because I too was itching for the new Lollipop update.
The way I approached this flash is like I've always had, I moved the zip into the storage and using the latest TWRP recovery I just flashed the rom and everything worked buttery smooth.
Hope things go well for you.

MrFishiz said:
Just to ease your mind a bit, I was just like you.
I too have came from Purity 4.4.4 , I upgraded to cataclysm because I too was itching for the new Lollipop update.
The way I approached this flash is like I've always had, I moved the zip into the storage and using the latest TWRP recovery I just flashed the rom and everything worked buttery smooth.
Hope things go well for you.
Click to expand...
Click to collapse
Ohhh, do you mean this Cataclysm?
http://forum.xda-developers.com/google-nexus-5/orig-development/rom-cataclysm-nexus-5-t2518660

Yea that's the one, it's a very nice ROM, very customizable and very stable.

MrFishiz said:
Yea that's the one, it's a very nice ROM, very customizable and very stable.
Click to expand...
Click to collapse
Sweet, and you didn't have to fudge with radios or anything of the sort?

Brian Rubin said:
Sweet, and you didn't have to fudge with radios or anything of the sort?
Click to expand...
Click to collapse
Well, the author explains that he included gapps and root into the build itself, but he also said that the rom does not update the radio. I didn't get any signal problems if that's what you mean but when you think about it I don't think that any rom includes a radio in it aha that's always a separate update.
If you do want to update your radio to the latest version, visit this link:
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003

MrFishiz said:
Yea that's the one, it's a very nice ROM, very customizable and very stable.
Click to expand...
Click to collapse
Right on all counts. I did what'cha said, wiped (a few times, to be sure), flashed, and waited during the long reboot. Now it's working swimmingly, and I LOVE IT. Very fast, very stable, now I just gotta get used to some of Lollipop's idiosyncrasies. Thanks folks!

Problems with Nandroid backup

Hello!
I recently had my OnePlus One on RMA because of a OTA-update brick.
Now when I got it back from OnePlus, my device was now suddenly running OxygenOS based on Android 5.0. This is not what I want! Fortunately, I have done Nandroid backups in the past of the Cyanogen Android 4.4.4 which I wish and need to run. So I went ahead and unlocked the bootloader of my phone, rooted it and installed TWRP, which is the same as I used to take said backups. Then I took a backup of OxygenOS 5.0 just to be safe.
Now, the issue is as soon as I restore any of my old backups (I tested that these are working in the past.), the phone goes into a bootloop and refuses to start until I flash back the OxygenOS backup.
What in the world is going on here?

After reading around some, I am wondering if this is because the "modem" or "firmware" is different now from what it was before when the backups were working?
See Step 9 here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Is this my problem? Could I try it out safely by first restoring my backup and then applying one of those (Which? I am confused why there are two downloads for the same task.)?
Please, I need a little help here as I do not want to hard brick my phone.

NodCom said:
After reading around some, I am wondering if this is because the "modem" or "firmware" is different now from what it was before when the backups were working?
See Step 9 here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Is this my problem? Could I try it out safely by first restoring my backup and then applying one of those (Which? I am confused why there are two downloads for the same task.)?
Please, I need a little help here as I do not want to hard brick my phone.
Click to expand...
Click to collapse
Yes it's because the firmware is incompatible. You can search for the right one based on which version of CM11 you had before in your backup. Oxygen modem is compatible with 5.1.1 CM ROMs in case you want to upgrade later
http://boeffla.df-kunde.de/bacon/modems/
Sent from my A0001 using Tapatalk

Renosh said:
Yes it's because the firmware is incompatible. You can search for the right one based on which version of CM11 you had before in your backup. Oxygen modem is compatible with 5.1.1 CM ROMs in case you want to upgrade later
http://boeffla.df-kunde.de/bacon/modems/
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply!
How can I tell more precisely what version I had before? All I really know is that it was CM11 and Android 4.4.4. Do I need to be more specific in my knowledge than that?
Sorry, but what do you mean by that last part? If I flash the CM11 modem, would not that remove the Oxygen modem?

Hello again,
After doing some research I decided on the XNPH44S-modem as it seems to be the newest modem for CM11.
This did however not help, the phone still bootloops after flashing the modem. Is the modem separate from the firmware? Do I need to find a firmware as well?
Help is highly appreciated.
Edit! I solved it! With a combination of http://forum.xda-developers.com/oneplus-one/general/cm11-cm12-firmware-repository-t3019881/page2 and http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 as guidelines I made the phone boot successfully! The snag is that "fastboot flash LOGO logo.bin" failed because it "remote: partition table doesn't exist", so "half" the boot animation seems to be missing. Any fix?
I am a little confused though, after booting up I had the OTA updated suggest update XNP44HS, which is the exact same name as the modem flash I did. What gives? Is it safe to download this update?
OTAs have me slightly worried. Last time I went through all the CM11 updates and then jumped into CM12, found it not to my liking and tried to go back, which I managed to, after which I tried to update to the latest CM11 using OTA; and the first security update here gave me a hardbricked phone that time. Any suggestions or insight into this from someone with good knowledge?

NodCom said:
Hello again,
After doing some research I decided on the XNPH44S-modem as it seems to be the newest modem for CM11.
This did however not help, the phone still bootloops after flashing the modem. Is the modem separate from the firmware? Do I need to find a firmware as well?
Help is highly appreciated.
Click to expand...
Click to collapse
You'll have to test out the older modems till you find out which is the right one. Last I checked 05Q was the latest CM11. Try that one, otherwise download and test 33R, 30O etc till you find one that works. It would have been really easy if you could remember what version your backup was and make sure you're using TWRP 2.8.6.0. Download Oxygen OS modem too if you want to go back to it or use newer ROMs
Sent from my A0001 using Tapatalk

Renosh said:
You'll have to test out the older modems till you find out which is the right one. Last I checked 05Q was the latest CM11. Try that one, otherwise download and test 33R, 30O etc till you find one that works. It would have been really easy if you could remember what version your backup was and make sure you're using TWRP 2.8.6.0. Download Oxygen OS modem too if you want to go back to it or use newer ROMs
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I updated my message within a minute of you posting yours, so you might have missed the edit.
SIM and calling works with the XNP44HS modem which I flashed. Still, the OTA updater claims to have it as an awaiting update, but I am not sure if I dare downloading it or not? Also, why is that specific version of TWRP important? I can see that my current version is 2.8.5.1.

Update Build W/O a Computer

Ok, let me start by saying that I'm fully capable of updating my phone with a computer, I'm just hoping there is a better way. So far every time I've downloaded a new firmware, update the flash-all.bat and run it, something will fail towards the end of the update and the only way I've been able to successfully update is by using one of those tool kits (forget which one, it's on my computer). I'm not that concerned about all of that with this thread. I'm wondering if there is a way to do it without a PC.
I'm on NMF26O (root, ElementalX, etc) and tried flashing Pure Nexus over the weekend. Since it's based on NMF26V, I kept receiving an error on boot about updating my vendor.img. So I downloaded that firmware, extracted it, and flashed the vendor.img in TWRP. That led to a plethora of other issues that I couldn't resolve by flashing the boot.img, reflashing the rom, ect. Several hours later I ended up flashing the boot.img and vendor.img for NMF26O, restoring my backup, re-installing Elemental, and rooting again.
Since these updates will be coming out every month, and roms will always be based on the latest update, I feel like I'll be pulling out the computer every month, downloading the updates, modifying the flash-all.bat, and running it through the tool, just to be able to update my rom. The first time I forget to update flash-all.bat, I'll lose the 60+ GB's I keep in internal storage. There has to be an easier way. TWRP is capable of flashing images. Has anyone been able to update without using a computer? I don't care if my radio is out dated, or something is mismatched as long as my phone works as intended.
Sent from my Pixel using Tapatalk

Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though

aholeinthewor1d said:
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
Click to expand...
Click to collapse
I'm on NMF26O. What's the difference between it and NMF26U and why would the vendor image from NMF26V work with NMF26U but not NMF26O?
Seems like all you would need is the /system from the rom, the vendor image, and maybe the boot image (or a custom kernel). I think I'm missing something here.
Sent from my Pixel using Tapatalk

If you install PN its based on NMF26V. So unless you are already on that then you would need to flash the ROM, reboot back to recovery, then flash the NMF26V vendor image.

I'll play devil's advocate here... Yeah there is an easier way, use your Pixel stock and take OTA's. Enjoy a phone that always works, with or without a laptop!
I understand my audience and realize this isn't a popular mantra here but I felt exactly like you did with my 6p and vendor images. I got to the point where I sacrifice root now just for my own sanity. My phone works for me, not the other way around.

What I do is side load the full OTA ( which you can get from the same place you get the factory images ). I only use the fastboot boot version of TWRP so that my stock recovery stays in place. Then all you have to do is boot into the stock recovery, adb side load the OTA file and re root. Then you're fully up to date without worries of your data being wiped :laugh:!
( Although if you look in the flash fire thread from Chainfire, he's working on a version that will let rooted pixels flash otas like normal ones :fingers-crossed: )

I think you guys are missing the point. I have no desire to ever be stock, which rules out the possibility for an OTA in any form.
What I'm trying to figure out is exactly what is necessary to make a custom rom (based on the latest OTA), work if flashed over an older build, without first somehow applying the full OTA. Or is it impossible?
On just about every other phone I've owned, we could piecemeal the files needed for minor updates, along with a custom rom. The only time we'd have to flash a full update is for major updates ( 4 to 5 to 6, etc).
Sent from my Pixel using Tapatalk

Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Sent from my Pixel using Tapatalk

joshw0000 said:
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Click to expand...
Click to collapse
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU

aholeinthewor1d said:
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
Click to expand...
Click to collapse
I've done it several times tonight. Went from O to U to V, flashed Pure Nexus, screwed up the rom, restored to O, then O flashed back to U and V.
Just flash it like a rom in TWRP RC1. Make sure you flash TWRP again before rebooting if you want to keep it.
Sent from my Pixel using Tapatalk