Database Users

How do i flash back to a previous modem?

hey guys, so i have a retgb stock rom for lollipop, how would i go about just flashing the modem from that rom. I want to do this to test a theory i have about the battery drain on marshmallow, to see if its caused by the new modem, any help would be appreciated...

certainly not caused by the modem. Did you clean flash? What did you do to upgrade? etc? have you disabled wifi/bluetooth scanning in the extended location settings, deleted play services data yet?

Benjamin_L said:
certainly not caused by the modem. Did you clean flash? What did you do to upgrade? etc? have you disabled wifi/bluetooth scanning in the extended location settings, deleted play services data yet?
Click to expand...
Click to collapse
updated from a stock moto x play single sim, retgb to marshmellow via normal ota, had no root or bootloader unlocked. After the ota i installed twrp and rooted, wiped cache and data, did a factory reset. Then did everything you said above. Then tried with squid kernel, still have massive battery drain about 1 hour sot and barely lasts me 1 day. So yea... i thought it was worth a shot just trying my idea about the modem...

Tvman1231 said:
updated from a stock moto x play single sim, retgb to marshmellow via normal ota, had no root or bootloader unlocked. After the ota i installed twrp and rooted, wiped cache and data, did a factory reset. Then did everything you said above. Then tried with squid kernel, still have massive battery drain about 1 hour sot and barely lasts me 1 day. So yea... i thought it was worth a shot just trying my idea about the modem...
Click to expand...
Click to collapse
Really strange. Any special apps you use? Whats the app on top of your battery stats?

Benjamin_L said:
Really strange. Any special apps you use? Whats the app on top of your battery stats?
Click to expand...
Click to collapse
Mobile standby and phone idle, i have xposed and greenify installed, no speacial apps installed if you dont include kernel adiutor. Im gonna try going back to 5.1.1 stock and try a 6.0 stock rom via twrp, il post the results later.

Frequency stats probably show deep sleep as unused state?

Benjamin_L said:
Frequency stats probably show deep sleep as unused state?
Click to expand...
Click to collapse
no, deep sleep is being used like 92% of the time

So basically everything is working fine. In some other thread I read xposed seriously cripples battery life. I'm not using it so I can't tell

Benjamin_L said:
So basically everything is working fine. In some other thread I read xposed seriously cripples battery life. I'm not using it so I can't tell
Click to expand...
Click to collapse
well im currently going back to stock 5.1.1 for now, im gonna try my therory, then i try with and without xposed, see if it makes a difference

@Benjamin_L well i can safely say that xposed makes no differece that i can see to the battery life so far. After flashing the old stock (5.0, including the modem, through fastboot) then going back to 6.0 by flashing the stock rom by GtrCraft via twrp my battery life seems to have improved quite a bit. So maybe it is the modem after all? Also why did you say it cant be the modem in the first post? just curious...

Tvman1231 said:
@Benjamin_L well i can safely say that xposed makes no differece that i can see to the battery life so far. After flashing the old stock (5.0, including the modem, through fastboot) then going back to 6.0 by flashing the stock rom by GtrCraft via twrp my battery life seems to have improved quite a bit. So maybe it is the modem after all? Also why did you say it cant be the modem in the first post? just curious...
Click to expand...
Click to collapse
I ran both modems on 5.1.1 and 6.0 on several roms and stock firmwares and there was no difference, except for rom related things. And I never heard modem influences battery life dramtically if at all. On my old n4 i flashed several basebands and never noticed any difference in battery consumption at all.

Benjamin_L said:
I ran both modems on 5.1.1 and 6.0 on several roms and stock firmwares and there was no difference, except for rom related things. And I never heard modem influences battery life dramtically if at all. On my old n4 i flashed several basebands and never noticed any difference in battery consumption at all.
Click to expand...
Click to collapse
well, my phones now getting around 4hrs sot so im happy. XD

Downgrade to Marshmallow to avoid bootloop?

My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel

No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!

Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app

rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..

rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk

Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.

Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?

I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app

CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.

I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.

jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!

Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.

Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app

Bad news, and there isnt official answer from Google

I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it

seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.

jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse

CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?

Updating to latest security update - 6.0.1

Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow.
However, my security patch is from April 2016.
I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Sent from my Nexus 6P using xda premium

