damn boot loops... - Nexus 4 Q&A, Help & Troubleshooting

hey guys, It seems that i cant get my phone out of boot loop. This ocurred last night while i was switching roms. I went from PA jan11 build downgrading to the beta 8 build. I was able to downgrade successfully, but when i tried to upgrade to the latest experimental feb1 build I then got bootloops. Now when i tried to flash back to the older build it still wouldnt work.. My phone was at very low battery at the time(under 10%) through the whole process. I charged my phone over night and when i tried flashing PA again it still doesnt work. I am still able to enter recovery and fastboot. I tried to go complete stock through fastboot(and erased all data through fastboot) and now im able to see the Nexus X logo. This is where im stuck. I also upgraded twrp to latest 2.4.1.0 and it told me my data was encrypted. I fixed this by wiping the entire system through twrp. Then I went back into fastboot reflashed the rom again and im still stuck here with a Nexus logo. Any help?
EDIT: NVM I fixed it, installing cfx through twrp seemed to work. please close this

Related

Nexus 4 stuck on boot animation

Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus
bump bump
I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!
my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...
badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?
Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

Bricked?

I was from LineageOS 14.1 and I saw a post where the Nougat update has been pushed. Decided to flash A2017U B29 and it worked fine but when I tried to update, it said failed to update. So decided to reinstall the B29 rom again, and it still failed. So I decided to flash back to my stock rom which is A2017G and my phone is now stuck at the ZTE Boot logo. Waited for more than 40 minutes, still stuck there. Decided to go back to recovery and it seems that my TWRP recovery is no longer there. Only able to go back to stock recovery. Tried factory reset, wipe cache and reboot, still stuck on boot logo. Is there any way to fix this? Basically new to Android so dont really know what I'm doing. Just following tutorials that are in this forum. Pretty much f*cked up right now.
Edit : Its 12.18am now from where Im from. Hopefully someone can help me fix this issue before I go to work later in the morning :/

Nexus 4 only boots to fastboot/download mode, otherwise stuck in bootloop. Need help.

I was running cm12.1 a while ago, and updated to cm13. It broke one of my apps that i used on a regular basis at the time, so i tried downgrading back to cm12.1. The OS rebooted into twrp, but nothing happened. I rebooted but it wouldn't let me out of twrp/fastboot/download mode.I tried wiping the data and re flashing cm12.1, nothing. same issue. I downloaded a different custom recovery (a version of clockwork mod) but i believe it was in the wrong format and when i tried to overwrite my recovery with this other one in twrp, my phone stopped booting into recovery at all, and only download mode or fastboot, besides bootlooping when plugged in and not holding any volume buttons or power. The nexus 4 itself IS unlocked and rooted, and was working fine before this happened. I don't know what to do, and i hope someone can help me.
orionboughton said:
I was running cm12.1 a while ago, and updated to cm13. It broke one of my apps that i used on a regular basis at the time, so i tried downgrading back to cm12.1. The OS rebooted into twrp, but nothing happened. I rebooted but it wouldn't let me out of twrp/fastboot/download mode.I tried wiping the data and re flashing cm12.1, nothing. same issue. I downloaded a different custom recovery (a version of clockwork mod) but i believe it was in the wrong format and when i tried to overwrite my recovery with this other one in twrp, my phone stopped booting into recovery at all, and only download mode or fastboot, besides bootlooping when plugged in and not holding any volume buttons or power. The nexus 4 itself IS unlocked and rooted, and was working fine before this happened. I don't know what to do, and i hope someone can help me.
Click to expand...
Click to collapse
Follow this and flash the factory images: https://www.youtube.com/watch?v=uO7HkTrRzwM
Nitin
Thanks for the quick response, i will try to follow that tutorial.
I just want to state that if anyone has the same problem as me, I found a way to fix it
https://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
that nice little tutorial there saved me

Weird boot problem

I've had my note 4 for a little while now and I've been trying a lot of roms. Yesterday I tried flashing the flyme os 6 beta which I couldn't get to boot up. After that I flashed back the rom I was coming from and I noticed that twrp was unable to boot to recovery or system and went straight to stock recovery mode. When I manually started the rom up and tried to boot to twrp the screen went black for about a minute before booting into recovery. I've tried flashing back the factory images, reflashing twrp, different kernels, different BL and CP versions but nothing seems to work, I keep having this weird issue.
PS: I also can't turn it on when it's powered off. I have to remove the battery first before I can.
Has anyone else had this / knows how to get rid of this issue?

Categories

Resources