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
Related
I successfully rooted my phone using this method:
http://forum.xda-developers.com/showthread.php?t=2130276
Then I tried the following method to modify multi-window on the phone:
http://www.andromods.com/tips-trick/verizon-galaxy-note-2-adding-all-apps-to-multi-window-bar.html
And ran into this problem on this step:
4. Copy and replace “FlashBarService.odex” to “/system/app” folder, as well as “services.odex” to “/system/framework” folder. If you have difficulty to replace services.odex, reboot your device. In case you experiencing bootloop after replacing services.odex, then you need to pull out and reinsert the battery, if the bootloops remains, just flash the root image with ODIN to fix it.
PROBLEM: THE PHONE FROZE. THEN WHEN I REMOVED AND RE-INSTALLED THE BATTERY AND TURNED IT ON, IT LOADS UNTIL THE 4GLTE SCREEN AND REMAINS THERE INDEFINITELY.
- I did what it directs to do with the battery but it didn't work.
- I don't know what it means to "flash the root image with ODIN"
I've tried this to fix it:
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
and I believe maybe another thing with odin. Odin usually fails, maybe it's just my USB drive. But i have no idea what to do, or what to even look up to learn how to fix it because I don't know what my problem is called.
Can anybody help me by giving me a method to use or steps to follow or some information?
Try this
http://forum.xda-developers.com/showthread.php?t=2040264
It is called a boot loop by the way
God bless the American people.
barrackOBAMA said:
It is called a boot loop by the way
Click to expand...
Click to collapse
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Milimbar said:
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Click to expand...
Click to collapse
That's right, you understand. and perhaps I just don't know what it means but, I don't think it "freezes" on the 4GLTE screen, it loads until that screen and then continues to be animate, rings appearing and disappearing, loading indefinitely. I don't know if that's anything different, but just in case that clarifies anything.
and I tried http://forum.xda-developers.com/show....php?t=2040264 but to no avail. it always fails @ or immediately after the RECOVERY step.
Any ideas?
I have a problem with one of my Lenovo A830 phones.
I bought it from Etotalk, so it came rooted, and with their custom version of the Lenovo Stock ROM and their custom version of CWM 5.5 installed.
I tried formatting my SD card and then doing a factory data reset from within the operating system. (I was intending to install MIUI V5 after rebooting into recovery).
However, on rebooting, the device is now caught in an infinite boot loop, and I am not able to boot into recovery mode (by holding down power and both volume keys). It loads the initial splash screen, then shows a few seconds of the Android character and some whirring cogs before rebooting.
I am able to boot into Factory mode (power and volume up) or Meta mode (power and volume down). Factory mode has a number of options, but they are all in Chinese characters, which I am unfortunately not able to read.
I did notice that my SD card seemed to be write protected when I tried to format it in my computer and to copy on the new ROM - I solved this by putting it in a different phone and reformatting it. I wonder whether the factory reset process has write protected something it shouldn't have?
Does anyone know how I might best proceed? I've been digging around on the forums, and tried a few things, but there's nothing which seems to provide a coherent solution for this problem.
I've got the latest Android SDK Tools, MTK Droid Tools 2.4.8, SP Flash Tool 3.1312, some additional ADB drivers (120827 v3.7) that I'm not sure how to install, the latest MIUI V5 ROM (3.8.16), and the latest stock Lenovo ROM (S118 from Need A ROM, just in case I need it).
Maybe different SP Flash Tools version?
I had trouble using SP Flash Tools v3.1312 with A830. Once I switched to v3.1304.0.119 I was able to flash both the original ROM and the custom MIUI one without serious issues. I'm unable to post the download link but google it.
One other thing is that when connecting the phone, it usually loads the something something Preloader driver, which is no good (even if it gives you Download OK). When attempting to flash either ROM, try pressing both the power and volume up buttons while connecting the phone (after pressing Download), only way it worked for me.
Good luck!
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
tominglis said:
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
Click to expand...
Click to collapse
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
claudiuionel said:
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
Click to expand...
Click to collapse
Hi I had similar "reboot loop" problem this morning after a phone factory reset.
I have no idea how I solved that but the following was the steps I tried:
1. Install the MTK6589_PdaNET_ADB_VCOM_Drivers. Skip the USB connection during setup. Start the PdaNET after setup finished.
2. Insert battery inside the phone and connect the phone with the computer by USB
In my case, the phone reboot loop once, and the lenovo screen appeared in the second restart. The phone hanged. I unplugged the cable, took out the battery, insert the battery again and start the phone normally again and it is working now.
I recommend installing the recovery rom after you have fixed the phone.
Goodluck
Hello,
I have a big problem with the I9300 from my mother-of-law.
Her Galaxy is neither modified, nor rooted or anything. So it's stilll stock.
Now her I9300 won't boot correctly anymore.
When she starts it, it lasts much longer than normal to boot. When unlocking, an error message pops up immediately "Application Installer stopped" (angehalten), when clicking ok, it comes another time then it reboots completely.
When going into "Android system recovery" and wiping data/factory reset, there still comes an error message when I reboot (error) and the same procedure appears.
> It lasts a long time to boot > after unlocking the error message appears (Application installer stopped and it reboots immediately).
Does anyone have an idea what the issue might be and what I could do?
Flash a new Rom?
(P.S. sometimes it doesn't start at all an just shuts down and the battery is empty - even though it was still 77%).
Edit:
Sorry, I made a data / f factory reset another time and now it finally seems to work, unfortunately with all datas erased..
You should flash newest firmware for your country via Odin and it should work correctly
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
First of all, I don't know where to post this thread. Please redirect me if this thread is not for here thanks.
Hi, Im having serious problem with my Samsung S7 phone. what happen was I was trying to install root on my phone, but my TWRP cant find my Internal storage. so I try to search on youtube how. then I saw repairing/formatting the data to exFat/ext4 or something. I did the steps but it shows error while formatting the data and its still on formatting process so there is no any back buttons or anything to cancel it. It take like 10mins on formatting process that keep showing errors so I did turn off my phone.
After that I turned on my phone. TWRP logo shows up and it stays there. It wont go to the main menu of twrp. I cant even turn off my phone after that. if I do the volume down + power, it will just reset to twrp logo. I cant make it turn off so I can go to download mode or safe mode to factory reset coz it doesnt accept any buttons except if I reset the phone [by pressing volume down+power] which directs me to TWRP logo.
Only way to completely turn off is to drain the battery. If I charge it, it automatically opens and lead to the TWRP logo again at get stuck.