Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)
Related
Has anyone ever ran into a situation where the UI locks up after a boot? I keep searching through threads and can't find anything. I'm not sure if it's something I have installed or if there is actually something wrong with the device. I had a nook previously and never encountered this problem but on the new one I just got (ebay refurb) the problem just keeps coming back.
Basically, it boots just fine and starts to show the Launcher but then the screen goes black and leaves the soft buttons at the bottom. The only way to recover is to shut it down and start it back up.
The funny thing is it doesn't do it all the time... sometimes it boots just fine and never locks up while in the OS... it's only on boot it does this.
I've tried multiple different versions of cm7 and am getting the same thing on all versions. I've tried different kernels and stock speeds and it still happens.
Any help or advice would be appreciated!
Hmmm... well after hours of troubleshooting I think I pinpointed it to beautiful widgets
Hi hello howdy!
I'm going to skip the foreplay cose the action here is pretty weird and you'll want to get right in, trust me.
I've a Galaxy S3 Mini GT-8190L, that reboots itself, after it has booted up, and I entered the sim pin and lock pattern I've from seconds to 5 min of grace before the phone restarts itself. I have tried two different batteries and the problem persists. I went and decided to rule out hardware problems (power bttn) and after some tinkering, ruled that out too. So now my best guess is firmware.
The phone is not rooted, does not have recovery mode installed, and is running stock 4.1.2 jelly bean with TouchWiz, no mods, no hack-y stuff, your old regular samsung s3 mini.
I tried installing CM11 with odin, and didn't work. But not because odin threw an error, no, that went on perfectly according to the program. But when the phone booted up, the rom was still stock, nothing changed, and it rebooted itself briefly. Weird. So then I thought "well, maybe at least the recovery mode is there now" since it supposedly was a package install. But no, when I tried to boot onto recovery the phone gets stucked on the boot screen with the samsung brand and model of the phone, and then restarts itself, this happens like four times and then the phone boots normally, the OS starts, everything loads and then goes on to restarting. So this was not a solution either.
Next I though, well lets just install the recovery, no, that didn't work, odin said that the install was successful but it was not. Tried with odin 3.04, .07 and .09, tried CW and TWR, neither of them load, as before, when trying to boot to recovery the phone displays the splash and the reboots itself like four times before starting up the OS.
Next I though well, lets try to root this thing, at this point I was just trying anything to see if anything sticked, but nothing, tried SuperOneClick, and no. Wanted to try TowelRoot but that uses an apk. I tried vRoot against my best judgement, but that didn't work, but not because of the reasons you might think, it did install, the phone managed to stay on for enough time for it to get running, but when it restarted, there was no app there, it was as if nothing was installed just a few second ago. I thought "huhh? That's really weird". So I went and did some testing on this matter.
It turns out that no matter what I do, I can install an app, delete 5 apps, change settings, and nothing sticks, when the phone restarts it goes back to the way it was, its like the phone lost the short memory and its like that Adam Sandler and Drew Barrymore's movie, 50 First Dates. The phone rollsback to the state it was when everything began.
I even tried to change something quick, and restart myself the phone to see if that would make the change stick, but no, that didn't work either.
So, I came up with a brilliant idea, look up a similar case on internet, 'cose you know, it has to have happened to someone else before me. But this is so weird that looking it up is a challenge by itself. I tried a few things here and there but nothing does it. So now I'm here writing my sci-fi story looking for some feedback on how can this story be ended without killing any of the characters, I want everyone to survive and work again. You know, happy endings.
Any ideas on what can be the problem? Seen anything like this before?
Hi all
I am not technical and am not really sure what to even call this issue, but have done numerous searches on this and other forums over a few weeks and am not able to find anything like it. I'm sure there must be, but because there is nothing onscreen to help identify the issue I don't know what to search for next.
I few weeks ago I got a message to upgrade the O/S. I didn't do it at work, as my reception there is pretty lousy. When I did do it I had good reception. When it had finished, it then wanted to install. I left it until the next day, when I was home again with a strong signal. It commenced installation but when it got to 91% it rebooted and started over again. This has been happening ever since and the only way to stop it is to remove the battery. I've tried leaving the battery out for several hours, draining it, and all the different kinds of reboots but nothing helps. I was able to get it into download mode, but then it got stuck in there. I was able to get it back to the other screen and don't know what to do now.
The only thing on the screen is a standing android guy with a blue polyhedron rotating in his belly, and an upload percentage. It always restarts at 91%.
I don't want to mess anything up, because this is a borrowed phone - after my previous two Nexus 4s chucked it in. I ended up having to send the first N4 back to Google and lost everything on the phone, but the other one has a lot of data I really want to keep, so I won't do that again.
Is anyone able to help me with this issue?
Altotude
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.
Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong.
So my story, I got a refurbished unit at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!
I'm in the same boat. Never had a problem before. Received my phone back from Samsung after a screen repair and now, doesnt matter what rom, kernel, patch, it always ends in random reboots. Most often when I'm scrolling or if a page is loading something in the background. It does a lot of hot reboots (not full shutdown and start ups) so its quick but infuriating. Tried everything, slowly losing my patience.
Any idea what it could be? Something related to Knox? Bootloader/Modem?
#3
Hello, I am too having the same problem. Even after a factory reset