Galaxy Note is freaking out! (solved) (dirty usb port) - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

It started yesterday. My Note is opening car mode itself and then turning it off and also some other programs. While it's happening i can't do anything with my phone. Then it stops the phone is ok for some time. It's very fast between swaping to car mode and back to desktop like few times a second. I have ISC Stunner 1.4.26.1v. on so my phone is using a bad kernel but everything was alright till yesterday. I've wiped galaxy but it 'didn't help. Is it emmc is broken or it's just a virus?

bulla666 said:
It started yesterday. My Note is opening car mode itself and then turning it off and also some other programs. While it's happening i can't do anything with my phone. Then it stops the phone is ok for some time. It's very fast between swaping to car mode and back to desktop like few times a second. I have ISC Stunner 1.4.26.1v. on so my phone is using a bad kernel but everything was alright till yesterday. I've wiped galaxy but it 'didn't help. Is it emmc is broken or it's just a virus?
Click to expand...
Click to collapse
You're lucky if you didn't brick.. Use mobile odin to flash Hydracore kernel.. After flashing Hydracore do all wipes and flash another rom....
Enviado desde mi GT-N7000 usando Tapatalk 2

May be also worth cleaning the usb port with some cotton buds and pure alcohol. I've heard this type of thing happening if contacts get crossed due to residue shorting the pins.
Sent from my GT-N7000 using xda app-developers app

Clean the USB connection
Go to the wiki on the note, look under troubleshooting, then for false usb connection. I had them add that after my little boo-boo.
Get a good powerful magnifying glass and look at the notes microUSB connector really close. It will be dirty, you can bank on that, but
what you really need to look for is contamination of the pins, especially the ones on the right side of the connector. Pull the battery, dip some
LINT/DEBRIS free cloth in pure alcohol, swab it clean. Let it sit for a few minutes and install the battery and see if that takes care of it.
It did for me...phone would just all of a sudden give the noise like it was connecting, and then the car mode would pop up on the screen, even
when not connected to anything.
bulla666 said:
It started yesterday. My Note is opening car mode itself and then turning it off and also some other programs. While it's happening i can't do anything with my phone. Then it stops the phone is ok for some time. It's very fast between swaping to car mode and back to desktop like few times a second. I have ISC Stunner 1.4.26.1v. on so my phone is using a bad kernel but everything was alright till yesterday. I've wiped galaxy but it 'didn't help. Is it emmc is broken or it's just a virus?
Click to expand...
Click to collapse

p51d007 said:
Go to the wiki on the note, look under troubleshooting, then for false usb connection. I had them add that after my little boo-boo.
Get a good powerful magnifying glass and look at the notes microUSB connector really close. It will be dirty, you can bank on that, but
what you really need to look for is contamination of the pins, especially the ones on the right side of the connector. Pull the battery, dip some
LINT/DEBRIS free cloth in pure alcohol, swab it clean. Let it sit for a few minutes and install the battery and see if that takes care of it.
It did for me...phone would just all of a sudden give the noise like it was connecting, and then the car mode would pop up on the screen, even
when not connected to anything.
Click to expand...
Click to collapse
Looks that you solved my problem. Cheers man!

bulla666 said:
Looks that you solved my problem. Cheers man!
Click to expand...
Click to collapse
Make sure you change your title "Solved" and highlight this post in your OP so it will help others. **See sticky about courtesy and responsibility**
Thanks!
Btw, may I ask why you are still using Stunner?

andreww88 said:
Make sure you change your title "Solved" and highlight this post in your OP so it will help others. **See sticky about courtesy and responsibility**
Thanks!
Btw, may I ask why you are still using Stunner?
Click to expand...
Click to collapse
Because i'm afraid of doing anything with my phone I don't want to get hard bricked.

Related

Help - screen shaking when touched!

