Hi,
I was using nameless ROM on my TAB. I think it was 4.4.2. I have decided to try ART runtime, so I have removed Xposed Framework, switched to ART and restarted my TAB, it booted fine and showed "Android is upgrading" message so I left the TAB to start.
When I picked it up later I was "black screen only", I thought that battery driained out so I have connected it to charger but nothing happened, so i left if for a few days suspecting I has frozen so I can't unlock it/shut it down.
Right now after a week it's still "black", doesn't respond to connecting charger (I have tried 2).
I also tried to shut it down by pressing power button for 10 seconds but it didn't help either.
What I should try next?
What are the chances that perfectly working tab has died because of ART runtime, I though that bootloop it the worst scenario as system partition can be damaged only while flashing.
Is it possible that the TAB is bricked?
I can also add that I have previously tested ART with Omni ROM but a few apps that I used FC then...
Can you boot into recovery? If so, you can revert back to dalvik using this flashable zip from here: http://forum.xda-developers.com/showthread.php?t=2707841
No, it doesn't power-up at all. Looks like phone with no battery.
Then I have no clue. Never tried ART on my tab before because of Xposed. The one time I tried most of my apps kept FC-ing then I went back to dalvik. But you have to find a way to get your tab into recovery, then you can flash that zip.
Related
A couple of nights ago, I accidentally let my phone die. It must have been doing something important, because I kept getting force closes on all stock apps and also apps that required root including superuser. I rebooted to see if that fixed the problem but it didn't boot up after, I figured it wouldn't be a problem and deleted my cache and dalvik and rebooted. The phone booted to the lockscreen saying "Upgrading android, Optimizing x of x applications" but I noticed that when it got to the 33rd app, it would suddenly go very fast and the phone would crash to the boot animation (not the boot logo) on "starting applications". It wouldn't boot back up until I did a hard reboot. After a while, I realized it wasn't going to fix itself and just wiped and re flashed everything. I did restore some user apps in tb and everything was fine. On the next day, i made sure that the battery didn't die but i woke up to the same force closes and bootloop when i rebooted. Tried to delete cache and dalvik again to see if i could reproduce the problem but now it wont boot past the animation at all.
Im using siyah 3.2.7.2 and my second rom (which boots fine) is Pure ics
EDIT: On 3.3.1 now, doesn't make a difference
Device: Galaxy Player 5.0 INTL (YP-G70)
ROM: Cyanogenmod 10.1 (7/23/2013)
Kernel: Sultan r5 INTL
Problem: The battery appears to be malfunctioning somehow. After using "Pimp My Rom" and enabling some tweaks, the device began to randomly turn off and loop on and off with a white battery outline onscreen. Now, the battery has sufficient charge. When it finally turns on, it's always over seventy percent. When it does turn on, if it is plugged in on the wall charger, it immediately turns off upon disconnecting this wall charger. Also, it displays "Android is upgrading, starting apps" at every boot. Managing to turn on the device after doing a reboot with the power button many times takes up to 15 minutes. It sucks. ):
Steps attempted:
Reflashing ROM and kernel using exact steps (wiping all data, /system, cache, etc.).
Flashing Cyanogenmod 10.2 (8/05/2013) with Sultan r6.
Deleting battery stats.
Cleaning charger and microUSB port.
Rechanging tweaks to the values I remember in Pimp My Rom. (IDK about all of them, if someone could post the defaults that would be great).
Draining battery (I did to 1%) and then recharging. Should I drain until it turns off?
[EDIT]: Tried flashing to Chip v1.5 with r14 kernel. No luck; it is just a different battery icon.
[EDIT]: Tried flashing to stock with Odin.
Are there any steps that I could possibly take to fix this? Perhaps flash to stock and see if the problem persists?
[WORKAROUND!] I've found a workaround, however annoying it may be. Plug in the YP-G70 and it should bootloop with the battery icon. However, as the icon disappears and the screen is black for about a second, just before it is about to reboot with the icon, pull the charger from the device. This has guaranteed my device to start every time; I can't ensure that it will work for you, but it is worth a try.
Please help!
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Click to expand...
Click to collapse
I have done many factory resets from CWM. Would flashing back to stock do anything that flashing another rom wouldn't?
Also, after scouring xda for answers, I saw iurnait recommended draining the battery until the device turns off. I'm going to try that I suppose.
I'd flash back to stock if that doesn't work
Sent from my YP-G1 using xda app-developers app
Unfortunately, flashing to stock using Odin didn't remove the problem.
I used a guide from androidromupdate
To be honest, I've given up. I'll update the original post with what I've tried and the workaround that I've found for this dreadful issue. If anyone else has this issue, best of luck!
I've got the same "boot loop with battery logo" problem, but without the random shutdowns are "android is upgrading" message on boot.
Some additional details:
I can boot into download mode without any trouble.
It will occasionally complete a boot, but gets stuck in the loop as soon as something causes it to reboot or shutdown.
I can sometimes boot into recovery mode. It will successfully go into recovery mode about 2-3 times before it will go into a normal boot.
Flashing alternate kernels (even going all the way back to stock) just changes the battery logo, but does not stop the bootlooping problem
The stock kernel was far more reliable than the others, often booting all the way after only 3 or 4 tries.
Throughout the boot loop, the battery logo (except in the stock kernel) will show as empty, even after being charged overnight
Upon a successful boot (all the way to android home screen), the battery is shown as fully charged (if it's been charging) or a level that seems probable (e.g. it'll show as 70-80% if it's been in download mode (which keeps screen on at full brightness) for a while or left to bootloop for close to an hour.
If it's not plugged into a charger, it only loops once each time you turn it on (i.e. battery logo shows for a few seconds then the device shuts itself off).
An update to Joseph's posted workaround:
I've found the button lights a perfect indicator for the timing. Wait for them to go black and then come back on very dimly then unplug the cable before the screen shows anything or the key lights go full brightness (like they are when device is fully booted and awake).
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
ampeme12 said:
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
Click to expand...
Click to collapse
Tried wiping cache and dalvik cache in recovery?
Christiaan91 said:
Tried wiping cache and dalvik cache in recovery?
Click to expand...
Click to collapse
Haven't tried that but I will give it a go mate
My Rooted Nexus 7 was working perfectly. Now I am not sure If it is Soft Bricked or something else is wrong with it, It was charging one day and I took it off one micro usb charger and put it on another Nexus 7 charger. I went back and turned it on, Now it was stuck in bootloop, I have seen bootloops before, but not like this. It turns on and goes to the lock screen, then after a few second it freezes then restarts. I have been able to quickly log in boot into safe mode but it still freezes and restarts, I made it to the app menu once and then it sad , Unfortunately Launcher has stopped, I have cleared the cache and dalvik cache and nothing works, I have bootloader version 4.1.3 and CWM version 6.0.1.9, I have tried to format tablet and factory reset with cwm recovery but when I turn it back on I still see my stuff and I still reboots, I have tried to restore from a backup from a while ago with cwm but it fails. I tried to use nexus toolkit but I dont remember my version and I cant check, I gave it a guess but It can not find my device when plugged in, even in recovery mode, It said something about fastboot but i think i did that but I am not 100% sure what it is, I need to get this workig again fast.
Okay, here's the situation. I was playing Minecraft PE on a server. While I was playing, all of a sudden, my tab stopped working and froze. Then I reset (power button >5 seconds) the tab. After that, I was stuck on the splash screen (shows Samsung Galaxy Tab 10.1). But I did set the settings to not show the boot animation during boot (this was a long time ago). I left it there for 2 hours++ and nothing happened. I even left it to drain until it shut down itself. I did a full charge, not working. I took out the battery overnight, not working. Only CWM recovery works. I tried to backup, but then was stuck on SettingsProvider.apk. I cleared cache and dalvik, not working. I didn't factory reset though as I will lose the entire Rom itself. I tried to sideload the rom on my pc, but Windows shows USB not recognized etc. I also tried going into download mode, but then same thing, windows does not recognize it. In ODIN, nothing shows up. I suspect a faulty cable, so I'll buy a new one. However, that couldn't make it bootloop in the first place. So I need help for this.. It has been almost a week. My ROM is SlimBean p4 20121211. Thanks in advance.