[Q] Noob question 11S OTA - ONE Q&A, Help & Troubleshooting

So my phone installed the update via system>update. I lost root right? I've also notice a decrease in performance. This might be unrelated but I figured I'd so anyways.

t0mD said:
So my phone installed the update via system>update. I lost root right? I've also notice a decrease in performance. This might be unrelated but I figured I'd so anyways.
Click to expand...
Click to collapse
Just boot into custom recovery and flash root again...

Related

[Q] Does rooting affect OTA?

Hi guys,
I was wondering if rooting the phone interferes with the ability to receive OTA's?
I know OTA doesn't work with most other devices after rooting but I'm hoping it works with the OnePlus One as it comes with CM as stock rom...
Thanks!
Regards
Pihkal said:
Hi guys,
I was wondering if rooting the phone interferes with the ability to receive OTA's?
I know OTA doesn't work with most other devices after rooting but I'm hoping it works with the OnePlus One as it comes with CM as stock rom...
Thanks!
Regards
Click to expand...
Click to collapse
Just got my Oneplus today. My experience through 4 updates is that SuperSU gets uninstalled, which unroots your phone. You just need to boot into TWRP and reflash SuperSU after the updates and you're rooted again.
jtchinoy said:
Just got my Oneplus today. My experience through 4 updates is that SuperSU gets uninstalled, which unroots your phone. You just need to boot into TWRP and reflash SuperSU after the updates and you're rooted again.
Click to expand...
Click to collapse
As long as it installs the OTA I'm fine with reflashing SuperSU.
And judging from your reply TWRP also doesn't interfere with installing the OTA, great! :good:
Guess I'll be unlocking my bootloader (and having my phone wiped, damned) and rooting it.
Can't live without the Xposed Framework. :laugh:
Thanks!
Pihkal said:
As long as it installs the OTA I'm fine with reflashing SuperSU.
And judging from your reply TWRP also doesn't interfere with installing the OTA, great! :good:
Guess I'll be unlocking my bootloader (and having my phone wiped, damned) and rooting it.
Can't live without the Xposed Framework. :laugh:
Thanks!
Click to expand...
Click to collapse
could of searched and found the answer... question has been asked quite a few times. also there is a setting in SuperSu to keep root in upgrades. Either way OTA or just wait for a rooted version which you probably would get faster than OTA in most cases
https://forums.oneplus.net/threads/persistent-root-after-ota.49868/
http://forum.xda-developers.com/oneplus-one/help/ota-updates-root-t2848715
http://forum.xda-developers.com/oneplus-one/help/ota-updates-root-unlock-t2873263
http://forum.xda-developers.com/oneplus-one/help/to-root-stay-stock-getting-ota-s-t2809334
http://www.reddit.com/r/oneplus/comments/2eyf2t/ota_after_root/
and there's more......

[Q] Unable to get back to stock

I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse
TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?
dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.
nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM
back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...
nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?

[Q] Question about root on 05Q

Is rooting the OPO on 4.4.4 05Q the same as rooting it on 4.4.4 44S? thanks a lot guys. I couldn't find any answer on this anywhere else considering this update is fairly new
Yes. It's the same no matter what firmware version you're on.
Transmitted via Bacon
no_username_available said:
Is rooting the OPO on 4.4.4 05Q the same as rooting it on 4.4.4 44S? thanks a lot guys. I couldn't find any answer on this anywhere else considering this update is fairly new
Click to expand...
Click to collapse
...and you just need to update SuperSU app in order to maintain 05Q rooted (if previous version was, of course...)
This is odd. I was previously Unlocked, and Rooted, with SuperSU 2.37. After OTA update to 05Q, my Root is gone. No SuperSU app in my installed program list.
Okay, so I go look for the latest, find that it's now at 2.46, download, reboot, flash (no errors), reboot, and i'm back into my phone. But: Still no SuperSU in my apps list, and I'm getting warnings from XPrivacy that it's not running. Does anyone recognize these symptoms? Am I still rooted or not?
thanks guys so can i use any 4.4.4 root toolkit?
i guess you can, unfortunately i'm not skilled in android things but as timmaaa said nothing changed between 44S and 05Q so your toolkit should work if you root your phone for first time. Take a little time to install custom twrp recovery and make a nandroid backup first...just in case of...
no_username_available said:
thanks guys so can i use any 4.4.4 root toolkit?
Click to expand...
Click to collapse
Don't use a toolkit, they're bad news. They cause more problems than they're worth, plus they allow you to do things to your device without actually knowing what's going on, which is bypassing some very crucial learning and knowledge.
This phone is very easy to unlock and root. Very easy. Just go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Thanks man, ill use that
no_username_available said:
Thanks man, ill use that
Click to expand...
Click to collapse
Feel free to ask any questions if you get stuck.
timmaaa said:
Feel free to ask any questions if you get stuck.
Click to expand...
Click to collapse
Thanks man ill let you know. Contemplating rooting now lol might wait till I need to reset because of lack of space because i really don't want to set everything up again