My phone has been working perfectly with JM5 & samset v1.9f with CFlag fix v1.80.
Then the other day I noticed the screen was shaking slightly when I held my finger on the screen, as if it couldn't locate where my finger was correctly. Also it shakes alot more severely while it's charging.
Has anyone heard of this problem before? Could it be a software fault that reflashing firmware will fix, or is it a hardware fault.
Please help!
Sent from my GT-I9000 using XDA App
it's called haptic feedback
it's on by default, you can turn it off from Settings
is that what you mean? or it's something else?
Maybe it's the touch point itself which doesn't register correctly.
Are you using an aftermarket (non-Samsung) charger? I remember reading about someone else having trouble with the touchscreen going bonkers while he was charging the phone on a non-standard charger, which for a capacitive touchscreen might indicate some kind of electrical grounding issue, (edit: or maybe not (link)).
edit: Maybe you can try discharging the screen by wiping it with a soft cloth used for cleaning vinyl records.
I have only ever used the charger that came with the phone, and the usb that came with it to attach it to my laptop.
The problem still exists while it's not charging, it's just alot less severe.
I'm going to have to flash it to stock firmware and hope that fixes it. If not I'll have to send it out to be repaired.
I hate phones sometimes......
Sent from my GT-I9000 using XDA App
I should also add my screen is perfectly responsive, there are no dead zones.
It's as if the touch screen can't tell which part of my finger is touching the screen. For example; If I put my finger flat on the screen rather than the tip of my finger, it shakes alot more.
Sent from my GT-I9000 using XDA App
miki4242 said:
Maybe it's the touch point itself which doesn't register correctly.
Are you using an aftermarket (non-Samsung) charger? I remember reading about someone else having trouble with the touchscreen going bonkers while he was charging the phone on a non-standard charger, which for a capacitive touchscreen might indicate some kind of electrical grounding issue, (edit: or maybe not (link)).
edit: Maybe you can try discharging the screen by wiping it with a soft cloth used for cleaning vinyl records.
Click to expand...
Click to collapse
Thanks for your help, I read the link you posted, very helpful. Maybe the charger was faulty and that damaged my phone overnight?
I tried the charger at someone elses house and the increased screen shaking still occurred. But if I connect it to my laptop by usb, it reacts the same as when it's unplugged.
I will try wiping the screen with a vinyl cloth when I get home. It has got a screen protector on, but I can't imagine that affecting it.
Sent from my GT-I9000 using XDA App
definitely not the screen protector
i have one installed, and i don't experience those screen shakes you described.
I found this interesting thread about someone having very simular issues: http://www.droidforums.net/forum/te...tions/31237-please-help-droid-has-shakes.html
It hasn't helped in solving the problem, but at least I know I'm not alone with this issue.
Edit
After reading the post more carefully, it seems that this persons issue somehow fixed itself.
Perhaps the best thing to do is check if this issue is covered by warranty (so I can send it to be fixed at a later date if problem is still there) & see if mine fixes itself too...
Sent from my GT-I9000 using XDA App
i used to experience this on my HD2 and Milestone, i must say that the galaxy S'es touch sensor is one of the best and have very seldom experienced this problem.
Link to video example>http://www.youtube.com/watch?v=Z2jdw8F3hrs&feature=related
Qazz~ said:
i used to experience this on my HD2 and Milestone, i must say that the galaxy S'es touch sensor is one of the best and have very seldom experienced this problem.
Link to video example>http://www.youtube.com/watch?v=Z2jdw8F3hrs&feature=related
Click to expand...
Click to collapse
Yes my problem is simular to that, but it's only that bad when it's charging from the mains.
I'm going to flash to stock firmware tonight. If that doesn't sort it I'll take it to a t-mobile shop & see what they suggest.
Apparently I've got 2 years warranty so if it gets worse rather than 'fixing itself' I can always send it to be repaired. I just don't want them to give me a refurbished one, knowing my luck it will be full of dead pixels...
Sent from my GT-I9000 using XDA App
Sounds like something interfering with the contact between your finger and the screen, or faulty hardware. ( Screen protector, wet fingers. )
If you are reproducing increased troubles with charger than it may very well be faulty hardware.
I can also attest to the high quality of the Galaxy S's touch screen, it can track 5 points very accurately.
It's not the screen protector as it was working fine with it before Tuesday, when the problem started.
I'm going to flash the firmware tomorrow when I have time, if that doesn't fix it then it must be hardware. I'll report back.
Sent from my GT-I9000 using XDA App
Intersting...
Ok, I flashed JF3 and the problem was still present.
I went to a local T-Mobile shop & showed them the problem. They basically said the phone still functions correctly, and recommended to stick with it and possibly get it repaired if it gets worse at a later date, which I fully agree with as I could get a refurbished phone in a worse state.
I reinstalled JM5, samset v1.9f, and used the update.zip ext4 instead of Cflag fix. I notice for some reason the problem seems less severe, but that might just be imagining it.
Thanks to everyone who helped.
Sent from my GT-I9000 using XDA App
I'd take it to an official samsung service point. There's no way a phone salesman would have a friggin clue about whether or not that's safe. It might make your battery explode and blow your nuts off if theres some shortcircuit in the phone or something...
Sent from my personal Dis-organizer GT-I9000
i solve this problem
It is temperature problem cpu is heating use home air conditioning home system and Cold it down as posible remove skin and cases protectors. Underclock cpu
I am using a HD2 and I noticed this problem when the phone is plugged in with a laptop. With Wall Charger, it works fine.
open up
i had the same problem with another phone. i tried everything. after that i just turned phone off, get all screws out of the back side. i pressed all connectors and after that put the plastic on it, turn the screws back in and restarted my phone. now i never got the problem anymore
NOTE: if youre not sure about what youre doing, ask somebody who know he can!
Kind Regards,

