Develop Bugs

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point

garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.

OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager

Older Recovery versions are available on "dougpiston.com" just follow the directions.

www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.

Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip

Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.

Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium

pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

HTC M8 weird booting issue

Hello team, I have a weird issue when booting my phone.
HTC M8 8Unlocked International version
This started after I installed Venom Rom 2.0.
It continuously made crash the systemui process so I thought something went wrong with the rom installation.
I reinstalled it, same thing.
I went back to Venom 1.8.0
Problem started:
When it boots I get the HTC white screen and then stays there forever. I thought it was stuck on the boot screen but if I press about 4 or 5 times the power button the screen refreshes and I can use the phone.
I have tested several things and noticed that after 2 minutes, when the HTC logo is there I can press the volume buttons and they actually work. Just the screen is not refreshing until I press several times the power button.
Here is what I have tried to fix this weird issue:
Did full clean with TWRP
I reinstalled Venom 1.7.1 same issue
Upgraded to 1.8.0 same issue
Installed insertcoin rom, same issue
Reinstalled TWRP (Advanced > Reflash Recovery) and went back to Venom rom, same issue
In TWRP I used the option Advanced > Restore Original Boot. Same issue
I did fix permissions. Same issue
At this moment I have no idea what else to try.
ADB and FastBoot are fully functional in my pc.
I noticed I cannot gain SU from ADB when the phone is on this state. As soon as I do adb reboot the phone returns in that state and once is connected back and I can see it using adb devices, the su command does nothing.
I want after fixing this thing to remove the red banner from the screen.
I would really appreciate any suggestions.

Have tried updating the firmware?
I had the long booting issue with custom Roms until I updated my firmware to 2.22.401.4
I think it's cause the latest updates of most the custom Roms run off that firmware and you might be running the older one.
You need to be S-off I think to flash firmware. And it might say you are on 2.22.401.4 in the phone settings but that might not be correct.

LinS123 said:
Have tried updating the firmware?
I had the long booting issue with custom Roms until I updated me firmware to 2.22.401.4
Though I had to get S-off to flash it.
Click to expand...
Click to collapse
Yeah I can't update it because I cannot get s-off since su is not working for me.
One last thing I just tried was installing an Odexed rom and the problem did not happen. This whole story started when using the stock rom, for no reason my phone started rebooting itself every 2 minutes. Then I installed venom and the problem went away.
I did find this odexed rom before to avoid the red banner which did the trick but the reboot problem came back. :crying:
So now I am just stuck trying to fix this with the custom rom

Well, you can try reverting to full stock and retry the entire root process from scratch.
The other way is to revert back to stock and wait for the new OTA to finally be pushed for the firmware update.
Try following this guide. It's written really well and should get you root access properly.
http://forum.xda-developers.com/showthread.php?p=53807690
Credits go to Vomer, the original writer of the guide; it's extremely well written and easy to follow.
EDIT: Posting from a phone is hard... Autocorrect is not always your friend.

LinS123 said:
Well, you can try reverting to full stock and retry the entire root process from scratch.
The other way is to revert back to stock and wait for the new OTA to finally be pushed for the firmware update.
Try following this guide. It's written really well and should get you root access properly.
http://forum.xda-developers.com/showthread.php?p=53807690
Credits go to the original writer of the guide, it's extremely well written and easy to follow.
Click to expand...
Click to collapse
I appreciate the response, I will try that and see what happens.

Just a heads up. Firewater is not guaranteed to work for S-off. It comes down to luck of the draw.
My M8 was an unlucky one so I had to find another way. I hope yours works with Firewater.

There is another tool called sunshine but it is $25, and it guarantees to S-Off any HTC One m8 variant, but I think I might just wait for the official firmware rather than spending $25.

Billchen0014 said:
There is another tool called sunshine but it is $25, and it guarantees to S-Off any HTC One m8 variant, but I think I might just wait for the official firmware rather than spending $25.
Click to expand...
Click to collapse
Thank you for this option as well. I did firewater and gave me the "you are unlucky" not-very-friendly banner LOL
I did it with Sunshine. (Yeah I paid the $25) Sometimes I do think paying the devs for good work is fine.
I can now remove the red banner
BTW. To close this thread. After flashing an Odexed rom the slowness went away, I went back to Venom 1.8.0 and it continued booting normally . Looks like there is kernel problem in my phone with certain roms.

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron

ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.

