Causes for a boot loop? - Fascinate Q&A, Help & Troubleshooting

I first noticed a random reboot yesterday and my widgets disappeared and the wallpaper was the original ocean floor/water live one. Other than that no problems and all today my phone seemed ok. So I was sitting around at home later and I hadn't checked my phone in a while so I went to look at it and it's at my boot screen (I flashed the bugdroid vaudeville one where it gives the apple logo the hook) and it doesn't change. I pick it up and I feel the buzzes telling me that it's getting force closes. I did the 3button to reboot to recovery and tried to wipe cache/dalvik/fix permissions to see if anything would change, tried flashing a kernel that was still on my sd (no roms left on it to try) and no difference. When I plug into the wall charger from being off it goes straight into CWM. I was on the stock debloated ED01 rom from adrenalyne's thread and OTB 1.6 kernel.
I'm just curious to see if anyone can figure out what caused the boot loop? I already know that the surefire way to fix it is to odin back to stock and restart from there. I don't readily have access to a Windows computer anymore because I only have a macbook, but I can get to one in the near future, so I'm also wondering if there is anything I can do. My phone can still boot into CWM 3.x.

Related

help phone will not go past vibrant screen

My phone is stuck on the vibrant scree and nothing happens........ i am trying to use odin to flash back to stick and it is always stuck on file analysis.....please help!!!!!!!!!!!!!!!
Try this: http://forum.xda-developers.com/showpost.php?p=8445823&postcount=11
Well mine just sits on file analysis for 10 mins and nothing else happens...can someone please help me i have no phone.
Remove the USB from the phone, remove battery.
Place the battery back in your phone and get back into DOWNLOAD MODE
Close Odin
Run Odin as Administrator
Select the 512 PIT FIle
Select the T959UVJFD.tar file for PDA
Plug in your phone (Make sure you see a COM Port come up)
Start Flashing
rolf90 said:
Well mine just sits on file analysis for 10 mins and nothing else happens...can someone please help me i have no phone.
Click to expand...
Click to collapse
as you i had the same problem and finally got it to work by watching this video on you tube:
1.go to you tube
2.search for flash vibrant
3.first video should be "Flashing Firmware with Odin on Samsung Vibrant" by ZDoomentral, its a 3:00 min video
(sorry can't post direct link but i a restricted since i am a new user)
pay close attention as to how he gets his phone into DOWNLOAD MODE, thats where i was going wrong, and just follow the directions of the video.
my phone is up and running with stock kernel and re-rooted it
man i just want to say i just had this same issue happen to be... im a truck driver and having my phone is serious... mainly to play games or what not...but i just got some from Minnesota and tried the odin method and saw that video on you which help give me a visual and its back up ... im very happy... sad to say it was a careless mistake somewhere but i did a back like i always do and it didnt work for some reason...i had a g1 before this vibrant and ive flashed a lots of roms... but anyway i wanna thank everyone one this forum ... i got my phone back
Does this restart the WHOLE THING? because I have information I didn't backup :/
Yes. It deletes EVERYTHING. Just like it's brand out of the box.
I recommend using Titanium Backup and back all your apps. ALWAYS ALWAYS, do a Nandroid backup before flashing ANYTHING.
scootatheschool1990 said:
Does this restart the WHOLE THING? because I have information I didn't backup :/
Click to expand...
Click to collapse
If you have adb up and running & have the ability to get into recovery while you're bricked you can do aN adb pull before flashing
Adb remount
Adb pull /sdcard
After un-bricking you can adb push the folders back
When I did it..it flash back to stock but I have titanium back up so mt phone is back to how I had it ...and I still have every thing else back on, like my movies music etc..
Sent from my SGH-T959 using XDA App
I was trying to help my friend with his Vibrant and now it's stuck at the splash screen in a loop. I can't seem to get it to download mode or recovery or anything. I've pulled the battery, held down both vol keys while pushing power. Any time I connect the usb, it just starts up the boot loop without giving me a chance to do anything else. I can never get to the green charging battery. Any ideas?
I guess I could provide more info... We had rooted the phone multiple times, but Superuser would FC every time. So, we decided to flash eugene's froyo build (http://forum.xda-developers.com/showthread.php?t=740558). That's when I got the boot loop. Odin said it was finished, and it did not go into recovery. It just started boot looping. Maybe I didn't wait long enough before hitting the power? I'm not sure. Anyway. I'm stuck.
EDIT: Unstuck now. I guess I just need to not panic and read more. I held both VOL keys in while connecting to USB and it went into downloading mode. SO, I flash a stock 2.1 ROM and it's back to the way it was. Calling works fine. No data though. Apparently, that was one of the issues before. I'll try rooting again, but it seems like there's another issue. Also... No settings survive reboots. Like turning on USB debugging... Strange.

rebooting into frankin after flash bricked my phone

I just flashed the Frankin Final rom on my vibrant and all was going well until I rebooted it and now the damn thing seems to be in a boot loop of some sort, but this is different than all others I have seen cause it goes to the samsung screen like normal and then it goes to a totally different screen that is only half size and is jumbled up and not a damn thing is readable. When I plug in my USB to the computer not only is it seen by the computer but it goes to the battery icon and then back to that screwed up - half sized screen. Please someone help.
Go back into recovery and reflash the rom you had installed previously. Or do a nand backup. You did back it all up before you flashed v4 as you should have, right?
I do have it backed up from v3 but it wont even get recognized by adb nor odin. Its the strangest friggin boot loop I have ever seen. When the vibrant screen goes blank then the strange unreadable screen comes on for about 2 seconds and then the vibrant screen comes on and thats over and over. I do have a hardware locked phone so I guess I will have to screw with it when I get home. I did have it in download mode but now I can't even get it to that. Is that USB that came with the phone the only usb that can be used when getting into download mode as I had no troubles at home but I am using my USB from my nexus one at work and its all screwed up.
Did you mean DON'T have a hardware locked vibrant?
I got it about a 2 months ago so I don't know if its locked or not.
Heres what happened in detail.
I rebooted via Rom Manager into the stock recovery.
I installed packages as I have the clockworkmod recovery as update.zip in my 14G sd
I backed up my current Frankin ver3 rom
I erased all userdata and such like I should when flashing a new rom.
I installed the Frankin Final Update
I rebooted the phone like normal and the BAM.
A never ending boot loop that wont even get recognized by my computer.
I cant even plug it into charge as it won't stop bootlooping. the
battery charging icon comes up but then it goes to that funky ass
screen and back to the charging icon. when I unplug the charger it
switches to the Vibrant screen and then the messed up screen. I
really think its bricked as its gotta be the boot image that is
screwed up.
I am very sorry if I am wasting your time on this as I do know how to
properly flash a rom on a phone but this phone is not like my G1 nor
my Nexus. Its about as flaky as a phone can get in my opinion and had
I known it was this flaky I never wouldve gotten the damn thing. I
guess I am going to Tmobile and tellin them the OTA update did this as
there is no way in hell to tell. Not even the splash screen comes up.
Its really bricked.
I just wanted to say that this website and you all developers are the BEST people I have ever followed. This is the very first post I have made and I really do think I f--ked big time. No matter, what you all have done for the G1 and Nexus blows my mind. I never owned a iphone and never will and I think I might say the same about this vibrant. Getting the Nexus bricked is nearly impossible but this Vibrant is to damn confusing and with the lag fixes and crap that I am leary about goin to the store and replacing mine with a new one. Wish me luck.
You may want to try loading Eugene's Froyo Rom that does not brick. Once that is done, try and install Frankin Twiz.
I tried and when the computer won't even read the connection all is bricked. good news though, I went to the tmobile store last night and showed the guy what happened after a OTA Update. he was totally understanding about it. He said it was the white screen of death and that I will have another shipped out the following day. Thanks again for all your help and especially the moderator for putting up with my crap. You all are the bomb-diggity.
I always just boot into recovery and flash say Vibrant7 that always seems to work for me. From there I flash whatever other rom I want.
Recovery meaning
Hold down your Vol + and -
Push Power.
Actually I get scared that I might screw things up by entering recovery through clockwork ( laugh at that now huh) so I always went to the stock recovery and updated my packages with the clockwork recovery file that was named update.zip. I think I had a issue with my phone from the get go as it never would enter download mode unless I was connected to only my samsung charger and no others. I tell ya it was a strange phone and to top it all of the tmobile dude showed me a g2 they had in stock. Nice phone I tell ya but it ain't no Nexus one. Thanks again for all your help guys. Keep the little green dude alive.

Bootlooping Tablet

I'm back after passing on my P7510 to my dad and switching to a TF300. Long story short, my dad shut down the tablet at night and tried powering it up in the morning. Got stuck on the initial Samsung screen with the padlock (it is unlocked).
Tried wiping and reflashing the firmware he was using which was the official ICS build but rooted and deodexed. Got the black screen with lines dealy after the initial Samsung logo and from there, bootlooped. Then I tried flashing another firmware that happened to be on there that he was previously using before the ICS update was released, UEKMP (again just stock, deodexed, and rooted). Same thing happened again with the lines before the boot animation. Samsung boot sound played at least before it just looped the animation. Tried odin with stock 3.2 firmware, which flashes fine, but also ran into the same issue (with lines and all before Samsung bootanimation).
Typically, i probably would have been able to fix similar issue by now by either rebooting (by holding power button and it will magically boot up as it would normally) or wiping and reflashing, but I am stumped on this one. Is it time for RMA? Looks like that's what some people seem to be resorting to after usual fixes don't work. I feel like the lines on the attempt to boot up may be a sign of something? I remember it being a kernel issue, which would be weird considering it was using the stock kernel when it was on Honeycomb or ICS. I've given up tonight as I have work early in the morning, but at least I was able to access nvflash and get cwm 4.x.x.x on there. Luckily it had a power down option so I'm just gonna let it sleep through the night . Any idears are very appreciated!
TL;DR
Bootlooping with black screen and lines even after flashing firmware or stock 3.2 P7510 Odin tar
Can access recovery and download mode fine, including nvflash
For anyone that cares or is in the same boat,
Resorted to going back to stock recovery and wiping the device (this also wipes /sdcard/ of course) and it's working fine again. Now I've got to get everything back on there for my dad..............

Stuck in boot cycle, won't get past Beats animation

Hello all....so I've got an issue with a friend of mine's HTC Rezound.
The thing, all of a sudden one day, wouldn't boot back into the OS. I either hangs at the HTC screen or it gets to the beats boot animation and hangs right there. No further. This was a stock phone. So far, I've been able to unlock the phone via HTCdevs.com, and install Amon Ra's recovery. Prior to this, hboot and fastboot were all I had. Recovery from stock wouldn't boot at all, and factory reset didn't do anything either. Custom recovery let me get in, to where I could flash an RUU or 2, and still, no luck. I've wiped the whole phone, and even reformatted all partitions, then installed 2 different RUU's on it, wiping both times before proceeding. I own a Gnex myself, so I'm no newb to flashing and things.
No matter what, the phone never will boot past the beats logo. Sometimes it only makes it to the start of the "b" curling up, sometimes it makes it to the circular "b" logo, sometimes just will sit at HTC before rebooting. Phone hasn't been wet, and was working fine, prior to this. Battery has been completely discharged as well. Tried booting without the back cover on, as if this were a network bootloop, but still same issue persists. Anybody got any ideas I can try? Considering I've tried different RUU's, and still can't get this thing to rock, wondering what could be causing it. Let me know, down below!
Bump

[Q] Flashing issues

Hi, got some difficulty flashing.
Just trying to flash liquid smooth onto my old s3, but having some difficulty.
Previously loaded with a temasek rom and with devil recovery, pretty sure that the partitions had been reformatted to f2fs to boot. Well, I tried to reformat the partitions to ext4, complete wipe, install rom, gapps and then wiped cache and dalvik. Tried many times to boot, got it to load once but resulted in an unresponsive touchscreen (still works in recovery though). I didn't do anything specific to get it to boot this time, it just hung on the Samsung screen for over 10 minutes, saw a liquid smooth writing (which I thought was a boot loop) for about 20 minutes and then the intostart screen but unresponsive. Needless to say something isn't right, and it can't take half an hour just to reboot the phone!
I would go through odin, and start from scratch, but it's no longer my phone and the phone is no longer recognised by my pc (I guess the connector has been damaged, I had to get the volume buttons repaired this morning just to access recovery!). It can charge, just not specified under device manager on the pc... therefore can't seem to use odin at the moment.
Question is does anyone have a solution? Is there a specific recovery (do you have to use TWRP)? or am I doing something wrong? I've loaded lollipop onto my xperia z2, and a friends galaxy s4 but I'm facing issues with the s3... I have no idea why it just won't boot but if anyone could give me a hand it would be greatly appreciated! I've been banging my head against the wall for hours now! The only way I can get the phone to work again is to restore from my backup... something is definitely wrong here but for the life of me I can't figure out what!

Categories

Resources