New kernal and bootloaders

So will bootloader flashing be the norm with GB from now on out or just something because it's new and there will be a work around later. The only reason I ask is because I'm scared about an odin flashing right now due to the fact that my phone usb is acting weird because I have to wiggle my cable the right way to charge.
Sent from my GT-I9000 using XDA App
Nerz said:
So will bootloader flashing be the norm with GB from now on out or just something because it's new and there will be a work around later. The only reason I ask is because I'm scared about an odin flashing right now due to the fact that my phone usb is acting weird because I have to wiggle my cable the right way to charge.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
well you only have to flash the bootloaders once. but i see your fears if the cable is funky. good news is that it only takes about 1 second for that part of the flash, so if it happens to crash at that exact time you are very unlucky.
it may be possible to create a new kernel that works on the old bootloaders but dont expect it to come along any time soon. but if it does consider your self fortunate because it really runs good. come to think of it cm7 works on the old bootloaders so depending on what samsung did there is no logical reason a kernel cant be built with this in mind.
is it the stock samsung cable??
Yea. It's the stock cable, but my baby daughter sucked on it and I think partially corroded the terminals. I didn't know when it happened so I'm not sure if my phone terminals also got wet, so I'm worried about that too
Sent from my GT-I9000 using XDA App
terminals are copper
copper dont corrode with spit.
chewing wouldnt help though.
Its not that bad a process. just watch videos and follow instal instructions a listed. The new boot loaders work with all roms
Sent from my GT-I9000 using XDA Premium App
TRusselo said:
terminals are copper
copper dont corrode with spit.
chewing wouldnt help though.
Click to expand...
Click to collapse
I'm pretty sure it has some corrision because after it was harder to get a connection. And if it is anything like xbox, I know that got correded by my older son some years ago.
Sent from my GT-I9000 using XDA App
it may have spit residue on it making bad connection but trust me, those terminals wont corrode with spit. I know my metals, if anything get some 70% or better rubbing alcohol and clean the terminals with a folded paper towel

[Q] Did my phone brick itself?