No need to relock the bootloader for an ota. People should stop spreading that info

Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!

ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.

You can be unlock and have OTA.
You just need a stock recovery.

HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.

Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.

jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron

ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates

jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.

ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..

vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.

Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.

jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

[Q] WiFi Not Working, PC Not Picking Up Via USB

So today I was looking at the ElementalX thread after I update to GPe 5.1 earlier in the week. I saw that a couple of people had the kernel working fine, so I decided I would flash it and see if it would work fine for me.
Of course, that was not the case. It got stuck in a boot loop, getting past the boot logo and to the "Optimising apps..." stage, every time. So I decided to flash the stock kernel back, but when I upgraded to 5.1, I didn't flash the new firmware, so I thought that this would be a good time to do that. After I did, I managed to get into Android just fine, however I had no WiFi. So after some restarts and clearing caches, etc, I decided to flash the firmware for 5.0.1. Same again. I found another GPe radio posted somewhere on XDA that was flashable in recovery, but same thing. I get a 4G signal fine and Bluetooth appears to be working.
Amongst all of this, now when I plug my phone in via USB neither my Macbook or Windows PC are picking it up...eurgh. I just don't understand why it is doing all of this when I'm sure it is now back to how it was before I started this morning? Would it just be easier to flash the 5.1 RUU to my phone now, or will I most likely just get the same problems?
Thanks in advance!

zedlor said:
So today I was looking at the ElementalX thread after I update to GPe 5.1 earlier in the week. I saw that a couple of people had the kernel working fine, so I decided I would flash it and see if it would work fine for me.
Of course, that was not the case. It got stuck in a boot loop, getting past the boot logo and to the "Optimising apps..." stage, every time. So I decided to flash the stock kernel back, but when I upgraded to 5.1, I didn't flash the new firmware, so I thought that this would be a good time to do that. After I did, I managed to get into Android just fine, however I had no WiFi. So after some restarts and clearing caches, etc, I decided to flash the firmware for 5.0.1. Same again. I found another GPe radio posted somewhere on XDA that was flashable in recovery, but same thing. I get a 4G signal fine and Bluetooth appears to be working.
Amongst all of this, now when I plug my phone in via USB neither my Macbook or Windows PC are picking it up...eurgh. I just don't understand why it is doing all of this when I'm sure it is now back to how it was before I started this morning? Would it just be easier to flash the 5.1 RUU to my phone now, or will I most likely just get the same problems?
Thanks in advance!
Click to expand...
Click to collapse
Yes, it would be easier. RUUs are the safest way as well. You'll lose all of your data though, so backup anything that is important to you (photos, apks, zips, etc.)

xunholyx said:
Yes, it would be easier. RUUs are the safest way as well. You'll lose all of your data though, so backup anything that is important to you (photos, apks, zips, etc.)
Click to expand...
Click to collapse
Yeah, I ended up doing this and it's working now. Bit annoyed though because I kinda forgot to move things from my /sdcard/ folder, thinking that it wouldn't get wiped...
Whoops. At least it's all working now though

Pixel XL rooted with TWRP updated to February build on its own!

So, something pretty strange just happened. Earlier today I downloaded the latest OTA to my phone to flash with TWRP sometime in the next few days. I was playing around with my phone tonight and setting up Google Assistant to work with my Nest thermostat. The Assistant wasn't consistently recognizing the ability to adjust my thermostat so I did a simple reboot thinking it may solidify things. Much to my surprise, when I rebooted the phone, I noticed the Nougat 'N' in the status bar and when I pulled down the notification drawer it said "finishing upgrade," or something to that effect. STRANGE. I figured, surely my phone didn't just update on its own, so I checked about device and surely I'm on the latest build. Went to reboot my phone and TWRP was replaced with the factory recover and I no longer have root.
In the end, I have no idea how this happened. Everything I have read says updates will fail with a modified system and in fact I've tried updating in the past only to have it fail. Any ideas How or why this happened?

You got a real SMARTPHONE!

mlin said:
Everything I have read says updates will fail with a modified system and in fact I've tried updating in the past only to have it fail. Any ideas How or why this happened?
Click to expand...
Click to collapse
While I can't explain how this happened, I can point out that recovery is part of the boot image. And SuperSU is a "systemless" root method that also modifies the boot image. So your system image would appear as stock.

Sounds very interesting... I hope someone could answer this.

FlashFire? Also, do you have auto-update disabled in developer settings?

