Hey guys, I'm a long term lurker to XDA's Forums, but had to make a new account and share a problem I'm having..
Long story short: My rooted Nexus 6's 'volume down' stopped working.
I've only had the phone for about 6 days now, so I've begun making contact with Google in hopes i can just send it back... But it's bothering me enough (worried about warranty) that i thought I'd ping this community too about the scenario.
I'm quite certain it's not a software issue because (sadly) the volume-down button doesn't work at boot either (preventing me from getting in the recovery mode).
As per what I've done:
I'm still using the stock firmware.. I've unlocked and rooted it (as you know already), and just installed (and configured) Greenify, Light Flow and Titanium Backup. I did not freeze or uninstall any apps; i just backed a few up that have complicated configurations. I even got the paid versions of them all to help support the work of the developers (not that it matters). I have not installed Xposed (alpha) or any custom recovery tool (CWF or TRWP) at this point.
Today i installed BusyBox Pro too but never did anything further. I can't be sure when the actual (down volume part of the) rocker stopped working because i never really paid much detail to this until it became evident today, I know i needed it to unlock the phone 4 days ago when i first went through with the process. So it stopped working somewhere between then and now..
Suggestions or Advice?
lead2gold said:
Hey guys, I'm a long term lurker to XDA's Forums, but had to make a new account and share a problem I'm having..
Long story short: My rooted Nexus 6's 'volume down' stopped working.
I've only had the phone for about 6 days now, so I've begun making contact with Google in hopes i can just send it back... But it's bothering me enough (worried about warranty) that i thought I'd ping this community too about the scenario.
I'm quite certain it's not a software issue because (sadly) the volume-down button doesn't work at boot either (preventing me from getting in the recovery mode).
As per what I've done:
I'm still using the stock firmware.. I've unlocked and rooted it (as you know already), and just installed (and configured) Greenify, Light Flow and Titanium Backup. I did not freeze or uninstall any apps; i just backed a few up that have complicated configurations. I even got the paid versions of them all to help support the work of the developers (not that it matters). I have not installed Xposed (alpha) or any custom recovery tool (CWF or TRWP) at this point.
Today i installed BusyBox Pro too but never did anything further. I can't be sure when the actual (down volume part of the) rocker stopped working because i never really paid much detail to this until it became evident today, I know i needed it to unlock the phone 4 days ago when i first went through with the process. So it stopped working somewhere between then and now..
Suggestions or Advice?
Click to expand...
Click to collapse
Personally, I wouldn't worry too much because it's a hardware issue and probably not software related. However, since you still have stock recovery, I think all you need to do is unroot via settings in SU, and uninstall root apps. If you feel the need to relock, use ADB to reboot to bootloader then you can use fastboot to OEM lock I believe.
If you need to get into bootloader, download https://play.google.com/store/apps/details?id=simple.reboot.com onto your Nexus 6 and reboot to bootloader using that app.
From that point on, you can reflash factory images https://developers.google.com/android/nexus/images#shamu
And relock your bootloader.
You can also ask Google for a advanced RMA (they'll ship you a Nexus 6 and charge you for a Nexus 6 pending, when they receive your old Nexus 6 the charge will be removed).
Thanks for your help!
I was able to restore everything back to factory and relock the firmware using just the usb cable.
The following command allowed me to always gain access to the bootloader in every situation (had to enable Debugging mode after flashing back stock firmware with a temporary account to do the relocking)
Code:
adb reboot bootloader
It's software problem my hardware is ok and and after rooting phone four mobile s400 volume down button isn't working.
So have anyone experienced?
Related
Wondering if any of you guys could help me out here?
By the way, if this is the wrong section for this, apologies and feel free to move?
Nexus 7, 16gb, rooted with stock 4.1.2. I have not edited the build.prop, still using the 4.1.2 Keyboard, Gmail etc.
So, nothing changed other than unlocked/rooted.
I have superSU pro and have 'Survival Mode' enabled, which is basically and OTA Rootkeeper (I am sure you already know this...)
When we got the OTA to 4.1.2, it worked no problem, survival mode worked and I kept root and custom recovery.
So this morning I get a notification to upgrade to 4.2, which I done. It restarted, and installed with no errors etc, then comes the Google screen with the unlocked padlock... and it stayed this way for an hour, so I am assuming it is borked?
I restarted it, same again, so rebooted into the bootlaoder menu. Going into recovery shows the android dude on his back, red triangle ! etc, so I gather my custom recovery is gone.
So the question is, where to go from here, and is there a walkthrough I can use to resuce this (I am techy enough minded, but given the state it is in, loathed to make it worse down to sheer stupidity)?
Any help would be much appreciated guys.
BTW - I used Wugs Toolkit to root, so that is all set up with drivers etc, can that be used now to recover?
No ideas?
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.
What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?
get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts
So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no ota back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app
sookieball said:
So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no it's back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
well, to flash stock, you dont use twrp, you use fastboot while youre in the bootloader. and in N, allow oem unlock is automatically enabled.
It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app
sookieball said:
It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
how? did you do fastboot oem unlock?
Maybe you've already tried this, and I don't know if it will work, but have you tried re-enrolling and unenrolling in the hope that it will jog the revert mechanism into life?
I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app
sookieball said:
I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
you pribably cant oem unlock while on N then. that probably why they made it unavailable. im not on N now, so cant test.
What about trying a sideload of the full OTA? I thought (I might be wrong) that it's independent of a locked bootloader.
https://developers.google.com/android/nexus/ota#instructions
It's worth a shot, especially as it doesn't overwrite your data.
On a related note, I'm on preview 3 - battery drain when idle is higher than what it was on stable M, so thinking about reverting back to M.
1. To avoid a factory wipe, can I just flash the img files from the stable M (skipping userdata) on top of the preview 3?
2. If so, to avoid getting the N preview update notification, I guess I will need to un-enroll from the beta program. Will that cause an OTA to be sent back to my phone (causing factory wipe as described on the beta page)? Or does it recognize that I'm already on 'M' and skip the OTA?
3. Before I do this, is it possible to flash the radio only from the latest "M" image on the "N" preview? (could that help with the drain when idle?)
Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104
dahawthorne said:
Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104
Click to expand...
Click to collapse
LOL! Yes, I did! And thank you for that as well - the part that I didn't understand (and unless I missed it in your response, I don't think we talked about in that post) was - since I'd still be enrolled in the preview/beta program, how do I get out of the program, without getting factory reset.
(I do have a nandroid backup as a last ditch option - trying to do this the 'clean' way first)
The preview is working well for me as well - skype is the only app giving me grief, but I can live with that. The battery drain on idle seems to be significantly higher than what I encountered with "M" stable. With barely any usage this morning (screen on for 11 minutes), my battery is at 77% (full charge and off the charger at 10 pm last night). Cell Standby is the the highest drain (6%). Phone idle and Android system tied for 2nd place at 3%.
With the latest M build, I'd be at over 90% battery remaining (with similar usage).
You're right on all counts...
I think the answer to your wipe question is that you'd have to agree to do it - if you unenrol and have already reverted manually to M, the downgrade OTA may be downloaded (though from my experience, as I said, I think the developers are smart enough to recognise that it's a waste of time and even that won't happen) but you would still have to push the button to accept it. They won't unceremoniously dump it on you without your permission.
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Looks like Google have a bit more work to do on their power management...
Edit: And in the 5 minutes since I wrote this, with the phone sitting beside me, screen off, nothing running, it's already down to 74%. Not at all impressive. Despite being relatively happy with it, I may have to renege on my previous comment that I can't see myself reverting to M.
And before you ask, I'll be reverting using my TWRP backup of M which I took immediately before I installed N...
Thank you
I'll wait for the June security update (factory image) and install that directly (skipping userdata). If that fails, I'll revert to the TWRP backup. (restoring TWRP on my old N5 has given me grief in the past, so going to avoid that if possible)
Edit: maybe I'll try flashing the radio from the May image onto "N" and see if that helps. The battery drain appears to be radio related.
Done. No problem at all. TWRP took about 12 minutes to restore 7GB of data, then a rather nerve-racking 5 minutes with the Google quad-icon swapping bits, and I'm back to MOB30I.
Seven updates waiting; BBC Radio, Skype, Google Drive, Sygic, all the broken apps working again, still have root.
Welcome back, old M world...
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
I've also just unenrolled from the Beta program, and checked for a system update. Exactly as I thought, "Your system is up to date" on MOB30I. I know that the OTAs have been slow for some people, but I don't expect to see the revert OTA - I'll post in this thread if I ever do.
dahawthorne said:
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
Click to expand...
Click to collapse
Would the fact that I'm rooted cause any issues with sideloading the OTA? (I realize the new OTA is essentially a full image, so it should just overwrite the system, and I'd have to reroot after that)
No problems at all, no. My N5 was rooted & encrypted, and the OTA slid in easily. As I said in another thread, it boots into TWRP but the OTA is designed to handle that. I installed TWRP again anyway, probably pointlessly but just to be on the safe side, and then used it to install SuperSU 2.74.
Easy as pie...
I unenrolled, got a prompt for system "update" back to MM, it downloaded, and now I am going on 30 minutes on the install part....been stuck on the reboot screen with 4 colorful circles....
How long does it take to re-install MM? TIA
EDIT: Decided to hold down power button for about 5 seconds and it rebooted to setup screen
dahawthorne said:
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Click to expand...
Click to collapse
I ended up flashing the radio (only) from MOB30I on to the N preview, and so far, the battery life on idle is back to how it was on M. I think I have a reason to stick on to the N preview a bit longer now
banditsw said:
How long does it take to re-install MM? TIA
Click to expand...
Click to collapse
Looks like you got it sorted out, but just for future reference, the reason it took long is because it essentially factory reset your phone - a factory reset with full wipe on the encrypted N6 cane take 20-30 minutes.
I'm impatient, me, so by the time I read this I was already back on MOB30I, but in any case I'm happier to have all working apps without the rash of library errors and force-closures. Interesting thread...
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8
dahawthorne said:
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8
Click to expand...
Click to collapse
I ended up reverting back to the "M" stable image yesterday (was waiting for the June image to be available). No issues with the "N" to report, except one custom app that I use was giving me some issues.
Anyway, thought I'd share my "downgrade" story
If you do the downgrade the right way (un-enroll from the Beta program), and get the OTA back to the latest "M", it will likely go well - because it performs a factory reset on your phone.
I however, didn't wait to set my phone up from scratch (lazy), so I flashed the factory image for the latest "M" (and skipped userdata.img). Bad idea. Flash went thru' successfully, but I ended up with pretty much an unusable phone because two system processes kept crashing in a loop after booting up. I then tried ADB sideload for the new OTA image file - same results. Wiped cache partition - no difference.
I then remembered that some apps (like Google Maps) had different versions for "N", and realized that the issue must be because of apps like that not being compatible with "M". Thankfully, I had a nandroid backup of the "M" (May security release) from before I installed "N", and I installed that - and then, updated to the June security release of "M".
Whew!
So, in summary, If you are rooted, take a nandroid backup in TWRP before you install "N" preview. If not, plan to factory reset your device after going back (or while going back) to "M" - no shortcuts.
Hello everyone, I used to have an account on here years ago and I just had to create a new one for the purpose of this thread. Let me know if this type of issue has already been resolved but I have spent a great deal of time trying to locate a solution with no results. I have an older HTC One m7 I started using again to try and use the hotspot on it because I have unlimited data I needed to root it. Only reason for the hotspot is because I just moved and I am still waiting for my internet service to be hooked up on the second. Anyways, down to buisness. I made myself a developer on my device, unlocked the bootloader and installed TWRP V2.5.0.0 onto my phone. All was going well until the phone went to reboot. After it rebooted I was in the TWRP recovery menu, and I went to back up. As soon as I clicked it the phone completely froze up on that screen. And then a lock image appeared with TWRP across where the combination would go and i could still see everything in the background. Install, back up, mount, restore, settings, reboot etc. And beneath the image of the lock, which actually appears to be unlocked it says swipe to unlock and has a slider beneath it. Completely unresponsive on the screen, I cannot select anything at all. No different combinations of presses on the volume keys or power button is resetting or doing anything. I cannot even get it to turn off. I did notice, when i long press the power button the back arrow and home button flash simultaneously (on the HTC One M7 those are touch screen buttons, that are actually visible even when the device is off, but also completely unresponsive. I did notice as well that if I plug in my phone charger in the background above the menu options it shows how charged my battery is, and appears to charge when I plug it in. It is a silver, HTC One M7, AT&T version, running android 5.0.2 Thank everyone in advance, I tried to be as detailed as possible but let me know if more information is required to understand what is going on here. Thank you!
***UPDATE***
Ok everyone, issue resolved luckily since I did not get any responses on here. To anyone experiencing that same issue that I described. I let the phone die completely while it was frozen on the TWRP screen. I plugged it in while pressing down volume, and power button at same time and that allowed me to access the bootloader finally once more! From there you can select fastboot, then select reboot and everything will kick back up like normal! Just in case anyone finally stumbles across this what is a safe way to root my phone other than using TWRP? Thank you in advance!
cbmccown said:
Ok everyone, issue resolved luckily since I did not get any responses on here. To anyone experiencing that same issue that I described. I let the phone die completely while it was frozen on the TWRP screen. I plugged it in while pressing down volume, and power button at same time and that allowed me to access the bootloader finally once more! From there you can select fastboot, then select reboot and everything will kick back up like normal! Just in case anyone finally stumbles across this what is a safe way to root my phone other than using TWRP? Thank you in advance!
Click to expand...
Click to collapse
The best way to root your phone is to use the custom ROM's root manager. This is built in to cyanogenmod based roms, and doesnt require SuperSU. there is no app and it doesnt bother you about installing binaries or updating.
I always used SuperSU until I used CM.
Of all the ways to install root management, are these two the best. There is kingroot if you arent that concerned about the use of this third method.
For many the SuperSU (also installed by TWRP) is the most popular. Many will not know of the Custom ROM settings for root management and will install SuperSU over their setup. Its probably gonna be found in developer options, the root access toggle. It might be found in plain old settings though.
kruc Ire said:
The best way to root your phone is to use the custom ROM's root manager. This is built in to cyanogenmod based roms, and doesnt require SuperSU. there is no app and it doesnt bother you about installing binaries or updating.
I always used SuperSU until I used CM.
Of all the ways to install root management, are these two the best. There is kingroot if you arent that concerned about the use of this third method.
For many the SuperSU (also installed by TWRP) is the most popular. Many will not know of the Custom ROM settings for root management and will install SuperSU over their setup. Its probably gonna be found in developer options, the root access toggle. It might be found in plain old settings though.
Click to expand...
Click to collapse
Also, it always restarts if you hold the power button down for 15 *long* seconds.
I did Search and Did not find a solution.
Locked Bootloader (NRT says it can sideload OTAs with a locked Bootloader)
In NRT I selected Advanced Utilities
in Advanced Utilities I select Sideload Update
Clicked OK on First Screen
Browse to my downloaded OTA file
Click NO I am not unlocked
Get The Android With Exclamation Point Screen
Below it is the Text "No command"
NRT Tells me to Power Volume Up (obvious error I power Volume up and down).
It tells me I should Have an option to "apply update from ADB", but it doesn't exist as an option (i just get the normal Bootloader options and nothing more)
What Am I missing?
EDIT:
The Problem was I was Holding Down Power and Volume UP at the same time and not letting go and that was the problem, when that didn't work I assumed it was a mistake in the documentation.
I needed to just push power then while holding quickly press Volume Up
Windows 10 Pro
I started to write a brief script, but without knowing how much you know it's pointless.
As a first step I suggest that you invest time in reading instead of using toolkits (though I'm a big fan of NRT myself). Start with learning to flash a recovery - TWRP is popular and easy to use, and it has a big button titled "Sideload" for when you're ready to try the OTA.
Or you could try this:
https://www.youtube.com/watch?v=5Fl3Vg0ALYw
But NOT using the toolkit...
Ive done tons of rooting and flashing but always on an rooted phone with unlocked bootloader. This time I actually reverted back to stock to get back to 7.1.1 and Was hoping to stay OEM Locked and unrooted for a change.
Unfortunately I have the Horrible Speakerphone issue and since clicking on Check for Update does not find the March Patch I thought id try to sideloaded it.
I imagine the patch is probably a slow roll-out??
So i guess NRT cannot flash an OTA to stock as advertised.
I think the general attitude here (forgive me if I've misread, people) is that there's no point in playing with a Nexus if you just want to keep it stock...
The whole point of owning a Nexus is the flexibility to play without too much risk, since with an unlocked bootloader and TWRP you can usually recover from any mishap.
"Check for update" has never worked for me on any Nexus. It always waits until I'm looking the other way and then sneakily downloads it. I got tired of that and just started to flash the factory images when they appeared, and since Google started making the OTAs available for sideload there's really no reason not to use them.
The latest N6F26U OTA has fixed the speakerphone, and Google have somehow backed out the Android Pay problem it introduced, so personally I'd go back to rooting and flashing rather than waiting on Google's whims.
And don't rely on NRT, excellent though it is...
dahawthorne said:
I think the general attitude here (forgive me if I've misread, people) is that there's no point in playing with a Nexus if you just want to keep it stock...
The whole point of owning a Nexus is the flexibility to play without too much risk, since with an unlocked bootloader and TWRP you can usually recover from any mishap.
"Check for update" has never worked for me on any Nexus. It always waits until I'm looking the other way and then sneakily downloads it. I got tired of that and just started to flash the factory images when they appeared, and since Google started making the OTAs available for sideload there's really no reason not to use them.
The latest N6F26U OTA has fixed the speakerphone, and Google have somehow backed out the Android Pay problem it introduced, so personally I'd go back to rooting and flashing rather than waiting on Google's whims.
And don't rely on NRT, excellent though it is...
Click to expand...
Click to collapse
The Problem was I was Holding Down Power and Volume UP at the same time and not letting go and that was the problem, when that didn't work I assumed it was a mistake in the documentation.
I needed to just push power then while holding quickly press Volume Up
So have you managed the sideload then?
YES and it fixed the Speakerphone
dahawthorne said:
So have you managed the sideload then?
Click to expand...
Click to collapse
YES and it fixed the Speakerphone