I flashed Paranoid Android after wiping ARHD 10.2, everything installed perfectly, phone was working great until I was listening to Pandora and checking Facebook..then my SIM card became unreadable and I had to take it out and put it back in, when I turned my phone back on it had gone from 42 percent battery to 4 percent, then 2, then dead. I charged it for a little while before going out for dinner, I came home and it wouldn't turn on, and it won't charge now whatsoever.
What the ****?
Alright, this will sound silly but place the phone in front of a light so that the sensor picks it up then try to turn it on. Will have to hold the power button for a while but it should turn back on. Or, if it won't, also try booting into your hboot. Reason for this is so you can't accidently turn on your phone in your pocket or something like that. It's been a while since I read this, I could be wrong but this won't hurt your phone so just give it a try
Sent from my One using xda premium
g33mt4z said:
Alright, this will sound silly but place the phone in front of a light so that the sensor picks it up then try to turn it on. Will have to hold the power button for a while but it should turn back on. Or, if it won't, also try booting into your hboot. Reason for this is so you can't accidently turn on your phone in your pocket or something like that. It's been a while since I read this, I could be wrong but this won't hurt your phone so just give it a try
Sent from my One using xda premium
Click to expand...
Click to collapse
Light sensor trick didn't work. The phone won't even charge, let alone turn on.
I can't boot into recovery, nothing.
Have you tried a different charger, cable or wall port or all three?
TarekElsakka said:
Have you tried a different charger, cable or wall port or all three?
Click to expand...
Click to collapse
Yes, tried two chargers in two outlets along with USB only charging, none work. Both chargers worked this morning.
That happened to me today. Literally the exact same thing.
My solution:
Step 1. PANIC LIKE A MOTHA F******
Step 2. Contemplate spiking unibody sexiness into pavement because unibody is functionally retarded.
Step 3. Take a deep breath and remember why you love her...
Step 4. Hold down power button for 10 seconds or longer.
Step 5. Plug usb cable that came in your box into your device.
Step 6. Quit whimpering, people can hear you.
Step 7. Plug into PC. Watch for tiny red light at top of phone.
Step 8. Wait about 30 min.
Step 9. ??????
Step 10. PROFIT! !
Sent from my squash patch.
Followed your steps for 30 seconds of holding the power down, plugged in stock USB to phone, plugged into PC. Nothing. Black.
Sent HTC an e-mail, my phone shouldn't over-heat and brick while using Facebook and pandora and that's it. I'm about to swap this **** for a S4 and stop being a HTC fanboy. I'm upset.
Not every unit provided by manufacturer can be perfect. By the end of the day its electronics and something can go bad. If you feel s4 is better than get a s4. HTC One will be happy to leave you. I'm sorry for being rude and sarcastic but it is what it is.
Sent from my HTC One using xda app-developers app
You shouldn't quickly jump to conclusions in my opinion. Just get a replacement set and see how it goes. If it still has problems then you can go for S4 or whatever device is out there. Of course in the end it's your decision but I'm just saying that you shouldn't cloud your decision just because of one defective set.
Sent from my HTC One using Tapatalk 4 Beta
Bump, any other suggestions?
PapaRhino said:
Bump, any other suggestions?
Click to expand...
Click to collapse
Did you charge it overnight using the stock HTC charger and cable? That is about all I can thing of. Something in the ROM appears to have drained the battery flat, which is not normally possible.
This is device #4 that has died completely on a 10.1 rom
18th.abn said:
This is device #4 that has died completely on a 10.1 rom
Click to expand...
Click to collapse
Makes me wonder if they didn't do something to the safe charging capabilities, although I would think that stuff is in the hardware, not the ROM.
It seems if it was the base that's being used we would have a LOT of devices going down so can't really speculate the cause. I shouldn't have posted above in such a suggestive manner.
I don't imagine the rom would be stopping the phone from charging as the kernel etc is not loaded until after hboot, charging is dealt with well before this sequence in the boot process.
To be fair it sounds like a hardware failure, maybe an overheating issue, possible caused by the rom and many other factors but that's the risk you take flashing experimental 3rd party software to your device. I don't thing you will ever know, your not even getting a uart mode which to me says fried PCB..
Send it in for repair and play dumb
18th.abn said:
This is device #4 that has died completely on a 10.1 rom
Click to expand...
Click to collapse
Mine had the exact same too, using cm-10.1
Just overheated, drained dead and didnt want to turn on or charge anymore
Sent from my HTC One using xda premium
This is indicating that for the time being, there is something seriously wrong with 10.1 builds and it's dangerous to flash them...
It's a shame that the cause for the error cannot be found once the device is bricked...
Same with my phone. Using slimbean. Phone died and unfortunately htc said i installed 3rd party software and i need to pay the repairs.
I didnt know how they knew that i had a 3rd party software where my phone cant even charge or turn on
Sent from my HTC One using xda app-developers app
jadmask3rlm said:
Same with my phone. Using slimbean. Phone died and unfortunately htc said i installed 3rd party software and i need to pay the repairs.
I didnt know how they knew that i had a 3rd party software where my phone cant even charge or turn on
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You should raise that question with them to see if you can find out how they are getting the phone to turn on
MacHackz said:
You should raise that question with them to see if you can find out how they are getting the phone to turn on
Click to expand...
Click to collapse
I tried to ask them but they said they have somekind of hardware or software that can detect. Anyways im in a no win situation bec i knew all a long that if i flash 3rd party software its a goodbye to warranty
Sent from my HTC One using xda app-developers app

