I decided that I had enough with the charging issues on the 3.0 kernal. When i wiped system/cache/dalvik and then installed the stock rom, i wiped cache and Dalvik again, then rebooted.
I am not stuck at the point where the system boots up, I get to the main launcher, but it shortly has a series of crashes and force closes, and restarts.
I've been trying to recover with the stock rom again using the Kindle Fire Utility, but now am having no luck having the device recognized by the computer.
Any suggestions at this point?
There is one thing I do not see in your list of wipes factory/reset --- also did you flash it as update.zip or did you simply just flash the bin if you flashed the bin this is incorrect. If you didnt factory reset then restore is trying to handle the data you left behind.
Thepooch said:
There is one thing I do not see in your list of wipes factory/reset --- also did you flash it as update.zip or did you simply just flash the bin if you flashed the bin this is incorrect. If you didnt factory reset then restore is trying to handle the data you left behind.
Click to expand...
Click to collapse
I think i missed the factory reset. Anyway to "force" one I get as far as getting to it on the menu before it resets again...
Ok theres your key you must be very fast get there do it your fixed factory reset just keep trying might wanna keep it on the charger to avoid letting your battery die as this will only compound your problems.
---------- Post added at 05:03 PM ---------- Previous post was at 04:50 PM ----------
Also hold the power button down for 1 min and then power on you might gain the needed 2 or 3 seconds to finish the task
Related
Hey all, so I have a Stock Galaxy nexus running whatever the latest OTA update is that is stuck in the boot process right now at the "X" screen with the changing colors.
This is pretty much all I know about the situation:
I was sitting around with my phone next to me, decided to look to see if I had any messages, so I hit the power button to turn on the screen, nothing happened, so I pressed it a couple more times. Still nothing. Assuming the phone had frozen or something (although I haven't had any issued with this in the past) my instinct was to take out the battery and reboot it. After I did that it started to boot, showed the Google logo, moved on to the X screen and stayed there for about 15 minutes. I did some googling and people said it can occaisionally take a while to boot but after 20 minutes I figured there might be an issue so I once again took out the battery and tried again. This brought me right back to the same X screen and it's been sitting there for some 30 minutes now. Any suggestions or ideas of what's going on?
EDIT: I also just booted into recovery and tried clearing the cache, but that didn't really do anything.
EDIT2: I just wiped all my data through recovery and it booted fine. Is there anything I can do in the future to avoid having to start from scratch though?
Any help is appreciated.
Thanks for your time.
More details might evoke more replies. What did you do immediately before rebooting the device the first time it got stuck at the boot animation?
Same problem! Stuck at 'X' for infinite time ..
I have faced this problem second time now.
One of my friend who also has Galaxy Nexus faced this problem once!
Both of us have 4.1.1
When problem occurred ? -- (me both time)
I turned on Bluetooth using widget on homescreen, it halted for a second or two and suddenly 'X' logo appeared which didn't go away ! I tried taking off battery and turning on phone again. While starting it "Passed Google logo" and on next screen at "X" logo it stuck.
When problem occurred ? -- (my friend once)
While changing from flight mode to Normal mode.
to : Junior Member - OP
" I just wiped all my data through recovery and it booted fine." I have not done anything by myself yet, so don't know how to do that. can you please explain in detail ? It will really be helpful . Thanks ..
4.2.1 is the latest version, not 4.1.1.
Without any logs, it's that much harder to tell.
Sent from my i9250
Have you rooted your phone?If yes then head over to recovery=>then Clear cache partition=>factory reset=>advanced-clear dalvik cache
Then reboot..now your phone should work fine.
As per your problem stated you might have different rom and got OTA,which finally messed with your system and hence got bootloop..
my phone not rooted
hello,
If phone is not rooted, can I reach recovery mode and clear cache ?
Is there any other way to do this with not rooted phone? or can I root my phone in this condition?
---------- Post added at 09:42 AM ---------- Previous post was at 08:51 AM ----------
Also can to install yakju image freshly while my phone is stuck in bootloop?
With procedure given here
If I can install it, then will it solve the problem ? (stuck at X logo)
Thanks a lot..
You can enter recovery by turning the phone off and first pressing volume down + volume up + power =[bootloader], and then use the volume arrows to scroll so recovery is across the top, then press the power button to accept the selection. In recovery, android with red triangle, press and hold power then press volume up to bring up menu, and you'll see clear cache option. Otherwise, adb will allow you to erase cache, as well as rebooting to recovery. Fastboot is how you'll flash fresh factory images. And yes, that should fix your problem. Why not go with takju rather than yakju? If you do, i believe you'll have to do a factory reset, as well as the cache and dalvik wipes.
Ok so I have a bizarre and painful one here.
Recently the micro-usb slot faulted so I had to replace it, managed to do it but the volume rocker whose connector was soldered on was removed.
A week later I change roms get the recurring start up animation so go to manually put it into fastboot. Except of course my volume rocker is disconnected. And as the phone can only do recurring animation or off I don't think adb is going to help me.
I have a feeling the answer is going to be fix the volume rocker, if so anyone know how? Or better yet another way to get into fastboot in my current predicament?
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
flash back to stock rom
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
Good thing is you are not "hard bricked" just "soft bricked." Press the power button and volume up and hold till your phone reboots then immediately press the volume button and power down button to enter recovery.Then do a complete wipe, factory reset, then and only then reflash your stock CWM backup of your stock Rom . Just guessing mind you ,because I do not know every single thing you did before trying to return to stock but you should always do a full Wipe or factory reset before flashing between different roms. If your trying to flash a stock image, not a CWM backup, of your firmware you'll need to first reflash your stock recovery and relock your boot loader.
Is your phone a single SIM or dual SIM? Dual SIM phones have allot more issues on Cyanogenmod . If yours is dual SIM I'd stick to stock Rom or sense based custom roms made for our device. By the way what didn't you like about CM if your on a single SIM phone? It had a few issues but with a few tweaks you can get it working great and it's alot less bloated than stock lollipop. I'm on unofficial 12.1 CM with the a5_chl single SIM and it's fine. Having said that I had to tweak several things and I exempt dual SIM versions from my reasons for me liking this Rom. I get that it's sadly alot buggier for those phones . Let me know how things go in fixing your issue and best of luck.
---------- Post added at 10:43 PM ---------- Previous post was at 10:02 PM ----------
Ddreth said:
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
Click to expand...
Click to collapse
First thing, some friendly advice and I truly do mean friendly, not accusing, but you should never let anyone else touch your device when it's in custom recovery. They can seriously mess it up not just"soft brick" it like yours is now.
2nd thing is the factory reset in your custom recovery doesn't have anything to do with your personal files. It's to clean your system and its data so that you can do a fresh install of a different Rom. It's called a "clean flash." A dirty flash is when your upgrading the same custom Rom and you just flash it over the previous version without wiping then clear your Dalvik cache and reboot. These wipes leave your personal files on your internal and external SD card intact unless you specifically wipe then in your custom recovery . They just call it factory reset to make it familiar to the stock Roms use of the term in my opinion. When you have this"soft brick" you can press your power button and volume up to reboot then quickly press power button and volume down to enter recovery. Then factory reset or wipe Dalvik cache if not wanting to reset and reboot one or the other should get you back into your rom.
Hope this helps and good luck plus let me know if this works to resolve your issue. Be happy to help in any way because I have been there myself in the past. Bootloops, soft bricks,etc etc................... If you can name it, I've messed it up.
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,
after experiencing some problems with crashing Galery-app on Stock ROM Android 6.0.1 I decided to do a factory reset.
After factory reset, I got constant android.process.acore and HTC Sense crashed and could not use ANY app nor even see my starting-screen.
I managed to get into the settings and enable USB Debugging. But most of the time, my device did not boot up properly and just showing the HTC-bootscreen. When I pressed volume-up + Power I could reset the phone but was not able to manually power on again. Aso Volume-Down+ Power (To access recovery mode) did not worked anymore.
After getting on low batterie my device turned off and then I was able to access recovery mode again.
I started installing CWM Recovery (Philz touch) which ran fine.
After some unsuccessfull factory resets (same problem as above) I decided to install a custom rom. I choose cm-13.0-20160329-NIGHTLY-m8.zip (Android 6)
The installation process ran fine and I was able to boot normally. Only thing that was wierd: The phone did not recognize my sim-card and I was not able to play any sound. So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop). Naturally, there was the animated CM-Bootlogo showing and not the stock HTC Boot screen.
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power, instead I have to wait till my phone powers up on its own (Which will lead to a bootloop again)
Is there any way to get the device working again?
Thank you!
EDIT: Also it is running really hot while in bootloop.
EDIT2: my battery ran out of energy and I managed to get into recovery mode again. installing latest nightly (20160330) now
EDIT3: "Setup Assistent" crashes while startup. Can't get into recoverymode either. dont know why. phone just starts up normally...
Vendaar said:
Hello,
after experiencing some problems with crashing Galery-app on Stock ROM Android 6.0.1 I decided to do a factory reset.
After factory reset, I got constant android.process.acore and HTC Sense crashed and could not use ANY app nor even see my starting-screen.
I managed to get into the settings and enable USB Debugging. But most of the time, my device did not boot up properly and just showing the HTC-bootscreen. When I pressed volume-up + Power I could reset the phone but was not able to manually power on again. Aso Volume-Down+ Power (To access recovery mode) did not worked anymore.
After getting on low batterie my device turned off and then I was able to access recovery mode again.
I started installing CWM Recovery (Philz touch) which ran fine.
After some unsuccessfull factory resets (same problem as above) I decided to install a custom rom. I choose cm-13.0-20160329-NIGHTLY-m8.zip (Android 6)
The installation process ran fine and I was able to boot normally. Only thing that was wierd: The phone did not recognize my sim-card and I was not able to play any sound. So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop). Naturally, there was the animated CM-Bootlogo showing and not the stock HTC Boot screen.
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power, instead I have to wait till my phone powers up on its own (Which will lead to a bootloop again)
Is there any way to get the device working again?
Thank you!
EDIT: Also it is running really hot while in bootloop.
EDIT2: my battery ran out of energy and I managed to get into recovery mode again. installing latest nightly (20160330) now
EDIT3: "Setup Assistent" crashes while startup. Can't get into recoverymode either. dont know why. phone just starts up normally...
Click to expand...
Click to collapse
Yout could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Vendaar said:
EDIT: Also it is running really hot while in bootloop.
Click to expand...
Click to collapse
That's going to happen. The CPU is working hard during boot, and if its caught in a bootloop, the CPU is getting constantly worked, and heat is the inevitable result.
---------- Post added at 09:38 AM ---------- Previous post was at 09:34 AM ----------
Vendaar said:
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power,
Click to expand...
Click to collapse
Is the phone powering off with Power+vol up; or is it rebooting? It should be rebooting. If its rebooting, the moment the screen goes dark, and before any boot splash screen shows; hold only vol down to access bootloader (don't let go of vol down until you see bootloader).
Failure to get into bootloader this way is usually user error (often the result of not pressing vol down soon enough, or letting go of it too early)
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
jkolner said:
Yout could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Click to expand...
Click to collapse
I agree to try TWRP. Philz hasn't been updated in a very long time, and is known to cause some issues due to that.
---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------
Vendaar said:
So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop).
Click to expand...
Click to collapse
Are you doing full wipe (data, Dalvik, cache) when installing new ROMs? This is recommended, and failure to do so will often lead to boot problems on the ROM.
Also, are you installing gapps (Google apps) with the CM ROMs? Failure to do so will also lead to boot issues, or setup assistant crashing (and a lot of other errors during startup). And the CM ROMs can be finicky with some gapps packages.
Thanks for your replies!
redpoint73 said:
Failure to get into bootloader this way is usually user error (often the result of not pressing vol down soon enough, or letting go of it too early)
Click to expand...
Click to collapse
I pressed both about 10+ seconds. Guess it was my error then.
redpoint73 said:
Are you doing full wipe (data, Dalvik, cache) when installing new ROMs? This is recommended, and failure to do so will often lead to boot problems on the ROM.
Click to expand...
Click to collapse
I did not do a full wipe then . Thought deleting cache will also delete dalvik cache. I did only delete data+cache
redpoint73 said:
Also, are you installing gapps (Google apps) with the CM ROMs? .
Click to expand...
Click to collapse
Yes, I booted to recovery, and used sideload to first push CM and afterwards gapps to the phone.
jkolner said:
Your could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Click to expand...
Click to collapse
Okay. I will now install TWRP 3.0, do a full reset (data, dalvik, cache) and flash the latest CM. Thank you very much!
Android is now booting well. Thank you
Next problem i'm running into: can't play any audiofile. Ringtones dont work either. My phone isn't doing any beep. videos do not work and Gallery-app is crashing instantly. Also my equalizer AudioFX.
Errors, I get are:
Music-App
[CRASH] com.cyanogenmod.eleven threw java.lang.IllegalStateException
Gallery crash:
[CRASH] com.android.gallery3d threw java.lang.RuntimeException
Audiofx:
[CRASH] org.cyanogenmod.audiofx threw java.lang.IndexOutOfBoundsException
I researched some time but did not found anything useful here
EDIT: New problem:: SIM is not recognized by phone anymore. It worked on first boot..
Edit2: cant even hear sound over headphones.
updated to latest nightly. Did not resolve anything.
Bump.
Updated to latest nightly and cleared cache + dalvik before. didn't solve my problem either
Bump
Sent from my m8 using XDA-Developers mobile app
Hello guys,
I tried rooting my phone using the tutorial that is on this site.
then I flashed TWRP on it, the official version by beroid.
this went well and I tried to install crdroid and gapps for this I had to wipe the system, data and cache
after this android wouldn't boot up and now it is stuck in TWRP when I press reboot system.
fastboot doesn't work and I can only see the boot partition in twrp when flashing an image.
I really hope you guys can help me since I'm not really that advanced in rooting devices and this is my first go on it
I see this is marked as solved - is that correct? If so, could you post how you fixed the problem, as I think it's affecting me too. (My issue below.)
Does anyone have any advice on what to do here? I tried to update from:
lineage-14.1-20170320-nightly-crackling-signed.zip
(which was working fine) to:
lineage-14.1-20170328-nightly-crackling-signed.zip
When the updater rebooted into TWRP, it couldn't find the download, and I didn't know where it was either, so I just rebooted, and ended up back in TWRP!
TWRP has 4 reboot options, System, Power Off, Recovery, and Bootloader.
System - goes to TWRP again
Power Off - goes to Wileyfox logo, which stays on the screen forever
Recovery - goes to TWRP (as it should)
Bootloader - goes to fastboot mode
Nothing actually boots into LineageOS.
I tried flashing the previous nightly and the current one direct from the removable SD card, but same results.
TWRP appears to be able to flash anything I want, also fastboot is working when I connect it to my computer, so I assume the bootloader is somehow being prevented from loading LineageOS? Or I've somehow wiped the bootloader? (/boot is empty - is that correct?)
I'm now clueless as to what to do, so any help would be much appreciated.
---------- Post added at 12:15 PM ---------- Previous post was at 12:08 PM ----------
Just made some progress in the last few minutes, using the command:
Code:
fastboot reboot continue
gets it to the LineageOS boot animation.
Now waiting for a hopefully successful boot... :fingers-crossed:
edit: this worked, but I'm not sure I want to risk actually rebooting now
I have this exact same issue.