Database Develop

[Q] New sort of N7000 brick

At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?

interesting, try to catch the evnts in the logs, use elixer/logcat/android tuner for that.

Check the battery dude.
I had similar problesm due to bad battery.
Phone was closing itslef. And before it closesi thescreen was turning crazy
Then no boot at all....

ardicli2000 said:
Check the battery dude.
I had similar problesm due to bad battery.
Click to expand...
Click to collapse
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?

JolyonS said:
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
Click to expand...
Click to collapse
I was outside when faced such a big problem. It was happening before like reboobs and stucks on logo. But after i took out the battery for 15 min I was able to boot the phone.
However, eventually, one day phone got stuck with a flickering screen and then it never booted. Tired nandroid restore. Did not help. Changed kernels etc. It was no good either. Then I changed battery. Did not work again Then made a factory reset. It worked. Using it without any problem now. But even at that time I was able to see my files in the phone via Qadb. This could be your case as well.
Try changing battery if it is older than 9 months. Make a full pit fresh Stock install.
Then Reboot. I hope t will work

JolyonS said:
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
Click to expand...
Click to collapse
Me too, i have some problem.

delete-

ardicli2000 said:
if it is older than 9 months.
Click to expand...
Click to collapse
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.

JolyonS said:
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
Click to expand...
Click to collapse
Glad to hear that problem is solved

[Q] Help: Phone locks up often...

Hi Guys,
I have a serious problem with my Inc S. Lately, after using a few apps (mainly on the bus) the phone will go to the lock screen. A this point when the power button to wake the phone, it will just hang. The backlights will still be on but the phone is unresponsive. I have pull the battery out for 10-15 mins before it will restart. This issue happens at least 2-3 times a day. I can see no reason why this would happen. I have tried a factory reset but nothing works. Any help to resolve would be greatly appreciated.

GiantP2 said:
Hi Guys,
I have a serious problem with my Inc S. Lately, after using a few apps (mainly on the bus) the phone will go to the lock screen. A this point when the power button to wake the phone, it will just hang. The backlights will still be on but the phone is unresponsive. I have pull the battery out for 10-15 mins before it will restart. This issue happens at least 2-3 times a day. I can see no reason why this would happen. I have tried a factory reset but nothing works. Any help to resolve would be greatly appreciated.
Click to expand...
Click to collapse
Telling us your issue is fine. However, we need more information such as your bootloader status as well as what ROM you are currently on (if you are of course)

I have unlocked the bootloader, cwm recovery, but still running stock Rom. Haven't flashed a new Rom as yet. The phone seems to get quite hot, too. I think overheating may be the problem as it won't turn on for 15 - 30 mins after battery has been pulled out, which suggests the phone would need that time to cool? Dunno, just a thought.
Sent from my HTC Incredible S using Tapatalk 2

GiantP2 said:
I have unlocked the bootloader, cwm recovery, but still running stock Rom. Haven't flashed a new Rom as yet. The phone seems to get quite hot, too. I think overheating may be the problem as it won't turn on for 15 - 30 mins after battery has been pulled out, which suggests the phone would need that time to cool? Dunno, just a thought.
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
Overheating is most likely your culprit. But its pretty difficult to pull the phone to about 50 degrees you really should watch whats running in your background and what applications you are running. Overheating may damage your phone and I assume you probably won't want that.

Would flashing a new Rom help? Never done it before.
Sent from my HTC Incredible S using Tapatalk 2

Ok, so when the screen blacks out, I can still receive sms. I have turned the screen time out to "never" (as it seems to only lock up when it goes to sleep mode), but it still blacks out after say 1/2 hour and screen becomes unresponsive. Have to pull battery out for a while. Is this a hardware issue rather than a software issue?

This still an ongoing issue, and driving me nuts. When ever the phone goes to the lock screen or after a phonecall, it wont come back on. The touch still works (can play music, etc by touching screen from memory) but the screen wont show anything. Have flashed cm7.2, done wipes, etc with no luck. Any help?