Wi-Fi MAC Address: Unavailable

Hello,
the problem I've with this phone is that the wi-fi wont turn on, either the bluetooth.
So I tried different roms, stock 2.3.5, and then cm10.1.2 stable, and the same issue.
The last thing I tried was a simple one-click odin installation consisting in a super wipe plus the installation of a stock 2.3.5 firmware.
And here I am, facing the same problem. Actually when I go to "about phone", status, then I see:
Wi-Fi MAC Address: Unavailable
Bluetooth Address: Unavailable
At this point it seems like this is a hardware problem, and for that reason is more than welcome an oppinion in the opposite way
dionieins said:
Hello,
the problem I've with this phone is that the wi-fi wont turn on, either the bluetooth.
So I tried different roms, stock 2.3.5, and then cm10.1.2 stable, and the same issue.
The last thing I tried was a simple one-click odin installation consisting in a super wipe plus the installation of a stock 2.3.5 firmware.
And here I am, facing the same problem. Actually when I go to "about phone", status, then I see:
Wi-Fi MAC Address: Unavailable
Bluetooth Address: Unavailable
At this point it seems like this is a hardware problem, and for that reason is more than welcome an oppinion in the opposite way
Click to expand...
Click to collapse
EDIT: nvm just saw your other post.
Sent from my SGH-I747 using xda app-developers app
Yeah... they nor bluetooth nor wi-fi can't be turned on, actually the wi-fi in menu in settings looks "bold", like you can't move the switch, you know what I mean?
what if my captivate was shipped with a generic non-original battery cover and that's the thing provoking this issue? I'm saying this because battery covers shoud have some little metallic things on the back that improves the wifi, gps and bluetooth, am I right?
dionieins said:
Yeah... they nor bluetooth nor wi-fi can't be turned on, actually the wi-fi in menu in settings looks "bold", like you can't move the switch, you know what I mean?
what if my captivate was shipped with a generic non-original battery cover and that's the thing provoking this issue? I'm saying this because battery covers shoud have some little metallic things on the back that improves the wifi, gps and bluetooth, am I right?
Click to expand...
Click to collapse
Actually, they should work whether you have the back on or off. I never saw that problem before you and the guy mentioned it in the 4 years I've had this phone. It's quite odd.
BWolf56 said:
Actually, they should work whether you have the back on or off. I never saw that problem before you and the guy mentioned it in the 4 years I've had this phone. It's quite odd.
Click to expand...
Click to collapse
Also I found this:
near to the screw that is close to the sd card slot, there should be a copper pin coming out from a tiny hole. Every Captivate has that tiny pin of copper, that should match with a white spot in the back of the battery cover.
Mine doesn't have that tiny pin; there is nothing but a tiny hole in that spot.
So this is what happen when youg get a refurbished Captivate on eBay these days...
dionieins said:
Also I found this:
near to the screw that is close to the sd card slot, there should be a copper pin coming out from a tiny hole. Every Captivate has that tiny pin of copper, that should match with a white spot in the back of the battery cover.
Mine doesn't have that tiny pin; there is nothing but a tiny hole in that spot.
So this is what happen when youg get a refurbished Captivate on eBay these days...
Click to expand...
Click to collapse
Perhaps that's your problem. There might be a way to replace it.
You can try contacting Josh @ mobiletechvideos.com on that if you can't find the necessary info.
BWolf56 said:
Perhaps that's your problem.
Click to expand...
Click to collapse
I don't think this pin is the problem. Unable to turn on <something> usually means the system did not recognize the module during boot process. As it was mentioned already, Wifi/Blutooth on Captivate works fine with back door removed. Missing part indicates the phone was disassembled and someone attempted to repair something.
Val D. said:
I don't think this pin is the problem. Unable to turn on usually means the system did not recognize the module during boot process. As it was mentioned already, Wifi/Blutooth on Captivate works fine with back door removed. Missing part indicates the phone was disassembled and someone attempted to repair something.
Click to expand...
Click to collapse
I remember reading a thread a year or so ago about a guy who replaced that pin after having problem with his cappy. He had done it by himself though.
I might be wrong but what you suggest would come from the modem and/or kernel which seems to work fine on every other phone that runs CM.
It's a shot in the dark but it's what we got for now if you check what the other guy has tried so far (in the other thread with the same problem). Could be a good idea to ask that other guy if his phone still has the metal golden pin.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
I might be wrong but what you suggest would come from the modem and/or kernel which seems to work fine on every other phone that runs CM.
Click to expand...
Click to collapse
I'm not sure either, not very familiar with phone software specifics. I'm a computer guy and in computers missing software controls means device not initialized. Kernel/modem software is fine, but there is something wrong with the hardware. I personally don't believe restoring the pin will fix the issue. On a good Captivate, even with this connection open (back cover removed), wifi/bluetooth works fine. A good repair guy have to take a look here and check all currents/voltages from SoC through amplifiers to antenna. Shooting in the dark is asking for more trouble. On the other hand there is no point to pay for shipping/repairs on a $90 device.
Val D. said:
I'm not sure either, not very familiar with phone software specifics. I'm a computer guy and in computers missing software controls means device not initialized. Kernel/modem software is fine, but there is something wrong with the hardware. I personally don't believe restoring the pin will fix the issue. On a good Captivate, even with this connection open (back cover removed), wifi/bluetooth works fine. A good repair guy have to take a look here and check all currents/voltages from SoC through amplifiers to antenna. Shooting in the dark is asking for more trouble. On the other hand there is no point to pay for shipping/repairs on a $90 device.
Click to expand...
Click to collapse
Good call.
OP, I believe your best chance is to try with mobiletechvideos or a electronic shop in your area.
If you ever find the problem/solution, please let us know so we can help others.
Sent from my SGH-I747 using xda app-developers app
Yes, I will! actually this thread had pointed out some interest, I'm saying this due to the over 200 visits it had in just a few days lol
Back to the topic, this phone definitely was disassembled because it was a refurbished unit bought from a big store on eBay.
This piece of.. hardware, cost me $89 by the way, and the only solution I got from the seller -as I'm overseas now and I can't ship it back without expending lots of money- was to get a refund for the half of the price...
So basically I got this $45 Captivate that only works for:
calls, sms, music, storage & camera
Still, I don't think that $45 is a good price of this piece of... hardware.
And yeah, now I'm convinced that the missing pin of copper it's not related to the wi-fi issue, actually that pins only exist to improve call reception as I was told by the seller.
Therefore, and after flashing many stock and non-stock roms through Odin & cwm respectively, I must conclude that this is a hardware issue.
So I'd like to know if any of you guys would drop me a link of a DIY for disassembling and replacing wi-fi hardware on a captivate, because I've another Captivate with a different issue: usb port broken, so I can take the good parts of both and create a fully working Captivate
let me know
peace
BWolf56 said:
Good call.
OP, I believe your best chance is to try with mobiletechvideos or a electronic shop in your area.
If you ever find the problem/solution, please let us know so we can help others.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
BT/WIFI main logic in inside SoC, can't replace it. There are few external components you may check, but you need oscilloscope, good voltmeter, some special tools and advanced electronics repair knowledge. DIY repair in home conditions is not possible. I can send you the repair manual, if you want. One thing you can do is to repair the USB port on the other Captivate. It is doable, but you still need some equipment like vacuum pump, precise soldering gun, solder wick, good flux, etc.
install this app (Blade Wifi Fix)