[Q] Microphone Problem {} Need Help

Hey, I have got a problem with my OnePlus One for quiet some time..
It started about 2 months ago - Whenever I'm on a call, the other side can barely hear me unless I'm on speaker.
I did some reading and there are suggestions that this is because of some mis-written code or something, that makes the input of the microphone low, so that only a small precent of the sound is being transferred to the one I'm talking to.
this may or may not be the problem, but I wanted to ask you fellows if anyone has any suggestion on what's causing this and how to try & solve it.
I'm Running a Stock 5.0.2 Cm12s with the latest OTA update, and this problem started when I had Stock 4.4.4 CM11s.
Device isn't rooted & never was.
Locked Bootloader.
Please help if you can
Lidor167 said:
Hey, I have got a problem with my OnePlus One for quiet some time..
It started about 2 months ago - Whenever I'm on a call, the other side can barely hear me unless I'm on speaker.
I did some reading and there are suggestions that this is because of some mis-written code or something, that makes the input of the microphone low, so that only a small precent of the sound is being transferred to the one I'm talking to.
this may or may not be the problem, but I wanted to ask you fellows if anyone has any suggestion on what's causing this and how to try & solve it.
I'm Running a Stock 5.0.2 Cm12s with the latest OTA update, and this problem started when I had Stock 4.4.4 CM11s.
Device isn't rooted & never was.
Locked Bootloader.
Please help if you can
Click to expand...
Click to collapse
try to flash this http://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
I had the same problem and it fixed it.
The only thing is that i had to flash it after every rom change.
solokiller11 said:
try to flash this http://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
I had the same problem and it fixed it.
The only thing is that i had to flash it after every rom change.
Click to expand...
Click to collapse
Does it not require a root access?
Lidor167 said:
Does it not require a root access?
Click to expand...
Click to collapse
it requires a custom recovery but not sure about root, i guess its required but not sure
solokiller11 said:
it requires a custom recovery but not sure about root, i guess its required but to sure
Click to expand...
Click to collapse
I don't even know what costum recovery means..
Lidor167 said:
I don't even know what costum recovery means..
Click to expand...
Click to collapse
read this thread, its a great one and explains everything you need to know
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
you don't have to read everything (although recommended)
solokiller11 said:
read this thread, its a great one and explains everything you need to know
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
you don't have to read everything (although recommended)
Click to expand...
Click to collapse
So in order to install a custom recovery ( say TWRP ) I do not need root acess? do I only need to follow step no.2 at the guide you gave me?
Lidor167 said:
I don't even know what costum recovery means..
Click to expand...
Click to collapse
Lidor167 said:
So in order to install a custom recovery ( say TWRP ) I do not need root acess? do I only need to follow step no.2 at the guide you gave me?
Click to expand...
Click to collapse
Yes, But it is also recommended to root the phone. Root is a great thing to have

Stuck at 5.1.1

Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
You won't be able to update while rooted. Actually updating with a factory image is probably safer than taking an ota update. Personally, I think the update is worth it.
Sent from my SM-T530NU using XDA-Developers mobile app
hexr96 said:
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
Click to expand...
Click to collapse
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
acejavelin said:
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
Click to expand...
Click to collapse
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Tel864 said:
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps stability is not the real argument here... both are stable, as are most production ROMs, I have been using Marshmallow since early December and never had any real problems. But there are pros and cons to both and depending on your situation one may be better than the other, but I guess that wasn't really the point of this thread so I will say I half agree with your statement.
I would also have to relock the bootloader, correct?
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
No
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
Nope, in fact, you can't relock the bootloader even if you want to. The bootloader lock state is not relevant to taking an OTA.
Thank you everyone

Categories

Resources