Lior84 said:
Hi,
My Nexus 6P is on android 6.0.1 and after reading all the problems with Nougat, I would better stay on marshmallow. However, my security patch is from April 2016. I am rooted with stock 6.0.1 MHC19Q.
Would like to know if I can update only the security update and if so, how to do this ?
Click to expand...
Click to collapse
I respect your decision to stay with MM, but I think it is misguided. There are many improvements that come with installing N, including the security updates. Security updates are part of the OS update and are not available separately. If you want the benefits of the latest security updates, you have to install 7.1.2.

Right now I'm on latest stock rooted with franco kernel and there are no issues. Except there's no xposed support.
But updating to nougat comes with no issues, so u should try, make a backup and flash.

I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium

Lior84 said:
I'm afraid to update because of brick possibility. From what I read, many users that updated, had a brick.
Sent from my Nexus 6P using xda premium
Click to expand...
Click to collapse
Nah, don't be afraid, I'm flashing everything with twrp, factory images too. No issues.

If by brick issue you are talking about the boot loop of death that's a hardware issue and it happens while you are on Marshmallow, Nougat or a custom Rom. If you are talking about something else as long as your bootloader is unlocked and OEM Unlock is enabled in developer options you should be able to recover in the unlikely event of a flash going bad. Whether to flash or not is a tradeoff. You get the latest features and security updates on Nougat but you can't use Xposed (if that's actually important to you) and you will almost certainly get worse battery life on the latest versions of Nougat than you are getting on Marshmallow. Google has goosed the stock kernel settings lately resulting in worse battery life and the operating system and screen using more battery than previously. The only way to avoid that and stay up to date is to flash a custom kernel or flash a custom Rom.

I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Sent from my Nexus 6P using xda premium

Lior84 said:
I have bootloader unlocked from the first day of the phone. I really like this model (except for the camera that responds slower than the nexus 5 one) and would like to use it at least one more year. Really worry about the hard brick and because of its, staying till now on stock 6.0.1.
With N5, I flashed many roms, but in this one, I stayed one year on a single rom that came on it.
Click to expand...
Click to collapse
The bootloop issue has nothing to do with the os update. It is because of dodgy hardware. It can happen from a damaged and degraded battery. Updating to nougat doesn't cause the issue.

Stick with PureNexus or update to Oreo?

I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?

Etheralrealm said:
I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Click to expand...
Click to collapse
Unless you're worried about the security updates, just stay on PN. PN for Oreo should be out soon as well.

That makes a lot of sense, thanks.

Etheralrealm said:
I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Click to expand...
Click to collapse
I was on PN since I got my 6P and updated to Oreo as soon as it came out. I don't regret the decision at all. Battery life is as good or better than PN (I routinely end the day with 4+ hours of SOT and 35-40% left. Your experience may vary depending on usage), performance is wonderful, and I haven't found any major bugs yet. All of my favorite mods work (EX kernel, Pixel mod, Camera NX, WakeBlock, and a few others I'm forgetting).
The only downside is some modifications require a bit more work. For example, to resize the navigation bar and add dynamic coloring I had to extract, modify, and push framework-res.apk instead of having those options built right into the settings menu. There's no custom quick settings tiles and I can't change the number of rows/columns, but that isn't a big deal and I've learned to live without it for now.
As stated above PN based on Oreo should be out within the next month or two. Beans posted an announcement on G+ yesterday explaining that he had a family emergency that slowed down development on PN O, but he is actively working on it as much as he can.

Etheralrealm said:
I'm currently running the latest version of PureNexus and debating installing Android Oreo. Are there any huge downsides? Is it buggy, slow, etc? In other words, is it daily driver ready for someone who uses their phone all day for music, video, games, EVERYTHING and still wants to tweak the os to their needs.
?
Click to expand...
Click to collapse
I went from PN to 8.1. Honestly, stick with PN. I used it for a couple days and I am downgrading right now. My battery life was significantly worse (on 7.1.2 I ended the day at ~40-50% battery. On 8.1 I was at ~20-30). I didn't notice anything great about Oreo and found myself missing PN.

Poebat said:
I went from PN to 8.1. Honestly, stick with PN. I used it for a couple days and I am downgrading right now. My battery life was significantly worse (on 7.1.2 I ended the day at ~40-50% battery. On 8.1 I was at ~20-30). I didn't notice anything great about Oreo and found myself missing PN.
Click to expand...
Click to collapse
Maybe your battery is just getting tired I'm finding the opposite Oreo 8.1 giving me excellent results.

Exodusche said:
Maybe your battery is just getting tired I'm finding the opposite Oreo 8.1 giving me excellent results.
Click to expand...
Click to collapse
Might be Xposed then. My sot dropped by 1.5hrs.

Poebat said:
Might be Xposed then. My sot dropped by 1.5hrs.
Click to expand...
Click to collapse
I'm gonna go back and try Pure Nexus again now that I have a new battery I could use extra 1.5 hours.

Exodusche said:
I'm gonna go back and try Pure Nexus again now that I have a new battery I could use extra 1.5 hours.
Click to expand...
Click to collapse
Good luck.

Not sure aware of this or not, but beans posted in the PN thread he's working on Oreo for the angler. So you'll soon have the best of both.

Poebat said:
I went from PN to 8.1. Honestly, stick with PN. I used it for a couple days and I am downgrading right now. My battery life was significantly worse (on 7.1.2 I ended the day at ~40-50% battery. On 8.1 I was at ~20-30). I didn't notice anything great about Oreo and found myself missing PN.
Click to expand...
Click to collapse
Hey man, how did your downgrading go? I had the intention of downgrading today but somewhere messed up and now my phone is in a bootloop. What steps did you take?
Thanks!

Ritser said:
Hey man, how did your downgrading go? I had the intention of downgrading today but somewhere messed up and now my phone is in a bootloop. What steps did you take?
Thanks!
Click to expand...
Click to collapse
I had that issue too. Spent waaaayyy to long trying to figure it out. I think 8.1 has a different encryption method. You need to wipe the phone completely and then do a nandroid restore (or flash PN)

Poebat said:
I had that issue too. Spent waaaayyy to long trying to figure it out. I think 8.1 has a different encryption method. You need to wipe the phone completely and then do a nandroid restore (or flash PN)
Click to expand...
Click to collapse
Don't mean to sound like a complete noob, but how did you go on about wiping the phone completely? I've now tried so many things, reflashing TWRP, reinstalling stock firmwares, using Wug's Nexus Rooting kit, ... I can acces fastboot, what do I need to do to be able to reinstall TWRP? Because when I try it right now, I can't acces it. It goes back into the boot loop.
Cheers

Ritser said:
Don't mean to sound like a complete noob, but how did you go on about wiping the phone completely? I've now tried so many things, reflashing TWRP, reinstalling stock firmwares, using Wug's Nexus Rooting kit, ... I can acces fastboot, what do I need to do to be able to reinstall TWRP? Because when I try it right now, I can't acces it. It goes back into the boot loop.
Cheers
Click to expand...
Click to collapse
In TWRP, format /Data and the internal storage. I also formatted /system just to be safe.

How to downgrade the software version?

Hi,
I've read a lot of threads about upgrading software on this phone but I'm not really sure how to downgrade it. I would want to play around with different versions of android to find which one suits me the best. I will get A2017G version. Can you help me?
Thank you

Pretty sure if you're on Nougat you can flash MM B11 to go back. That's the latest MM. You lose Daydream on MM if that's of any concern.
I use Nougat, won't be using MM.

RobboW said:
Pretty sure if you're on Nougat you can flash MM B11 to go back. That's the latest MM. You lose Daydream on MM if that's of any concern.
I use Nougat, won't be using MM.
Click to expand...
Click to collapse
And which version of Nougat do you use? I'm worried about battery life.

Evzzza said:
And which version of Nougat do you use? I'm worried about battery life.
Click to expand...
Click to collapse
Battery life isn't really something consistent among different phones. Sometimes your installation will run like utter crap, and the way to fix it would be by installing a custom ROM (you can get around 7h SOT with a well set up system; like an EAS kernel, Swift Black, and LOS-based stuff like RR) and either stay on custom or go back to stock. Also you can use MiFlash to reinstall the stock system without actually needing to go custom then return.
I had this little thing where I went custom just to try, I used it for 3 months, and then I decided to go back to B10 Marshmallow. After using MiFlash to get B10 working, the phone would randomly reboot roughly once every two hours. I updated to latest Nougat, then even downgraded, but there was no way to fix that. The only thing that helped me was to install custom again then go back to stock. MiFlash might also do the trick though

Evzzza said:
And which version of Nougat do you use? I'm worried about battery life.
Click to expand...
Click to collapse
Was on BO4 and updated to B08, saw no real difference between.
I had some funny stuff with dual SIMs being unreliable then realised I couldn't send a multimedia message. The update messed up my apn settings a tiny bit but I fixed that and been fine since.