Quantcast
Channel: xda-developers - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting
Viewing all articles
Browse latest Browse all 4112

[Q] New sort of N7000 brick

$
0
0
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?

Viewing all articles
Browse latest Browse all 4112

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>