My last phone was a OnePlus and it was/is a great phone, however I like the Nexus line and the pure android experience. I thought I would try the N6 and see what I thought. I was not able to find it on Motorola or Google, so being I have a bunch of upgrades figured I would grab a ATT one, de-ATT it and done.
So I boot unlocked, rooted , TWRP and got rid of any ATT taint. But something was calling me back to the OPO. So, day 14 of the 14 day return policy comes and I put in a return. I cleaned up the phone, re-installed stock, unrooted and last locked my bootloader. However, and I would reboot and check after each step, when I re-locked the bootloader, it would go to status = 2, say its locked, but would basically boot-loop no matter how many times or what I did. I would unlock and it worked just fine. I tried everything and nothing worked. If anything, it would flash to the Google screen 2x then hit the recovery (android with the blue star belly). I could power/up-volumn and it would show clear data sometimes, but still nothing.
Any ideas why? Is there any way to change that status 2, which I think shows it was unlocked once, to just 0 or 1? Think this had anything at all to do with ATT?
And just FYI, I cancelled the return and love my N6. I didn't realize how attached I grew to the real estate.
Related
So I have read about this issue a couple of other times on here, where the device is playing music and it randomly lowers the volume and it may/not come back up to full volume. Well this is happening to me. I can't make it reproduce, but if I throw on some Spotify for a little bit or YouTube I notice it randomly. For me, if I keep hitting the volume up, 5-10 times, the volume comes back up. It's important to note the volume indicator in Android never says it lowered, it says its full. But after hitting the volume up numerous times, it'll come back up. It's also worth noting I don't have any notifications coming through at these times, and my screen has been on so the notification screen that pops up wouldn't be lowering it.
I have done multiple factory resets, flashed to M, to L, flashed different ROMs / Kernels etc, but I always stick to stock. I only flashed those to see if I could get it to go away.
I went to the Sprint store and the tech said he needed to see the issue for him to replace it free of charge. I have insurance, so I should be able to get a free replacement IF its a device fault and not my own. If it were my own I'd have to pay. So here's where the issue comes in. I took it in the first time, and he hooks it up the the Cellebrite machine to see if he can see a fault in the device through that, and it says its rooted (which it was w/ bootloader unlocked). He is cool about it, telling me he is supposed to flag my phone so I can't have it replaced free of charge, but he isn't going to. He said if I come back and it isn't rooted he'd try again. I flash the newest Android M dev preview from factory images (no root) and bring it back in. He hooks it up, and it shows up as an N7 to the Cellebrite MAchine / diag app. He manually selected N6 but it still says its rooted so he can't do anything.
Before I moved I would go to Sprint all the time if I had a device fault (different devices) and that particular store said Sprint didn't care if it was rooted, it didn't matter as per Sprint employee guidlines. But now it seems it does? Neither of these stores (before I moved and now) are corporate stores either. But I know my local corporate store used Cellebrite too.
So I have a couple questions here:
1) Would my bootloader being unlocked really throw the "rooted" flash to the Cellebrite diag app? It had TWRP but was definitely NOT rooted the second visit.
2) I've read that relocking bootloader on 5.1.1 can be a little risky, is this true?
3) And he mentioned that he knew of the issue but since it was "rooted" he couldn't get me a replacement, but that I could try to get customer service phone support to send me one. He said I would need a reason I couldn't bring it in the Sprint store, though.
I didn't buy it through the Play Store so Google said they won't replace it (even though its within the year warranty) but to get Motorola to replace it. The problem there is almost the same as insurance. With insurance, I just pay a $200 deductible and get a new N6. With Motorola, they have to put a hold on my card for like $580, then they will refund all of it but the $25 fee for them sending me the phone first and then me sending it back. (Alternative is me sending my phone in first, but I can't since I don't have an alt phone).
Anyone know a direction I could go?
P.S. Sorry for the wall of text, but its just been a long drawn out process.
DRatJr said:
So I have read about this issue a couple of other times on here, where the device is playing music and it randomly lowers the volume and it may/not come back up to full volume. Well this is happening to me. I can't make it reproduce, but if I throw on some Spotify for a little bit or YouTube I notice it randomly. For me, if I keep hitting the volume up, 5-10 times, the volume comes back up. It's important to note the volume indicator in Android never says it lowered, it says its full. But after hitting the volume up numerous times, it'll come back up. It's also worth noting I don't have any notifications coming through at these times, and my screen has been on so the notification screen that pops up wouldn't be lowering it.
I have done multiple factory resets, flashed to M, to L, flashed different ROMs / Kernels etc, but I always stick to stock. I only flashed those to see if I could get it to go away.
I went to the Sprint store and the tech said he needed to see the issue for him to replace it free of charge. I have insurance, so I should be able to get a free replacement IF its a device fault and not my own. If it were my own I'd have to pay. So here's where the issue comes in. I took it in the first time, and he hooks it up the the Cellebrite machine to see if he can see a fault in the device through that, and it says its rooted (which it was w/ bootloader unlocked). He is cool about it, telling me he is supposed to flag my phone so I can't have it replaced free of charge, but he isn't going to. He said if I come back and it isn't rooted he'd try again. I flash the newest Android M dev preview from factory images (no root) and bring it back in. He hooks it up, and it shows up as an N7 to the Cellebrite MAchine / diag app. He manually selected N6 but it still says its rooted so he can't do anything.
Before I moved I would go to Sprint all the time if I had a device fault (different devices) and that particular store said Sprint didn't care if it was rooted, it didn't matter as per Sprint employee guidlines. But now it seems it does? Neither of these stores (before I moved and now) are corporate stores either. But I know my local corporate store used Cellebrite too.
So I have a couple questions here:
1) Would my bootloader being unlocked really throw the "rooted" flash to the Cellebrite diag app? It had TWRP but was definitely NOT rooted the second visit.
2) I've read that relocking bootloader on 5.1.1 can be a little risky, is this true?
3) And he mentioned that he knew of the issue but since it was "rooted" he couldn't get me a replacement, but that I could try to get customer service phone support to send me one. He said I would need a reason I couldn't bring it in the Sprint store, though.
I didn't buy it through the Play Store so Google said they won't replace it (even though its within the year warranty) but to get Motorola to replace it. The problem there is almost the same as insurance. With insurance, I just pay a $200 deductible and get a new N6. With Motorola, they have to put a hold on my card for like $580, then they will refund all of it but the $25 fee for them sending me the phone first and then me sending it back. (Alternative is me sending my phone in first, but I can't since I don't have an alt phone).
Anyone know a direction I could go?
P.S. Sorry for the wall of text, but its just been a long drawn out process.
Click to expand...
Click to collapse
Known issue. Please see this thread:
http://forum.xda-developers.com/showthread.php?t=3136759
---------- Post added at 08:33 AM ---------- Previous post was at 08:30 AM ----------
For relocking the bootloader:
http://forum.xda-developers.com/showthread.php?t=3067302
---------- Post added at 08:35 AM ---------- Previous post was at 08:33 AM ----------
Also, if you're going to RMA, just flash a factory image first, relock, and you're all set.
@danarama
i don't think an RMA will help.
danarama said:
i don't think an RMA will help.
Click to expand...
Click to collapse
So all nexus 6 have this issue? Getting a new device would still have it too?
DRatJr said:
So all nexus 6 have this issue? Getting a new device would still have it too?
Click to expand...
Click to collapse
Did you read the link?
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
Hi, (spent some time searching for answers; if this is covered elsewhere I missed it, sorry)
So, I'm a bit late to the party but I went and found a site still offering Nexus 6 "Factory new" XT1103 unit still in stock after so long, and bought myself one.
(1) I love it, and totally understand why so many people love it
(2) I'm a little concerned in that the bootloader seems to ALREADY be *unlocked*. I certainly didn't do it. Did Google ship these out with the bootloader pre-unlocked? (I tried to google this and found nothing; it strikes me as unlikely). And when booting into the fastboot mode, I don't see any entry saying "secure boot", which bothers me a bit since my Nexus 4 has this (is this deprecated and I missed the news?).
So, I assume that I can just download factory images off Google and flash them myself in order to be sure about my firmware (a little quicker since the bootloader is already unlocked, yeah?). But how do I verify that the bootloader *itself* isn't compromised in any way such that there's no issue with persistent malware, say?
(why yes, people HAVE said that I'm pretty paranoid, why do you ask? Have you been following me around?)
If you download the full firmware image and run the flash-all.bat command, it will overwrite the bootloader and erase everything on the phone. So even if the bootloader were somehow compromised (I really doubt it) this will take care of the problem.
Thanks, I'll do that. On the Google Nexus download page I see both "factory" and "OTA" images - I presume I should use the "factory" image?
I'm really spooked as to WHY the bootloader is unlocked, though, since I certainly did not do it and the box was shrinkwrapped. Does anybody know if anyone else has ever received a Nexus 6 "pre-unlocked"?
New and refurbished units from Motorola did not come shrink-wrapped. In order to open the box you needed to cut the label at the dotted line on the back of the box. Yours could not have been new nor a factory refurb, not just because the box wouldn't have been shrink-wrapped, but also because a refurbished unit would have had the motherboard refurbished so the bootloader status code would be set to 1 (Locked). A previously unlocked bootloader that has been locked would have a status code of 2, with unlocked having a status code of 3.
Strephon Alkhalikoi said:
New and refurbished units from Motorola did not come shrink-wrapped. In order to open the box you needed to cut the label at the dotted line on the back of the box. Yours could not have been new nor a factory refurb, not just because the box wouldn't have been shrink-wrapped, but also because a refurbished unit would have had the motherboard refurbished so the bootloader status code would be set to 1 (Locked). A previously unlocked bootloader that has been locked would have a status code of 2, with unlocked having a status code of 3.
Click to expand...
Click to collapse
...
ok the first time I ever looked, my status code was 3.
I definitely was not the guy who unlocked it.
argggggghhhhhhhhhhh
ok, so would flashing with the full factory image (per the first reply above) be sufficient for me to not have to worry about persistent malware lurking in e.g. a compromised bootloader? I'm not in a position to get a different unit and I'm just really bummed out about this now (especially since I've already logged in with my google account on the phone).
How could I check/verify (some kind of hash) after a full flash that everything is "as it should be"?
weilt said:
...
ok the first time I ever looked, my status code was 3.
I definitely was not the guy who unlocked it.
argggggghhhhhhhhhhh
ok, so would flashing with the full factory image (per the first reply above) be sufficient for me to not have to worry about persistent malware lurking in e.g. a compromised bootloader? I'm not in a position to get a different unit and I'm just really bummed out about this now (especially since I've already logged in with my google account on the phone).
How could I check/verify (some kind of hash) after a full flash that everything is "as it should be"?
Click to expand...
Click to collapse
Simply flash one of the factory images from Google's pages and all your concerns will be eliminated. But, you're being needlessly paranoid regarding the bootloader. All the bootloader does is transfer control from the low level firmware of the device to the Android kernel. Once it does that it sits quietly until the next time you boot. It has no contact with the outside world that I'm aware of so any malware in the bootloader would be useless.
got it, thanks so much for the help!
(I don't know enough about the android bootchain so was envisioning there'd be e.g. enough space allocated for the bootloader such that it would be possible to put in some sort of persistent malware that could be injected into subsequent boots; if it's just a tiny thing (especially if it gets overwritten anyhow when there's a full flash!) then alrighty I'm already safe since I already nuked the firmware twice
Hi, after doing my fire 7, my dad gave me his memopad 7hd k00b ( I believe) to try and "fix" Essentially I think it got rooted, and flashed, but something went wrong. On the start up/set up for android of some description, everything seems to pop up as stopped working, click ok. Everything, I've seen superuser, chrome etc. By clicking OK on all these boxes, You can get to screen 5 of 8, where it asks to set up google account, then you get process.com.google.process.gapps has stopped. To then try and fill in screen 5, you have to click ok to that message, however it then resets the set up and you go back to screen one (select Language etc). I can't get past that.
We're talking last year, early quarter perhaps that this was done, so it's just sat and stewed doing nowt since then.
Is there anyway I can "fix" this?
I wanted to reply to myself to say eventually got it sorted. I used something called SP Flash Tool V3 which, following a guide, allowed me to reflash it, unlock it perhaps, not quite sure, but needless to say allowed me to get access to boot loaders(?) and then flash on a new rom. So I have it back working again. Most replying just in case someone else is searching globally and it comes up.
My daughter was all excited today to get the Android 12 update on her 4a 5G. Once she installed it, the speakers all quit working. No sound from the phone at all, and I've check every single setting. When you make OR receive a phone call, it is stuck on speaker phone, but the no sound comes out of the speaker. The speaker phone button stays lit up and you can't turn it off.
We have rebooted it and I finally did a full factory reset, and the problem persists. I didn't reinstall any apps. Didn't even add her account. Just a clean FDR and reboot and still now sound.
Tried to flash back to Android 11, but the bootloader is locked, and it the OEM Unlock button is greyed out, and says its not available on carrier-locked phones. This is from T-Mobile, and Its financed, so I doubt they will unlock the device, so I won't be able to unlock the bootloader. I feel very stuck right now.
I've been flashing Nexus, Pixel, and Samsung for years now, going back to the original Moto DROID, adn I can NOT figure out how to fix this. I'm guessing I'm going to have to get a replacement from T-Mo.
Just had issues myself with a locked bootloader. Call a representative and describe the issue. They unlocked my pixel after saying I was using development tools.
Just solved this issue, I didn't have app auto updates on, there was an update waiting for Speech Services from Google. Once that had been installed (there might have been 2 separate updates) microphone and speakers started working instantly again.
D