GiantP2 said:
This still an ongoing issue, and driving me nuts. When ever the phone goes to the lock screen or after a phonecall, it wont come back on. The touch still works (can play music, etc by touching screen from memory) but the screen wont show anything. Have flashed cm7.2, done wipes, etc with no luck. Any help?
Click to expand...
Click to collapse
Ok now that is not an overheating issue. That's probably a ROM issue or a kernel issue. I would suggest switching ROMs, maybe CyanVivoX or CyanVivo10.1 if AOSP is your thing. If not then maybe SVHD, Nik Project X Rebirth, or ViperVivo for Sense 4.1 (or Blackout or ARHD if you want Sense 3.6). Happy flashing

After a month of stuffing around and flashing my phone with different tons, I am still having the same problem. The only solution I have found is to install a wakelock app from the playstore, which isn't ideal as the screen stays on, drains battery and everything gets activated when the phone is in my pocket (mates are sick of getting phantom calls from me). The phone is no longer in warranty so I don't wanna take it to a tech.... There has to be a solution. Any further help woyl be greatly appreciated.
Sent from my HTC Incredible S using Tapatalk 4

[TROUBLESHOOTING] Unexpected shutdowns during calls

Hey guys,
I really love my phone, also the ROM (Chroma) so the kernel (Francos). but my phone keeps shutting down during calls. It's really not funny anymore and it's totally getting a pain now, since I have to keep a 2nd phone with me, just to be able to do calls (the hell is my Nexus 6 for?!). I've tried all I could, with a simple fresh ROM without Gapps, with Gapps, with and without my own apps (backed up with Titanium). Just the most annoying thing I've ever had with a phone, and somehow I can't really believe it could be a hardware issue. Or maybe it is, since it's only happening during calls? To be honest, it already happened once during a game.
I'm living in Germany, so I've a PlayStore N6, no carrier labels or so. Just a pure Google Shamu device.
Any suggestions? Any help? Just something to keep my phone working during calls, except of an replacement? Would really love to get that damn thing solved. :crying:

Noone replies? Did hope for some more help. :crying:
The most curious thing is that my phone just simply shuts down (at e.g. 80 % battery). At this moment I'm getting warned about my battery status and the phone shows that it's 0 % battery left. Here's actually what's kinda weird. After immediatly restarting the phone it shows again 80 % battery (sometimes 1 - 3 % less). Redialing again ends up only sometimes with the same procedure.
Since those shut downs don't happen while charging the phone I coudln't even manage to get a Logcat via Android sdk. At least I was able to get a full log with LogCat. So if ANYONE is capable of getting some information out of that log - Let me know, you'ld totally be my man.
Thanks so far and hopefully someone's going to read this and help me.

Rooted Nexus 6 inevitably results in bootloop

Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.

Rooted?
You mention in the title that the phone is rooted. To be able to discount hardware errors, have you tried flashing a factory image to set it back to stock? If the same problems continue, then I suggest that you return it to Google. I did this myself when the back of my N6 started to peel and the process was painless, since they send you the new phone before you return the old one, so you lose no airtime.

saraddictive said:
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Click to expand...
Click to collapse
Yes, as mentioned, flash a factory image to rule out any software issues. However, it is most likely hardware failure. Especially the camera fault. I've noticed this is becoming a rather common issue lately. So, you should probably RMA again.

Thanks guys. I was just concerned as I unlocked the bootloader and rooted the phone almost immediately after I got it. If I try to RMA it, they won't cry foul over a re-locked boot loader,will they?
Also,I have a feeling this might be an OTA that is acting up. It appears that loads of people have had issues after installing an ota (I did this before unlocking and rooting) so I'm going to try to flash a factory image. Thanks guys

