I have the latest nightly PACman 20130926 installed and had NEAK kernel installed on it.
I then changed to Thor (not realising I should have came from PACs kernel first and not NEAK) but got bool loops. I went in CMW recovery and
reflashed NEAK.
The phone was fine for a few hours but not has gone into continuous boot loop.
I cant get into recovery or download mode, just constantly rebooting. Same thing happens when connected to PC via USB, when its charging,
with sim and sdcard removed (not that those things would usually make a difference)
Can anybody please help as my phone is inoperable.
Thanks
Related
I was on Insertcoin 1.4 rom, and went to CWM to install new kernel with fm radio. I wiped cache and dalvik, but didn't flash the kernel because I realized that there was two of them, so I wanted to reboot to check which is good but I stuck on bootloop. I took out battery, and rebooted again but still bootlooped. So I wiped with SuperWipe+ and installed rom again. It booted but when I was installing apps from market it freezed. I took out battery and turned on but it stayed on splash screen and did not go to bootanimation. I took out battery 2nd time and booted into recovery. It was showing some errors but it booted. I wiped and installed again, but it was still stuck on splash for a long time. I pulled out battery last time but now it don't even boot into recovery.. Also when i connect to charger amber LED doesn't turn on.. What I can do? I need quick help please.
Also when I connect it to usb it is detected as QHSUSB_DLOAD
I was trying to install AuroraPlay 1.1, everything was going fine, i unlocked my bootloader, installed doomkernel, booted it up and it was fine until then. Then i followed the next installation steps (factory reset, format system, and flashed the rom, did it all on Clockwork mod) and now the Xperia logo keeps looping. I can't enter recovery, the phone doesn't vibrate like it did before on the doomkernel screen and no matter what i press it just goes to the logo again
I'm pretty new to all this so i suppose i just made a common stupid mistake. Flashtool seems to still recognize my phone when i connect it in flash mode, but not for long, it disconnects itself and reconnects again but not in flash mode. Can i save my phone?
After removing the battery many times, and trying again and again, it booted into AuroraPlay
Everything looked normal, so i turned it off and on again to see if it was fixed, but it's looping again, and i still can't acess recovery
I can't think of anything i did differently when it booted successfully
Start from begining again:
-flash stock firmware and see does it boot up
-reflash doom kernel again, if you can enter fastboot mode (hold search when pluging in usb)
-boot rom again, to see if stock rom can boot up with doomlord kernel
-if you can, reset to recovery(keep pressing back button), format data and system and install Aurora again
If you manage to boot to (any) rom, check your sd card for errors, if any...
Around half an hour after my last post, i left my xperia looping for like 10 minutes to see if anything changed, then took out the battery and booted it up again
this time i managed to go into recovery, but didnt want to flash everything again so i just applied the doomkernel v14 wifi fix that i couldnt apply before
it then booted into the rom normally and i've been using it since without a problem
kinda afraid to reboot though
hi guys. Idk what happened to my phone. never had this happened to it before. my phone has been working properly. I have been running smooth rom2/3 without any problems. I then wanted to try synergyrom mk4 so I downloaded it. i wanted to backup my rom just incase something went wrong so then I boot into recovery( teamwin recovery) it booted and the logo of teamwin stays on then blinks then stays on and blinks... I tried pulling the battery and just turning the phone and it still goes into the teamwin recovery logo.
idk what do to. someone please help me...
UPDATE: I found the answer to my post. sorry I couldn't find it earlier I searched and couldn't find nothing until I read on someother post by iannb to flash philz recovery via oden and phone booted fine.
Hi guys,
I've got a big problem with my Gnex. I was running AOSPAL Paranoid SaberDroid ROM with Dirty V kernel and Nephilim's settings. Just the read ahead buffer was set as default so it was 512 I think. I think I just forgot to change it. Everything was ok and then I changed RAB to this value about 4000 (max). I started antutu benchmark and while it was running the phone restarted and got into boot loop. I don't know if it was the reason of the issue, but I wanted to tell you all the circumstances. When I tried to turn it on the Google logo appeared and then the system loading animation started, after about 3-5 seconds it restarted and so over and over again. I was able to enter recovery mode, so I wiped cache and dalvik cache. Nothing changed. I flashed Dirty V kernel again, thinking that settings would turn back to default, but it also didn't change anything. I flashed franco kernel, and also nothing happened. I returned nandroid backup but it also didn't help with this boot loop. Then I wiped cache, dalvik cache, system, data and clean flashed SaberDroid ROM with stock kernel and PA gapps. Nothing. I plugged my phone to computer and flashed Google factory image using WugFresh Toolkit, so it wiped everything unrooted my phone and flashed stock clean 4.1.2 android and everything. I thought that will solve my problem, but also it didn't help. Nexus is still in boot loop - it keeps restarting when there is nexus logo animation. I was scared at that moment. I forgot to mention, that I could get to fastboot mode, recovery and the battery logo was showing correctly when phone was plugged to charger. Then I locked the bootloader so it is completly stock right now, it just doesn't turn on...
I read the topic about omap flashing, but as I understand it is for those devices, which can not turn into fastboot mode (and mine does) and then the solution is to flash google factory image, what I did... When phone is turned off and plugged to computer the device menager shows for 2 secs omap4440, and when it is in fastboot mode and plugged to comp it shows normally as Android Phone (Google Galaxy Nexus BootLoader Interface, because I had drivers installed to use the Toolkit.
It is all what I could do and I don't know what else could be done to ressurect my loved Gnex .
Do You guys know what's going on?
Please help me.
I think I have read somewhere in the Dirty V thread that some bug in the kernel was causing the Google logo boot loop. Have you tried using 0sm0sis' Emergency Kernel Cleaning Script listed in his signature? I remember him telling someone to use that script in the kernel thread.
osm0sis's zip only restores kernel tweaks and settings to default. I didn't try it, but now I don't have to, because I don't have any custom kernel right now. My phone is pure stock.
Yesterday I tried omap flashing, and it run properly, but also didn't change anything. I also flashed Google factory image again after omap flashing.
Any other tips? It doesn't look optimistic ;/. Maybe it's hardware? But I thought reboot loops are connected to software and it is soft brick, which can be repaired.
Hi guys,
I left my phone on charge overnight and in the morning it was off and wouldn't switch back on.
A debrick image allowed me to get the phone into ODIN download mode (i couldn't get into the recovery mode though).
I have tried several different roms and now (i think) its on a stock 4.4.2 rom.
Odin seems to flash the phone without any errors but upon reboot shows "Booting Recovery..." then gets stuck in a boot loop.
I have even tried CWM - Odin seems to flash it without a problem but when it reboots it just shows "Booting Recovery..." and gets stuck in a boot loop (I have tried the Up Volume + Home + Power with no success).
Since it was on the stock rom and has never had a custom rom on it (until lately trying to fix it) it seems likely that the flash storage is dead or has bad sectors?
Any ideas? I have never had a phone die like this before
Thanks
I have exaktly the same problem and i think we are not alone.
Have you tried all usual things e.g. battery pull?
see
http://www.smartmobilephonesolutions.com/content/android-stuck-startup-boot-loop