Okay people, I've got a very ****ty situation with my N7 Wifi. I have multirom installed with stock 4.2.2 and AOKP JB-MR1 build 6. It won't react when I try to boot, and when I can boot it will hang on the Google bootlogo most of the time, but when it doesn't, and I boot into AOKP, it gives me the bootanimation, but then I get some sort of grey screen with horizontal bars. At first I thought my GPU might be fried, but when I boot into stock, everything works, except it turns off right after it boots because of an empty battery, even when my battery is full.
The device also doesn't show up in adb for some reason, not even when it's in bootloader.
If anybody has some sort of solution, answer, tip, hint, potato, that'd be great.
Related
Hi all
I've done something stupid to my phone.
Been fiddling with auto-brightness settings, and now the screen won't switch on.
Got CyanogenMod 7.1 stable for the HTC Desire HD, had it loaded for close to a month(been enjoying it).
I've rebooted, pulled battery, SD card, SIM, everything. On boot the display shows the HTC logo, and the CyanogenMod BootScreen, immediately after that, I see the screen off animation, where it would normally go to homescreen. I know the phone is still on, the notification light is flashing, and via USB I can get screenshots of my lockscreen(widgetlocker).
When I click the power button a few times, intervals of ~3 seconds, the screen flashes just quick enough to see my lockscreen, but it really is a split second flash.
I've got Juice Defender Beta, I think the latest, used it for a couple weeks. Today I wanted to test the auto brightness settings it "supports"(beta feature). I noticed no changes, so I skipped over to the custom display settings for cyanogenmod, under Settings/Cyanogen .../display/Auto Brightness.
I fiddled there, as I've so done before, couldn't find the right balance , so I left my phone for a bit, it clicked the screen off, now screen is 'stuck' off.
I understand that this may be Juice Defender's doing, but since I was fiddling with cyanogen settings too, I'm posting here and to JD support, just in case. There might be a conflict.
Anyone know how I would debug this through ADB? I would really like to disable auto-brightness, that would probably eliminate Cyanogen from causing this (as the settings I changed related to Auto-Bright).
I tried this, no luck.
Otherwise, how to reset Juice Defender settings via ADB, or through a USB screenview... thing?
I've got a NANDroid backup, but its a little dusty, I've done a lot of customisation and such since, I'd prefer to avoid using it.
This is, of course, urgent. I can't use my phone at all, so any help is greatly appreciated.
EDIT: Solved it. Booted into safe mode, disabled what I changed, sorted. Still no idea what caused it, but ja, I fixed it. Android has a safe mode? Good to know...
Hey guys,
I've done my homework and searched for similar topics as these but so far none came close to my solution (correct me if otherwise). Recently I flashed to this ROM
http://forum.xda-developers.com/showthread.php?t=1561705
from a stock ROM. Have done it a few times before and no problems have occurred. It's an MIUI rom and I decided to customize the theme a little. The themes section allows to change most of the detail ie fonts, status bar, home screen, lock screen, icons, boot animation.
And that's where it started, when I changed the boot animation, instead of using the default one. When I did a reboot after the switch, the usual boot logo was up, but then the screen turned pixelated like a CRT monitor/damaged LCD screen with colourful pixels. But then in boot into the new animation all fine, and has been ok since. The device boots fine, but I'm worried about that pixelated screen.
Is there anyway to fix this?
Please kindly advise Thanks!
anyone have any idea? x.x
You said it's been okay since? I wouldn't worry about it then. If you can't reproduce it, its not an issue.
RTContent said:
You said it's been okay since? I wouldn't worry about it then. If you can't reproduce it, its not an issue.
Click to expand...
Click to collapse
well the corrupted screen still appears, but im still able to use my phone.. just wanted to know if anyone found a work around this or encountered something similar.. care to share?
In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...
Hello, I have an i605 and have been using CM12 since it has been released and really like it as a daily driver. I have tried many different ROM's all using CM12 as a base and all, without question have had this same issue.
At least once a day (time of day varies) I will pick up my phone and turn on the screen (which button I use makes no difference) and it will be black, I see that the backlight is on but the screen is black. The home button does nothing, swiping left or right does nothing, the status bar shows up just fine, I can swipe down and see notifications and access the quick launch but if I try to access anything, it just returns me to a black screen. The only way I can get out of it is to reboot.
I am currently running the June 16 nightly with the kernel that is bundled with it. I did try a difference kernel before (I cannot think of the name right now) but the problem remained.
I have tried googling this issue to no avail and I haven't seen anything here on the forums.
Any help would be greatly appreciated.
Can you access to the recovery mod ?
Firstly I wanted to clarify one thing that my phone worked okay after the update. I didn't realise it has updated until after a boot loop.
Just FYI The camera in my phone have been crashing randomly when taking pics and the pics weren't having the full resolution. It was 1280x720. This wasn't an issue for me and I ignored it for like 3-4 months.
So my redmi note 10 have had some random reboot issues lately which i didn't give much attention to. It wasn't frequent just rare random reboots. Few days back I noticed my phone rebooting while in use and it started to loop for a few times and when it loaded into lockscreen right after unlocking, the power button started to press automatically triggering the power option screen and then the emergency calls as well. It stopped after a few taps on the power button.
A day or two later it rebooted once again while the recorder was on and and this time it boot looped a few times and showed the lockscreen and crashed booting back once again. A few tries after that it booted up and I was able to use it for another day.
The very next day, it did the same. Started to boot and loop once again. But this time when the battery is sufficient enough or the phones cool and haven't been used for a while, it boots into lockscreen but freezes and crashes. At one occasion, it stayed just a few more seconds long enough to open the passcode screen but crashes before I could type anything. Then it loops once again and before even reaching the lockscreen, boots back into MI Android Powered screen right after the three dots blinking page. And randomly it boots into lockscreen as well. But once the battery is down or the phone is heated enough, it barely goes into lockscreen.
Booting into safe mode also shows the same. It sometimes boots into lockscreen but doesn't show the 'safe mode' text in the bottom.
Right now when I had kept my phone off for a while it booted into lockscreen twice and the screen dims immediately before freezing and crashing.
The third time it just went back to the MI Android powered logo right after the three dots blinking screen.
Guys please let me know do you think this is a hardware issue or a corrupt software update?
I know software update issue can cause bootloop but does it reach till the lockscreen? My phone consistently gets into the lockscreen when the battery is sufficient or the phones cool enough.
What last update did you perform?
carlos974 said:
What last update did you perform?
Click to expand...
Click to collapse
MIUI 14 which i didn't even realise until I checked the settings app one day after a boot issue
What version do you have?
For me see screenshot, works fine!
Backup your data and clean flash with Mi Flash Tool, you can then exclude any software problem
This issue have been resolved.
The issue was the CPU couldn't handle the heat once the device turned on and would reboot right after reaching the lockscreen and loops.
Thank you for all your suggestions, though.
Dheerajvirgo said:
This issue have been resolved.
The issue was the CPU couldn't handle the heat once the device turned on and would reboot right after reaching the lockscreen and loops.
Thank you for all your suggestions, though.
Click to expand...
Click to collapse
May I know how did you fixed the issue? I'm stock with same situation as you. Did you change any hardware?
Hey, my mi 10 5g has similar symptoms - random restarts + random switch on power button without pressing it...
all this came after upgrade from miui 13 to 14..I use this phone for 1,5 yr with no problems...
Phone get hotter also...
Is it related to bug?