Hello everyone,
as an update, I did exactly as dahawthorne and evolution_tech said, and re-flashed a factory image. However, i found it extremely strange that both my nexus 6s were experiencing the same issue so i did a little research.
Turns out, many users from 5.1 have been experiencing issues with changing their dpi in android 5.1 and above. Because I'm not all that familiar with build.prop and using adb shell (tried using it once, it wouldnt work properly so i just gave up), im not going to bother changing my dpi and it works all fine and good now.
To anyone else experiencing the same issue, check this page out: http://forum.xda-developers.com/nexus-6/general/dpi-conflicts-lmy47e-t3061261.
Cheers

Yep, well known issue.

Restarting in random moments. New rom needed?

Hello,
I am here because i have another problem with my lovely phone :/
You guys always helped me so i hope you will do it again.
Okay,
My phone is restarting in random moments. Screen is freeze for 1-2 seconds and then rebot. It is doesn't matter if phone is used hard (games) or if it's on the table.
1st time it happend with ROM 5.1.2. Then i've decided to go back to 4.1 rom and then automatic upgrade to 4.3.
Few days was okay and after then it starded again.
Does someone know why i have that issue??
I really hope that is only rom problem and if i change it the problem will gone.
And here's second part of thread.
What oryginal rom do you recomend? I have saw a lot of them but i have no idea what could i install.
Right now i have stock rom, i do not remember exactly number but i has "James Bond" music so i am sure it was one rom from that edition...
Edit:
If you find any better rom than stock 4.3 that is really stable i can take it as well
I jsut want my phone wokrks without any problems
Please, halp :fingers-crossed:

Try to run phone in a safe mode and see if the problem with restarting still exists.
I would suggest you to use this CM 12.1 rom it is working just great.

It could be a problem because i have no idea whenit will happen.
Now few days was great only today morning i saw that it restarted.
Hmm, for the first time restarts like this started with that rom... but i will give it another chance i think.

Then maybe an app are causing that random restarts or it may be a hardware problem. It even may be that sim card causing restarts, I have read something about it.
Btw I'm using that rom from the very first builds and I havent have any problems with phone restarts.

I had few restarts when sim card was loose but i have information that phone is restarting.
About app it's not the problem because even if i had no apps downloaded i had that problem
I hope i haven't destroyed my phone when i installed some roms. That would be bad.
For now i will try to instal CM 12 and i hope the problem will go away.
Edit.
And may it be just a battery problem?
Btw. I just did factory reset and already got few restarts, so i am sure it's not an app that causing the restart.

Okay i have watched that phone for a while and found new, fresh informations...
Even in a safemode phone cause to restart. It is no matter if i have a sim/sd card.
I also think it is getting hotter every restart but i am not sure about this.
When i was traveling by train it was restarting like a stupid... The phone was loosing signal and was changing to roaming etc.
I don't know if it has something with that...
After changing to android 5 few days was good and then...
Also that problem started in 1 day. Just started restarting, without any sympthoms.
Oh and 1 what is strange... After the restart when i touch the square (to cloose the apps) there are apps that i have been using before that restart.
Please, help :c
Edit. A hour ago the phone was restarting over and over, it turned on and sudently after homescreen loaded it restarted again. And that was for some time, now it is working without any issues for over 1 hour...
Edit. 2
After the night, and many restarts as well i saw that battery dropped. From 90% to 20%.
May it be just a battery problem and changing it will solve that?

I have the exact problem for 3 weeks now, the phone becomes screen off then randomly reboot and gets very hot.After reboot battery goes down like from 49% to 10%. My phone is just 2.5 years old and everything ia stock. In battery test it shows like battery health is normal. I also only use gsm+umts, mostly umts, Is there any solution for this?
---------- Post added at 05:57 AM ---------- Previous post was at 05:54 AM ----------
This first started when i travelled by train, then it happened like crazy when i am on sub way, now even happens when i am at home

Sucha a big forum and noone knows the answer, daamn :c
I am really thinking about changing battery right now.