In developers options I decided to enable ART and it said it would reboot my phone. After that it said something about "upgrading android" and when it finished the phone rebooted again and now it's stuck on the Verizon Logo. I tried a battery pull but after booting it up it started to stall on the Verizon logo again. Help?
Got stuck for how long? Reboot again and then leave it alone for 5 minutes or more. Also, I'd leave the phone in Dalvik mode. Just my opinion.
Note 4
It's been like 30 minutes
Welp after holdng down battery down and power I rebooted into boot options, just selected normal boot it booted up, got past verizon screen, and did a small "upgrade" and now its booted Seems like S Health doesn't work with ART enabled tho so I had to remove my pedometer widget
i tried to switch to art. my note 4 got stuck trying to update the same number 96 app for 3 hours. did about 10 battery pulls and it rebooted and only got to the same number 96 app every time. had to do a full wipe from the recovery mode screen. good thing i had my data backed up to the pc.
---------- Post added 26th December 2014 at 12:35 AM ---------- Previous post was 25th December 2014 at 11:45 PM ----------
coltblue said:
i tried to switch to art. my note 4 got stuck trying to update the same number 96 app for 3 hours. did about 10 battery pulls and it rebooted and only got to the same number 96 app every time. had to do a full wipe from the recovery mode screen. good thing i had my data backed up to the pc.
Click to expand...
Click to collapse
tried it again after the full wipe and it worked. probably needs to be done from stock first.
Related
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?
Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
if you can get into cwm then try fastboot and flash the factory images from the boot screen
_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.
id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it
I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.
Yesterday, my phone started to freeze randomly. I would hit the wake button and nothing would happen, I would have to hold power for about 15s or remove the battery to reboot. The times between freezes got shorter and shorter until today when it would never make it to the OS. It would either go to a reboot loop or sit stuck with the Galaxy S III logo on screen.
I was able to boot into recovery, I wiped the Dalvik Cache and then rebooted. The phone got into the part where it updated apps but after waiting for than 20 minutes for it to update app 29 of 29, I pulled the battery and rebooted to recovery.
This time I wiped the normal cache and rebooted but it didn't make it to android.
I rebooted to recovery and did a factory reset, then rebooted. The phone powered off and would not power back on at all. The battery was at about 40% when this happened, I think. It was plugged in for the last 4 hours but it still won't start.
Is there anything I can do?
super6logan said:
Yesterday, my phone started to freeze randomly. I would hit the wake button and nothing would happen, I would have to hold power for about 15s or remove the battery to reboot. The times between freezes got shorter and shorter until today when it would never make it to the OS. It would either go to a reboot loop or sit stuck with the Galaxy S III logo on screen.
I was able to boot into recovery, I wiped the Dalvik Cache and then rebooted. The phone got into the part where it updated apps but after waiting for than 20 minutes for it to update app 29 of 29, I pulled the battery and rebooted to recovery.
This time I wiped the normal cache and rebooted but it didn't make it to android.
I rebooted to recovery and did a factory reset, then rebooted. The phone powered off and would not power back on at all. The battery was at about 40% when this happened, I think. It was plugged in for the last 4 hours but it still won't start.
Is there anything I can do?
Click to expand...
Click to collapse
Flash the stock firmware.
Can you get into download mode?
Sent from my SGH-T999 using Tapatalk
serio22 said:
Can you get into download mode?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
No, I even took it to someone with a USB jig. I've mailed it off to someone on ebay with a Riff box to see if they can fix it. In the mean time, I bought a Nexus 5 on craigslist and couldn't be happier.
So I just got a Zenfone 2 in the mail today, finally upgrading my phone after 2 years, except when I was running through the apps, I figured I'd install system updates.
Except it just loads up, tries to install it, 1/4th way through it freezes, then after a few minutes it resets itself.
I've tried to hard reset it by going to the bootloader menu but when I hit Recovery Mode, it resets back into system update loop
Edit - Nevermind, after hours of researching, I've learned the glory of fastboot and adb
That's normal. Stock recovery will always show installing update and then pop up an error message.
When the error Android bot shows, hold down power button and press volume up. Release both at the same time quickly. Do it right and the real recovery menu will show up.
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
Since your phone is still fresh and new and you shouldn't have any data you wanna keep on it, http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
Download the full firmware for latest stock ROM and update it through adb sideload in stock recovery.
Sindacait said:
Edit - Nevermind, after hours of researching, I've learned the glory of fastboot and adb
Click to expand...
Click to collapse
We have all been there... I modified my S2 years ago and the learning curve is impressive but fast.
For the Zenfone2 I also had to redo the whole fastboot/sideload yesterday after a failed update...
Hello there
I own Redmi 1s. I have been using the phone for nearly 2 years now. I currently had Cm 11 installed on my device. Today while using the phone, my phone shut down on its own. A few seconds later the MI logo showed up on the screen. It lasted there for a few seconds and then went off again. The same has been happening for over an hour now. The battery percentage before this happened was over 50 %. I have TWRP installed, i tried to open the recovery. The recovery opens up but the phone shuts down on its own within a second and the MI logo shows up again.
I can't figure out what to do. Please help me. Thanks
I removed the battery when I saw this problem. The moment I put the battery in, the phone starts up on its own. This is pretty different as the phone didn't start on its own when I used to remove the battery in previous cases. In this case it starts on its own and the MI logo keeps of appearing and disappearing.
If you can get into recovery, you might like to try clear cache and data or even a factory reset (means sacrifice all data) and see. If still keep restarting, might be time to flash back the stock ROM...
Yesterday, I scheduled my phone to update the new software at 2.00 A.M then left it charging. When I woke up, it was stuck on the Samsung rebooting logo. I can enter recovery mode.
Tried soft reset, wipe cache but doesn't open
I guess if I can update it manually via PC, it will be okay. But I don't know how to do it without losing my data. (I have very important photos and vidos)
I have never downloaded any unoriginal system update
cluczar said:
Yesterday, I scheduled my phone to update the new software at 2.00 A.M then left it charging. When I woke up, it was stuck on the Samsung rebooting logo. I can enter recovery mode.
Tried soft reset, wipe cache but doesn't open
I guess if I can update it manually via PC, it will be okay. But I don't know how to do it without losing my data. (I have very important photos and vidos)
I have never downloaded any unoriginal system update
Click to expand...
Click to collapse
Since you've never done it and you have very important data, ask someone who knows how to do it. You will need a single-file for odin.
Happened to my A225F when I updated to Android 13.
I pressed power button for about 30 seconds and it restarted. Went through optimizing applications screen and...voilá, came back to normal.
isn't that normal in samsung phones? I still can't believe people still choose that brand
moses_dx said:
isn't that normal in samsung phones? I still can't believe people still choose that brand
Click to expand...
Click to collapse
The brand doesn't matter. You need to be able to choose the right model.