i got mine not long ago and had 7.1 on it and i did root and added twrp and in the background it downloaded 7.1.1 and when i did a reboot it installed it with no issue.

turn off auto update

sliding_billy said:
FlashFire? Also, do you have auto-update disabled in developer settings?
Click to expand...
Click to collapse
Thanks for all of the responses. No flashfire. Auto update was on. I thought it was weird that with root, custom recovery and substratum theming that my phone updated, especially given the fact that I have tried to update several times through the system updates menu and it has always failed... No clue why it suddenly worked, and furthermore why it happened out of the blue.

mlin said:
Thanks for all of the responses. No flashfire. Auto update was on. I thought it was weird that with root, custom recovery and substratum theming that my phone updated, especially given the fact that I have tried to update several times through the system updates menu and it has always failed... No clue why it suddenly worked, and furthermore why it happened out of the blue.
Click to expand...
Click to collapse
Purely hypothesis, but this update seemed to touch very few core system files and maybe just by luck none of what normally would cause it to fail was checked for changes. Recovery seems to be it's own animal as running TWRP sideload just wipes all recovery. In your case it replaced it with stock since you ran basically a standard OTA.

fletch33 said:
i got mine not long ago and had 7.1 on it and i did root and added twrp and in the background it downloaded 7.1.1 and when i did a reboot it installed it with no issue.
Click to expand...
Click to collapse
Yeah, I knew TWRP alone wouldn't interfere with the update, but I thought root and other mods would. This is why I wasn't surprised when trying to update previously failed but was super surprised when it suddenly worked.

Apparently my wife's Pixel did this today as well. She said she didn't ever see anything about an update.
Its a Verizon model but was rooted, bootloader unlocked, with twrp installed.
It was previously on the December update just like my Pixel XL, but now is on February.
It currently won't make calls or record video, which is why she even asked me about it. I started working on it and noticed it was no longer rooted or had TWRP. I just got those two back and now have to try to get calls working.

jsbeagle said:
Apparently my wife's Pixel did this today as well. She said she didn't ever see anything about an update.
Its a Verizon model but was rooted, bootloader unlocked, with twrp installed.
It was previously on the December update just like my Pixel XL, but now is on February.
It currently won't make calls or record video, which is why she even asked me about it. I started working on it and noticed it was no longer rooted or had TWRP. I just got those two back and now have to try to get calls working.
Click to expand...
Click to collapse
Interesting, I was on the December update as well. No problems with calls or video though. Very strange that in 2 months the January patch never successfully applied but the February patch did. Good luck with calls and video.

A full factory image flash got everything working. It kept working after installing TWRP, but after I root (SuperSU v2.79 SR3) it stops again.

jsbeagle said:
A full factory image flash got everything working. It kept working after installing TWRP, but after I root (SuperSU v2.79 SR3) it stops again.
Click to expand...
Click to collapse
What stops again?
I am on 7.1.2 Beta and everything works good.
Whats not working for you?

After I root, the phone app gets sluggish, phone call audio doesn't work, the camera app "can't connect to camera" if you try switching to video, and youtube videos don't work in the app. They worked in the browser but had no audio.

jsbeagle said:
After I root, the phone app gets sluggish, phone call audio doesn't work, the camera app "can't connect to camera" if you try switching to video, and youtube videos don't work in the app. They worked in the browser but had no audio.
Click to expand...
Click to collapse
Granted, after I got the update everything seemed a bit smoother. Audio seemed louder and more crisp.
Have you tried a factory reset?

Scott said:
What stops again?
I am on 7.1.2 Beta and everything works good.
Whats not working for you?
Click to expand...
Click to collapse
Well, I guess its not even related to rooting. I had reflashed factory 7.1.1, installed twrp, and everything was still working. After I installed a few apps and restarted, all that stuff's not working again.
It doesn't even work in safe mode.
Just did a factory reset and it didn't help.

jsbeagle said:
Well, I guess its not even related to rooting. I had reflashed factory 7.1.1, installed twrp, and everything was still working. After I installed a few apps and restarted, all that stuff's not working again.
It doesn't even work in safe mode.
Click to expand...
Click to collapse
Thats really odd. Maybe its an app thats not updated for 7.1.1.
I would reflash, let it wipe, then run it as a new phone for 24hrs. If it runs fine then I would install only essential apps, one by one and test after each one. Your sure to find the rotten apple that way. :good:
Good luck!