• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Boot Loop Help?

TacClark

Newbie
Before I get into the problem here's some info. I was running the stock ROM that the phone comes with updated to (I think) 2.2.2. I did have the phone rooted. So, my problem is this. Today my phone prompted me to do an update, no problem, I clicked reboot or whatever the "ok" button says. The phone shuts down and after all the unloading and recovery type things display, it freezes on the "boost mobile" logo screen where it normally plays the little tune. I left it there for over 30 minutes, nothing. So, I tried a factory reset through the recovery menu. It booted into recovery mode but gave me the same issue after reset. So I flashed a stock ROM with ODIN. I now seem to have a boot loop. The phone will boot just fine, even playing the tune and moving past the screen it froze on before but it loads into the lock screen and stays there for about a second before rebooting. This seems to continue indefinitely unless I have it plugged into a computer or my charger, in which case it just shuts down and displays the battery as charging. I have no idea what else to do, any ideas?

EDIT: I just tried to re-ODIN with ED13 and the phone booted just fine. It stayed on and started the media scanner, I turned off the sound using the slider on the lock screen (personal preference), unlocked the phone, removed the little android tips guy from the home screen, and attempted to turn off airplane mode (it was automatically enabled, so I held power button and tapped airplane mode) the phone immediately shut down and went to the battery charging screen as it was still plugged into my computer.
 
I don't know for sure what the problem is but try odining to the newest baseband. I don't recall it's name but it's not ed13 or ej06... The other one. My thought is it tried to it's to it, failed along the way and now the files it did manage to get in are stuck. Make sure to use all the zips to, phone boot and pda and do a factory reset before hand for good measure. Of that doesn't work you'll have to wait for a response from someone else.

Edit... It's fa19
 
I appreciate the help but unfortunately that doesn't work. I don't even get to interact with the phone, it gets to the lock screen and before I can do anything it restarts. The boot loop appears to have something to do with the wireless signal being enabled because I have reflashed the ED13 several times and am able to do anything on the phone short of disable airplane mode. As soon as I turn airplane mode off, the phone boot loops.
 
I appreciate the help but unfortunately that doesn't work. I don't even get to interact with the phone, it gets to the lock screen and before I can do anything it restarts. The boot loop appears to have something to do with the wireless signal being enabled because I have reflashed the ED13 several times and am able to do anything on the phone short of disable airplane mode. As soon as I turn airplane mode off, the phone boot loops.

If Odin can't fix your boot looped phone I think the only other choice you have is to send it back to Samsung.
 
What stock baseband versions have you tried? Try each one. when you say stock rom there was nothing custom at all? No kernel custom kernel or theme? Did you remove any stock apk's?

Can you put your phone in debug mode? If so get a copy of adb (shabby mod had it with it) and post the results of running "adb shell dmesg"

Do you have can on your phone? You can try to fix permissions but tbh I don't think it will fix the issue but it's worth a shot. If none of the above work, sorry I can't help but I tried.
 
How do I actually get the results of running the adb? It closes too quickly for me to see anything.

orry about that, do "adb shell" then when it gives you the next prompt do dmesg

the output will be long but I'm thinking if there is an error message appearing in there it won't be in the tail.
 
Ok, sorry bout that, here's a way to follow the dmesg tail.

adb shell cat /proc/kmsg

let that run, it'll show new dmesg messages as they come in, then try to turn off airplane mode. Once the phone shuts itself off press ctrl + C to stop the command (if it doesn't stop itself) and look for anything in the last bit that might indicate an issue, or copy and paste here and I'll take a look.

Also if you're interested in seeing your entire dmesg log run:
adb shell
dmesg > /sdcard/dmesg.txt

That command will pipe your entire dmesg log into a file called dmesg.txt on your sdcard.

EDIT: Sorry it took so long to reply, I was doing some research on how to get a live dmesg feed off of android since /var/log/messages doesn't exist (/var doesn't exist)
 
Are you rooted? Do you have cwm?
I have a feeling we're heading straight into a brick wall :/ you might have to rma your phone sadly.
 
Just tried it again after a reboot and it worked. I'm not at all an expert at reading this stuff (and by that I mean I have no idea what any of it means) but this look kind of odd...

init: sys_prop: permission denied uid:1000 name:iq.bridge.enabled

I get that when I try to disable airplane mode.
 
Well... what that looks like to me is your build.prop/sys.prop didn't get updated when the update was installed but the file isn't actually there as it's trying to call the carrier IQ service.
UID 1000 is the system server.

can you pull your build.prop from your phone and upload it for me.
make a folder like C:\buildfile
If you don't make the folder first adb will return an error about cannot create directory

"ADB pull /system/build.prop c:\buildfile"

This will copy build.prop to C:\buildfile\build.prop
 
I'm not seeing anything. The only thing I would really recommend now is trying cwm fix permissions.

Flash CWM using odin, boot into it with vol up + power... go to advanced... fix permissions and if your phone works from there you can try flashing back to stock completely. I suppose it's possible that the update exited before finishing setting the permissions but, I don't know man. If that doesn't work make sure you're completely stock (no root no cwm by reflashing a completely stock odin image) and send it into samsung. Sorry I couldn't help out more but at least I tried..

I do see differences in your build.prop from mine but mine is also from CTMod which has been highly customized over stock. You COULD try flashing CTMod 2.5 with cwm if fix perms doesn't work but I don't really see that fixing it. I don't know why but the prevail's ota updates seem to cause people problems.
 
Yeah, neither of those worked. But I do appreciate the help and now I at least know how to do all of this so I can get custom ROMs when I get a working phone. It's off to Samsung with my Prevail...as soon as I can figure out how to use their bloody support site. :p

EDIT: I flashed FA19 onto the phone in preparation to send it to Samsung. It now gets to the first Samsung logo screen (not the flashing one) and freezes. I can get into download mode but not recovery mode and when I plug it up to charge with the phone powered down I only get the battery outline as opposed to the usual green fill and battery percentage. Thought this might help somehow.
 
not really :/ it's only really telling me that something got corrupt somehow. Samsung's your best bet now. Look at the bright side... you will likely get a shiny new phone!
 
i did the fa19 update yesterday and it just stops at the boost logo. phone wont connect so i can use odin. I tried hard reseting everything.. either I claim it on insurance and get a new phone on tuesday or send it to samsung. FML!
 
you cant get the phone back into dl mode? if you pull the battery then hold vol down camera and power...or recovery?
 
you cant get the phone back into dl mode? if you pull the battery then hold vol down camera and power...or recovery?

the pc doesn't recognize the device.. im on windows 7 home. Ive done the proper methods to install drivers. I even tried on my laptop. No luck.
 
But seriously, how do I get an RMA for this phone? I registered it on the samsung support site and I have four options. Modify account info, buy accessories, (next to register new products) mobile phone, and all other products. I try to find a location on the support site and it tells me to call a number but when I do, they're always closed. I'm so confused...
 
But seriously, how do I get an RMA for this phone? I registered it on the samsung support site and I have four options. Modify account info, buy accessories, (next to register new products) mobile phone, and all other products. I try to find a location on the support site and it tells me to call a number but when I do, they're always closed. I'm so confused...

Samsung

click live chat;)
 
Back
Top Bottom