How to recover a hard bricked Nexus 6

I flashed Android N Preview as a secondary ROM using MultiROM, everything worked perfectly, no issues what so ever.
After a day when I was listening to music using Spotify the phone suddenly switched of abruptly with battery over 90%
Since then I couldn't able to switch on the phone again.
No bootloader, no Recovery, Its not booting at all. No response from the phone.
I think it is dead.
Changed the Battery to new one.
Not worked. No sign of anything.
When I plugged in the charger the LED light is on, but I don't think its charging phone is not warm while it is plugged in.
In fact it felt like so chill.
So, I don't know how to recover my phone.
BTW, the phone's bootloader unlocked, rooted stock ROM as the primary one.
Any help would be highly appreciated.
Thanks guys.
Did you try to press the power button for 15-20 seconds? That's a weird problem.
The same happened to me.,and my phone is stock and locked. Its bricked. Nothing we tried helped
Sent from my Nexus 9 using Tapatalk
how do you change the battery on a nexus 6?
kidhudi said:
how do you change the battery on a nexus 6?
Click to expand...
Click to collapse
the back plastic sheet is held on with adhesive, I would apply heat first then work it open with a tool like isesamo or maybe a thin credit card or guitar pick. underneath there are 20 torx iirc can't remember size and another plastic shell with many holes in it. this cover, the wireless charging coil, and battery are adhered together i think and there are two small rubber covers for the power button (top) and battery (bottom). remember to disconnect your ribbon cables and treat them carefully.
the real problem imo lies in reassembly. i have repaired many and never feel they are the same as they came from the factory mostly because the back cover doesn’t re-adhere well. invest in some quality 3m adhesive, even a pre cut if you can manage.
Yeah done everything I have in my power nothing works.
Asked service center to check they said the phone is dead.
To get it repaired it will cost 3500 for me, they said.
Damn it.
Don't know what to do.
Now they said that the motherboard is dead, I need to change it inorder to get it work again.
Is it possible like this kind of problem occurs?
I was in Android N listening to Spotify
Putting a pre release OS on a phone, especially using a hack like multi rom, was indeed a recipe for disaster..
I'm certain that your partitions somehow got corrupted, and that results in a un bootable phone
Hopefully, someone reading this thread, who is thinking about doing something suicidal like that will learn from your mistake, but your phone is toast, unless you can get it J-Tagged, which might not even be available for your N6
I've heard the term j-tag a lot before. What does that mean
mikeprius said:
I've heard the term j-tag a lot before. What does that mean
Click to expand...
Click to collapse
http://www.brickedmyphone.com/products/jtag-unbrick-service/
http://easy-jtag.com/
My phone is officially dead. Service center said that the motherboard is weak and is impossible to repair and only fix is to replace the whole motherboard to a newer one. That would cost me a lot like i could get a new for it and they even suggested me to exchange this phone to a newer one.
And now i got Nexus 6P and I love it so much.
But God i really miss my Nexus 6.
Thanks for the help and suggestion here.
Long live xda.
I couldn't resist to unlock bootloader. Flash multirom and stock root and xposed.
That's the heaven, i can't live without.
I have done it all after i opened the 6P from its box. Lol.
May be i am fastest one to do it.
Thanks xda and friends from it.
Sent from my Nexus 6P using XDA-Developers mobile app

Categories

Resources