Hello.
So my phone was working ok (CM7 nightly 64 i think, glitch v12) and today i got the dim bootloop for the first time in a long time. I can't find anything that tells me what causes it however.
So I pull the battery and reboot. Stuck at the spinning android on a skateboard but it doesn't restart, just spins forever.
I tried adb reboot into recovery and clear the cache/dalvik and fix permissions. Nothing
I tried reinstalling CM7, glitch and gapps. nothing.
Tried installing just cm7 and gapps. nothing.
Tried updating to latest nightly (73). Nothing.
So I check the logcat and it seems to rebuild caches and everything fine but it gets stuck trying to connect to wifi.
I tried blocking the device from my router but it still tried to connect.
I can see the log messages where it's constantly looping through trying to connect. Before I blocked it it would hang on the connect message. I don't have the message anymore but i believe it was something along the lines that it did connect but it didn't do anything else.
I noticed wifi problems before. Particularly how if wifi is enabled when i reboot, it cannot connect when it boots up unless i disable it and reenable it.
Any ideas of how to get my phone to boot?
This is the message I'm getting over and over again right now.
Code:
I/wpa_supplicant( 486): CTRL-EVENT-STATE-CHANGE id=-1 state=1 BSSID=00:00:00:0
V/WifiMonitor( 191): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=1 BSSID=00:00:
V/WifiStateTracker( 191): Changing supplicant state: SCANNING ==> INACTIVE
thanks.
Related
Ok, so I was trying to flash a custom recovery on my Optimus V and now i'm stuck on a blue screen that has the text
fastboot mode started
udc_start()
I'm at a lost as to how to fix it. Removing the battery and putting it back in just goes back to the same thing, plugging in the usb cord gives me
STALL GET_DESCRIPTOR 128 6 3840 0 5
and I can't find the device using ADB, however in my devices i can see an unspecified device called Android.
i also have the same problem it happened when i did a factory reset when it was rooted. i did a factory reset because just the internet browser would work on when i was off wifi but everything else di pandora, youtube, mail, ect.
i will let you know how to fix it when i do
[Q] HELP! Boot loop after running "ZT-180 Adhoc Switcher" App on Galaxy Gio GT-S5660M
in an attempt to get "adhoc" network support, I did the following
installed and ran "Smart Wifi Scanner" which recommended, and I installed some "Wifi Library" to support adhoc networks
it didn't work, so I uninstalled the library app.
installed and ran "ZT-180 Adhoc Switcher"
(the app requested root access, I granted it, then the system shutdown abruptly - i.e. immediately off, not normal shut down)
I turned the phone back on, and tried running the "ZT-180 Adhoc Switcher" app a second time.. again phone turned off instantly.
Now it boots up, system is fully running and loading home screen etc.
but then reboots after about 7 seconds, and just continues in this loop.
here is what I have done so far in an attempt to recover
using CWM, restored the following
- boot
- system
- cache
(I am trying to avoid the data, as I don't want to loose all the ondevice data)
I also tried CWM "Fix Permissions" which appears to just have crashed.
I also tried booting without SIM card
... at which point, the system loaded w/o my home screens or widgets configured, and complained about a bunch of apps crashing ... but otherwise loaded, until I tried to turn the WiFi on ... as which point -> back into boot loop
(note this is not the type of boot loop described else where, the system actually launches, but then reboots)
.... I would appear to have to do with the Wifi ... somehow broke it.
Reflash a new rom
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I'm having the exact same problem. Phone is soft reboot loop after installing ZT-180 Adhoc switcher. I have manged to get back on by switching to aeroplane mode (same as removing the sim card). But I am not able to fix it.
Opening the application again simply soft reboots the device again. Did you find any solution ?
Hi,
I still have an old v10.0 cyanogenmod on my i9300, a nightly build from August 2012, because there never has been a stable release.
Recently i have found my mobile (having only 2% power less) try to switch off, but it seems that it wasnt impossible for the OS to switch off and so it restarted without having power. Because it was in the night, I just found my mobile in the morning with a bootloop and no power. Even after pluggin the mobile to power and first charging to 100%, I still cannot switch it off. After switching off, it instantly reboots.
The worst problem is, that it is not able to boot. I only see the cyanogenmod boot logo rotating.
With the recovery mode I can access to both sd card and onboard storage. I have downloaded the aroma filemanager and have done an e2fsck with the onboard shell: no problems, everything is fine!
Have cleaned dalvik cache and cache partition: No changes in the behaviour.
Then I have updated the cyanogenmod OS to the latest 10.0 version: cm-10-20121214-NIGHTLY-i9300, but: no changes in the behaviour.
Then I have done an "adb logcat" bootlog, there is a loop caused by a fatal errror in the ActivitiyManager, after each fatal error there is a loop and the mobile tries another time to boot and the log nearly repeats. I have attached the part of that logfile, which repeats every time, means: after the last line of that log you can place the first line of that logfile, endless.
I don't want to upgrade to 10.1, 10.2 or 11, because I still have some important data like wechat and whatsapp msgs, game saves, and so on, which I dont want to lose.
Does someone has an idea, what I can try to do?
Big Thanks!
So my phone decided to do a hardware reset while I was at work and I'm now getting the Demigod Crash Handler screen after reboot.
I am stock rooted on 4.4.2 and did nothing unusual while on break before this happened.
The error was first "hardware reset." After booting into stock recovery and performing a regular reboot, the message is now "Apps Watchdog Bark."
I've looked all over for any ideas but there doesn't seem to be very much info.
Can anyone help?
gray1ify said:
So my phone decided to do a hardware reset while I was at work and I'm now getting the Demigod Crash Handler screen after reboot.
I am stock rooted on 4.4.2 and did nothing unusual while on break before this happened.
The error was first "hardware reset." After booting into stock recovery and performing a regular reboot, the message is now "Apps Watchdog Bark."
I've looked all over for any ideas but there doesn't seem to be very much info.
Can anyone help?
Click to expand...
Click to collapse
I think it's a kernel crash. Can you get into download mode so you can restore to stock? (Turn phone off, push and hold volume up while plugging USB cable into phone)
TOT Guide- http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
Hi, got a samsung J6 phone with android 8.0, non-rooted and no custom recovery, usb debug is enabled
It just froze when starting an app that always worked before, now there is a blackscreen, buttons doesn't do anything; power included, but the phone seem still on, and as a proof, he's detected by my PC, which won't happen when it's off, on my side at least, i tried to reboot it into recovery via adb, this error popped:
C:\android\platform-tools>adb reboot recovery
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
then i tried to kill the server, and it just hand there doing nothing too now.
C:\android\platform-tools>adb kill-server
_
i can't remove the battery nor i can open the phone without breaking it seem, so what should i do?
@Gess1t
The catch is that you must have root access on your device if you want to perform adb reboot recovery cmd
So basically, my phone is just unusable now? tried to call it with another phone, instantly not available, so well, guess i'll have to wait for the end of the quarantine to send it for repair, still have the warranty i believe . hope they just don't remove my internal data for no reason, cause if they do that my google auth i had there is gone forever.
but wouldn't the phone still work if it was just the screen?
After all the battery still receive power apparently and the phone seem to do be detected by my PC, so it seem it still on? or maybe it's still in that crashing state.
So i was right, it was in a certain freeze mod, after couple day, the battery seem to have emptied, as i knew it would happen, i then plugged it in one of my external fast-charge battery, screen showing battery, i can turn it on, and it seem to run normally, playing high graphic game seem to be just as fine as before. still weird tho, what happened?