[Q] Help please, kernel issues? - Samsung Infuse 4G

I tried to flash the community kernel through odin, and i understand that it said it would take a LONG TIME to boot up, but so far it has been stuck on the samsung logo for about minutes (give or take a few minutes) how long is this supposed to take? or am i supposed to do something?

Related

[Q] stuck in boot loop-can't get into bootloader

I've been trying to find something to fix this, but can't. Basically it's stuck in boot loop after a bad flash. I took the battery out and when I put it back in it goes straight to boot flash and stays. When I try to go into boot loader it buzzes 3 times and then nothing but flashing amber light. Someone said take the SD card out and then boot, but no joy. Any help is greatly appreciated!!
Forget it. After nearly 30 times trying to get into recovery, it finally worked. Not sure what was different, but go it.

[Q] stuck in bootloop! please help! can only boot to download

Hi guys...thanks for taking a minute to help me out.
I have been using the Cyanogenmod Nightlies for a few months, and have recently been experiencing a few random quirks since upgrading to the new version of Android. I decided that I'd do a full wipe and then install the new nightly. Everything worked fine, the phone booted, I could use apps, etc. Then, I decided to restore some of my apps and data from Titanium Backup.
It took about 40 minutes, and then finally got stuck on 98% which was "android data" or "system data" or something like that...i checked back a few minutes later and the phone was completely dead/frozen. I eventually pulled the battery and rebooted the phone, and now it's just stuck in a bootloop.
When I try to boot into recovery, it freezes on the "Samsung Galaxy S3" screen for a while, and then turns off. However, i CAN boot into download mode.
Can someone please point me in the right direction here? I know that android 4.2.2 reworks some of the system folders, making reverting back to a previous version difficult..? I don't know what to do. Really, I just need to be able to get into recovery, but I'm too ignorant to figure it out.
Thanks so much for taking the time to help me, it's very much appreciated!
hold tight, guys! for some reason, it booted into recovery after like the 50th try. hopefully i can figure it out from here! thanks

Hyperdrive ROM s3 (1747) questions, please help

So I have already flashed this ROM by following the procedures asked by the DEV. I used TWRP insted of CWM as it was recommended but for some odd reason whenever I do choose to install what I want instead of the DEV's picks, it doesn't let me get out of boot. It seems that it gets stuck on a boot loop after the reboot and the installation.
The boot seems to last longer than the 10 - 15 min the DEV has listed. It even goes up to 30 minutes.
Does anyone know what the problem? Should I wait for the boot even if it passes well over 45 minutes? :/
And I wipe my system the exact way on recovery mode which is why I'm wondering why it gets stuck on a loop after installation reboot.
I have tried the DEV's pick and it is amazing but I do want to try other things as well. I am running the hyperdrive rom (dev's pick installation) right now.

[Q] Someone please assist me : )

I cannot get a ROM to stick, after one reboot it gets stuck on the boot logo. I have looked through all of the forums and have done this step by step. I have an unlocked bootloader. RSD lite back to stock with success, then root, then install latest TWRP. Nandroid backup then format data, then install ROM. When I reboot it gets stuck on boot logo. This happened ever since I installed CM 10.2, but I really want to install another ROM. I am not sure there is anything else I can do. Can anyone help me?
Nevermind, all is well, the first boot just took 15 minutes or so, which seems a bit long but fixed nevertheless.
There's a fsck (disk check) process that runs and sometimes takes quite a long time. Many have had this issue, patience is a virtue. So are proper thread titles...

[Q] Stuck in Boot and Wont Load Recovery

Sorry everyone for this annoying post but I have done research enough to think that I may be out of luck so you guys are my last hope here.
Here is the senario;
I have been running Cyanogenmod 12 (courtesy of Sultan). Once the ROM was discontinued I decided to give Paranoid 5.1 a shot. I downloaded the new rom, suggested SuperSU and Gapps and booted to the most up to date TWRP. I flashed the rom, then supersu, and finally Gapps and then rebooted my phone. The phone stayed in the boot screen for about 45 minutes (maybe even an hour) so I powered off the phone, pulled the battery, and attempted to boot back into recovery using the power and volume buttons but nothing was working. The phone would just keep vibrating (pulsing) until i let the buttons go and then jump right back into the booting screen until I turned the phone off again. Hopefully I am doing something wrong and there is an easy fix but Im afraid that I now havae a brick on my hands.
Please help,
SuperNewb
[Update]
Now the phone will hold the boot screen for a couple minutes then the screen just goes black. Not sure what that means.
Also, just so you guys dont think im too ignorant, I will say that I I have flashed at least 10 different ROMs before this so I would like to think that I have a decent understanding of how this all should work.
My mistake on posting this question here. I have reposted in the Q&A Forum.

Categories

Resources