okay so the weirdest thing just happened i was restoring a nand of cm7 and it just bootlooped on the splash screen so i tried a full wipe and fresh install but no dice the weird thing is i just nanded to nights ago to do the prl thing and everything worked fine. so i decided to restore my sense rom and it worked fine.
has that ever happened to anyone else.
Yup happened to me quite a few times. It seems like with my phone when I come back from sense it throws my system for a loop at times. Then at times it fine. I just reflash my recovery and its fine when it throws it off.
Root/Hack-Mod_Always *
it freaked me out when it did it, because ive never had it bootloop on the splash screen like that before.
A your not the only one. One time I was pissed because I had a time limit which was the wife with the ""your always on the phone thing"".
Root/Hack-Mod_Always *
My phone does the opposite, loops when I go back to Sense, works fine when I come back.
Booty loops everywhere lol.
sent from a series of tubes.
Boot loops like a BOSS!!
Just today I had a boot loop for flashing a sense ROM so I can update the PRL. Had to Hboot that bizatch and start from scratch. >_<
I want a boot animation that looks like a boot loop.
posted via tappa tappa tappa
For me this only happens going back to Sense. It also happens if I forget to flash fr-boot >_<
Related
Hi guys
I have re-downloaded the ROM, and also tried flashing with a completely different one, one Sense based the other generic android 2.1 based... That one freezes on the 4 colour pyrotechnics nexus splash screen.
Any ideas how to get around this?
Thanks
Mark
UPDATE:
It seems that I CAN restore to a nanbackup and get back to Sense, but without my settings intact. As soon as I try to flash to ANY rom again, it will still freeze at quietly brilliant or the nexus 4 colour splash.
Ive tired an SD repair, wiped everything I could wipe using the bootloader menu... so why all of a sudden this, I have often flashed with no problem in the past.
Tx
Mark.
yeah dat happens to mine now iv had to revert back to the stock android 1.5, im still rotted tho... its disappointing
Same here, tried the Villain Mod, freezes on this screen.
Attempting to restore now...
been messing about with the g1 a bit, flashing various roms and whatnot but i seem to be getting some very odd problems, for example when restoring the backup i took before messing about today it simply wont boot past the g1 screen, so i switched to a backup made yesterday and it booted, so i stuck my custom boot anim on and restarted, now it wont boot past the boot anim, it just keeps looping the animation forever
ive done full wipes with ohsaka and wiped data and cache but no change, what concerns me is that by all rights the backups should load fine right? i mean they were working perfectly before and all i have done is restore it (which worked fine yesterday) even in the case above surely changing the boot animation shouldnt have an effect on the phone actually booting should it. anyone else had previously working backups suddenly not work?
You said you stuck your custom boot animation on and it started boot looping? Maybe that is the problem? Try it without.
My HD2 worked perfectly fine with almost every rom I have flashed on it. Recently I dropped my phone, it was a pretty hard fall. The battery even came out. After that fall my HD2 would not boot, it was just stuck in a continuous boot loop and never fully started up. When I got home I re-flashed the same rom and everything was OK. BUT now, every week or so I get stuck in a boot loop and I have to re-flash my rom again to get out of it.
BTW, my rom is UrDroid HTC Sensation XL Stock, version 1.8
http://forum.xda-developers.com/showthread.php?t=1348922
BlaBlaBla01 said:
..........The battery even came out..............it was just stuck in a continuous boot loop and never fully started up.
Click to expand...
Click to collapse
those symptoms point to a bent battery pin, however since you say it works for a while and then stops, its unlikely, but worth inspecting them VERY carefully.
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.