The sides of the screen are flashing blue whenever I get any message - it is really irritating. I had this issue earlier, and Xiaomi Service Center fixed it by some software upgrade. I have installed custom roms since then, and it went back to same state (currently I am on factory rom - MIUI).
Related
Hi,
I'm using a ROM firmware which did not come with the phone, but Kernel is stock. Recently having major issues and contemplating whether I should risk a factory reset or just flash a new ROM (risk bricking the phone) and hope it solves the following major (frequent) problems.
1- Jams randomly
2- doesn't come off sleep mode. Just a black screen and a green indicator light indicating that the phone still on.
3- Crashes
I don't know what to do. Any suggestions?
I'm using JZ054K.I9300XXELKC
Risk a factory reset begore trying anything else.
FS as said followed by a stock rom .
Fails then its a service repair
I'm trying to install the DK Zen RLS2 ROM here:
http://forum.xda-developers.com/showthread.php?t=2309928
I figured they wouldn't want me mucking the thread up with my personal problems.
What happens when I install the ROM is that it will start up and get as far as the lock screen. Instead of going into the whole new-phone-setup business, it just stays on the lock screen and doesn't respond to any touch input. I can turn the screen on and off with the power button and I can change the volume, but I can't unlock, pull down the status bar, or open the volume settings. Holding the power button won't bring up the power menu (no real surprise) but it will reboot the phone after 10 seconds.
I'm fairly certain I've used this ROM before, but I recently formatted my phone and relocked it and everything in an attempt to fix other issues. I'm able to use other ROMs just fine without getting this issue. So far I've tried Stock with Goodies (http://forum.xda-developers.com/showthread.php?t=2301672) and SuperBLUE (http://forum.xda-developers.com/showthread.php?t=2520499). It seems, from reading the threads, that each of these ROMs is based on 4.3, but considering the way DK Zen rearranges my SD card, I have a feeling it's different (it adds the "0" folders; does that mean that it's a downgrade from or an upgrade to 4.3?).
Any thoughts? The one thing I can see from this ROM is that it gives me a full 4G signal, whereas the other ROMs only get me a few bars. Maybe the ROM isn't being honest, but if it is I'd really like to get it working for this alone (also volume rocker to skip tracks).
Reading through this thread (http://forum.xda-developers.com/showthread.php?t=2470569) it sounds like going with a 1.31 firmware (which DK Zen is based on) will have touchscreen issues if my phone's firmware doesn't match. Checking the Bootloader screen, I have 3.04.651.2 on the OS line. Is that the cause of my problems? Is it possible to downgrade my firmware, and would that be advisable anyway?
I feel like not many people run into this issue, or if they do they already know why, but I might as well post what I did here.
The touch panel firmware in 3.04 isn't compatible with earlier ROMs (or at least 1.31 ROMs). So, I had to go back to an older firmware. To do that, I just used Rum Runner to get s-off which I hadn't done at any point before. That was a very simple process, though I couldn't do it on my work computer, probably because of all the server and network security software that's installed here.
Once I got s-off, I was able to flash a 1.29 firmware using fastboot. From there, I flashed the DK Zen ROM that I was looking at and the touchscreen worked just fine.
Yay for learning!
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
So, to give some perspective my note 5 was working perfectly fine for a few weeks until out of nowhere i started getting this "Google Services have stopped" message every 30 minutes or so . I noticed that i wasnt getting any notifications either until i restarted my phone. So i decided to install a new clean room without all of the samsung bloatware. But i wanted to make a backup using smart switch so to my surprise as soon i plugged my phone in it allowed me to download the 6.0 marshmallow update and it worked fine...except the google services message + notification problem was still there . So
I went in fine and installed the clockwork recovery but of course, after this was done my phone would get stuck on the samsung logo forever, Since i dident even had a chance to copy the rom, i had to go all the way back. Download a stock firmware and flash that trough odin.. finally my phone was working again but now it wouldnt let me update trough smart switch ( says im on the latest version alredy )
The firmware i used is this
http://forum.xda-developers.com/note5/general/guide-update-note-5-sm-n920c-to-android-t3317984
Since updating to that firmware i also noticed that my perfomance and battery life is much worse, As well on the download mode i have the Knox flag as 1, i dont know if this has any impact on the smart switch software
Basically i just want to go back to the marshmallow update that i got trough smart switch since it also included the spanish language pack that i really need
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.