Develop Bugs

Returned to stock, reboot, crash...

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

[Q] Galaxy Nexus Stuck in Boot as "X" Screen

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?

Stuck on Google Screen - Restore Didn't Work

Good Morning All -
A few days ago, I dualbooted my N7 with Ubuntu. The installation went fine and the tablet was working with no issues over the last several days. Last night, I was using the tablet and set it down. I went to pick it up (roughly 5 minutes later) and the touch screen was unresponsive. I was at the lock screen but couldn't get it to unlock. I pushed the wrong key-combo first and the device took a screen shot.
I was able to reboot into fastboot and attempted to go to recovery. The device would just hang at the Google logo. I pushed a factory firmware update from my Ubuntu system and attempted to reset -- no joy. This morning, I used Nexus Root Toolkit from my Windows 8 machine to see if I could get it up. Root Tool kit worked fine, pushed the images over again and restarted but it continues to hang at the Google logo.
Looking for any other advice folks may have on getting the device to boot.
EDIT: I can get to the bootloader fine and the computer recognizes it.
Thanks!

Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.

xbi0s said:
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
Click to expand...
Click to collapse
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.

antonio824 said:
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
Click to expand...
Click to collapse
I'm unable to get into the restore menu. Hangs at the Google logo when attempting to get there.

I've tried about any solution I could find... Bumping one last time before I torch the unit :\

Nothing can be done. Its something inside. If its the 2013 model, call and get it rma'd. Sorry man.
Sent from my LG-LS970 using XDA Premium HD app

Resurrecting this thread to keep a work log.
I made have made some progress but hitting another roadblock. I've been holed up at home due to an auto accident so I started tinkering with the N7 2013 again.
Using the Nexus Root Toolkit, I am able to launch "Boot Temporary - Custom Recovery" from the advanced options. The problem I now run into is TWRP's touchscreen will not work. I attempted to do volume up/down to see if I could select but it wouldn't. The software is not frozen as I can see the temperature changing.
Anyone have any thoughts or information on how to boot another custom recovery that uses button inputs? I appreciate any input.
Updates:
1. I was able to push TWRP via "fastboot flash recovery." It went to the Google Logo then loaded TeamWin screen. I started to see errors when the program launched. "Unable to mount..." multiple times then the device rebooted. Device stuck on the Google screen.
2. Shut the device down, booted back into Fastboot. Selected Recovery and it began loading again. This time, the app launched and worked. Touchscreen does not work but the CPU temp is fluctuating and minutes tick up.
Update 4:49PM Central:
1. I am able to install and boot into TWRP 2.8.0.1 through TWRP 2.7.1.1. Those versions load but of course touch screen does not work.
2. I have been unable to get CWM to load... It installs fine but I cannot boot into.
3. The factory recovery images also do not load.

HTC One M8 won't boot after downgrading CM 13 to 12.1

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

[SOLVED][ZE551ML] I bricked my phone. Can´t enter bootloader or recovery. Bootloop

I was already using a custom rom and I wanted to update my Twrp from 2.8 to 3.0. So I booted to twrp, then I flashed twrp 3.0 using the Install menu and selecting the proper twrp image. But in the flash screen I ticked the boot partition and flashed. Immediately my phone turned off and now I can't enter recovery and my phone is on a bootloop without any system it seems (even though I actually have cyanogen 13 installed). The only thing it does is show the Asus logo and then reboot. I can't boot the bootloader or recovery.
I don't know what to do. It's the first time I actually brick a phone =/
Any help will be great!Thanks
EDIT: well... I installed intelSOC, connected my phone to my PC and after some bootloops it suddenly booted to twrp (I didnt do anything) , then I reinstalled my rom and it seems everything is normal now.

After many tries my TWRP wouldnt get past the blue logo screen. Then I decided to follow this tutorial http://techtrickz.com/how-to/unbrick-a-bricked-zenfone-2-ze550mlze551ml-restore-bootloader/
After doing every step, my ASUS LOGO is gone, replaced by something it seems a Flag with pink, yellow and purple horizontal lines, and nothing else. The phone boots, shows this flag and there is nothing else I can do.
Ideas?

Turns out I followed an incomplete tutorial. If you have the same issue as I did, just follow this one: http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

just follow my thread and you will be success in one try!
https://forum.xda-developers.com/showthread.php?t=3828667
---------- Post added at 09:46 AM ---------- Previous post was at 09:46 AM ----------
just follow my thread and you will be success in one try!
https://forum.xda-developers.com/showthread.php?t=3828667