Nexus 6 Speakers Lower on their Own - Nexus 6 Q&A, Help & Troubleshooting

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?

Related

New Nexus Not Working

Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts

[Q] Moto X randomly dies

Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.

[Q] Hard brick after 5.01 OTA just out of the box

i just got my Nexus 6 today. Ran through the setup without restoring anything from my M8 (used Setup as New device option). Got to the home screen, looked up my WiFi MAC address and added it to my router. In the meantime over LTE I received my Gmail mail and a notice to update to 5.01. Downloaded the OTA, hit the "Reboot & Install" button, watched it reboot and start the install. Didn't bother watching the process and when I looked back it was a black screen. Thought it timed out after a (possible) reboot so went to wake it and nothing. Will not power on or boot into fastboot and plugging it into the charger produces nothing on the screen.
Ordered it direct from Google Play so called their support, explained all I had done and after an hour of being put on and off hold I got disconnected. Tried calling back and after the prompts, the line drops. Guessing it was quitting time. The tech (if you can call him that) said he's got the 5.02 notice sitting on his N6 but from what he's heard, he's sticking with 5.01 for now as he has no issues.
I wanted to give you the full convo even though most of it's useless.
Oh, as far as the tech goes, he wanted to resolve it in one call and tried talking to Motorola but said his call was dropped and after trying to call back he got an After Hours message. Before that he wanted to send me a shipping label for me to send it back but wouldn't send a replacement until they got it back. He was going to talk to his supervisor about sending one out overnight... That's when the call dropped. I was very polite but after waiting since October and checking everyday, now I'm pissed.
Thoughts?
TIA
These phones dont get shipped out fully charged.
What was your battery level? If it was upgrading and it loss power due to lack of it, congratulations for bricking yourself.
You should always charge up a device like a cell phone before flashing.
Can you charge it up now? Give it some juice and see if you can at least get into the bootloader.
It was at 51%. No activity when plugged into the charger as I said in my OP.
xwera43 said:
It was at 51%. No activity when plugged into the charger as I said in my OP.
Click to expand...
Click to collapse
Man sorry to hear. I didnt even take the update. the day I recieved my device I unlocked the bootloader, flashed custom recovery and then cm12 nightly
I have a new replacement coming. Thanks for the input.
X
Yes, if you got it through Play ONLY deal with Play, Motorola is the WORST. I really never want to deal with their support again.

HELP! SEANDROID and FRP Issues.

I realize this has been mentioned before but, I couldn't find a solid answer specific to my problem.
As it currently stands, my Note 5 bootloops or so it seems with the SEANDROID and FRP Binary errors appearing with the Note 5 logo, and fade to black. Rinse, repeat.
I'll back up a little bit, my friend got me a Note 5 on his plan with Bell last November. After just 30 days he was fed up with the service and went to epic ends to cancel and return both his phone and mine, of course this didn't work. So, after a litany of calls and driving to different stores for various credits. He effectively was left with our phones and a bill total of around $800 after everything said and done. Somewhere in this mix though Bell, decided or someone he was laying into to blacklist both his phone and my beloved Note 5.
I was using the phone for work at the time and suddenly it didn't work!? So he told me his wasn't working either and alas we set off to figure out some circumvention around this, which ended up with some nerdy guy in a Tim Horton's changing the IMEI's of my Note 5, which had it's own issues itself.
First we had to root the phone, then he used an octoplus box to unlock it and pop another IMEI in there. I remember after the rooting portion though he had me remove my fingerprint, my google account and my samsung account. This was back in mid December. I, yesterday after all this time finally began to re-add my accounts. I added my google account and fell asleep after a old friend stopped by and smoked me up on a spliff which I haven't touched in years. For obvious reasons, I passed out to wake up to my phone dead, so I plug it in and BOOM I have the above errors popping up above my logo. For note though, the one error "SEANDROID" was present after the IMEI change. Now, I'm just bootlooping. I did read that I can flash a different kernel or another ROM, my biggest issue is I have client's files stored on my phone along with a bunch of sexy pictures of my girlfriend
So, I ask my fellow XDAer's what steps can I take to remedy this without losing my internal storage.
A happy footnote more to those that may think I'm a wily thief or some petty criminal looking to break a code or do something illegal with the phone. I am not and in an ironic twist my friend the account holder actually got both phones off the blacklist after yet another tear into Bell. Doesn't help me now but, it does show that had I waited I wouldn't have been in this predicament or even had a reason to go onto Kijiji and find a seedy IMEI guy.
Thanks anyone for reading this entirely too long post and I appreciate any help!
More info:
Galaxy Note 5
Bell - Unlocked
Android 5.1.1 - I never updated it if that helps.
Just flash stock rom on it. It happens when someones tried to root it without turning oem unlock on
---------- Post added at 07:07 PM ---------- Previous post was at 07:06 PM ----------
It wont touch your data partition.

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

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!

Categories

Resources