Could I have blown my Galaxy S 4 i9505? - Galaxy S 4 Q&A, Help & Troubleshooting

Short and sweet. I haven't used SetCPU for awhile and I've been using the ROM in my sig, which isn't entirely stable. Though I went to set the CPU to max 1890Mhz just before I went to use Titanium Backup to do a huge compressed backup. So it makes it a little faster. I accidentally (honest accident) swiped to the end of the list on available CPU frequencies.. I think the highest was like 2334 or something.. well the phone crashed at something like 2035. I rebooted it and it booted up fine, but there had been some noticeable changes. Some apps I had frozen had been unfrozen, some apps had lost their settings etc. I figured this was due to a bad shut down.
Today I was asleep and I left my phone like usual so the alarm would ring. When I woke up I dismissed the alarm and the phone hung for a good 20 seconds. Then 3 apps updated and the phone crashed whilst browsing the play store.
Now when I tried to boot I got that typical vibration that something had got unresponsive in the background and was crashing. (Whilst at boot logo) It was just doing a loop of that. Then I rebooted it myself again and now it does nothing. But it still was stuck at the logo forever.
So I went into PhilZ recovery and wiped everything. Dalvik, Cache and Wipe to Install a New ROM.
Now it won't even GET to the Booting Logo and just stays on the 'Samsung Galaxy S4 Gt-I9505' screen..
So gradually my phone is retreating into an even worse position.
Is there a chance I could have blown my CPU or something with overclocking by accident for a few seconds?

Nope, you shouldn't have blown a cpu, since it was working afterwards. Seems more like hangs due to some bad wipe.
What you can do is try to install any rom and make a full wipe. If that doesn't work apply a new kernel.
If that doesn't work. Try install stock samsung rom (no wipe)
If it's still in boot loop (do full wipe) however if you got any saved data do the last step if you're sure nothing else works.
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]

I didn't set it to 'Apply on Boot' because it was only meant to be a temporary overclock.
I just took the MicroSD out now and I am going to put the latest release of the ROM I am using on it, flash it and see if it works and flash the modem too to try and get some more stability out of it. I'll see how that goes, if it doesn't get off the 'Galaxy S 4' screen I am going to have to assume there's a big problem...

Well then there can be something else, if you haven't sent it to apply at boot it can be some kernel issue or something got stuck. It seems like there's something that blocks you from booting the phone up. Interesting,
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]

boot into recovery.. wipe /system, /data and /cache then install rom from external sd card

Related

Nero v3 infinite reboot issue

Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
stoanhart said:
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
Click to expand...
Click to collapse
Was her phone stock before you started tinkering with it?
In any case I'd suggest re-download nerov3 (to avoid corrupted download issue), ODIN back to JFD (remove the ghosts from the past ROM's) and reflash.
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
stoanhart said:
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
Click to expand...
Click to collapse
Good luck!
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
stoanhart said:
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
Click to expand...
Click to collapse
Did you re-download nero? It might be a corrupted download, I haven't seen anyone with the same symptoms.
Does it happen if Voodoo is disabled?
EDIT: Saw that you didn't even have a chance to enable it, hmm, try a different ROM? Axura or Eugene's work.
No, I didn't try re-downloading it. Perhaps I'll give that a try, although it is the same file I flashed onto my phone.
After a bit of time playing with Nero, though, I'm considering going back. The parts that work are slick and wonderful, but it very much feels like beta software. In particular, scrolling lists or web pages is choppy. I've heard this criticism of Android before, but I've never experienced it with the original Vibrant software. It was always so smooth. It makes me think that maybe Samsung was using GPU acceleration in some places. Also, I seem to have some problems with the touchscreen becoming unresponsive, especially in the browser if it's blocked waiting for data (another bug...).
Is it possible to run the JL5 modem on the stock image? That would be great.

Got stuck in an endless reboot on a non journaled rom.. No problem!

I tried restoring the stock battery icon using ACS 1.1 and my phone got stuck in an endless reboot cycle. I kind of started freaking out as my phone had been acting flawlessly prior to this and I was scared of corrupting my data. I had a recent restore point saved (I have MyBackup make one every morning while I'm sleeping) but that would mean I'd have to wipe my phone and after everyone complaining about how hard it is for them getting ACS 1.1 to work on there phone I was scared to test my luck a second time. I thought the only other option would be a battery pull which would lead to bad data with bad backups. So instead of following one of those two options I three finger rebooted out of the loop and immediately three finger booted into CWM. I wiped only my cache and dalvik and then reflashed 1.1 over the existing one. I then rebooted and the only things I had to do were reflash my Vision kernel and delete a few apps that I did not want that come with the ACS rom that got reinstalled. I assume none of my data got corrupted and I know this probably won't save everybody from corrupted data due to endless reboots but just thought I'd share my method. So far everything has been running just as good as ever.

Nothing works as it should...

I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.

[Q] TMo Note 3 Deciding Rebooting is the Only Solution

Ended up "solving" this by doing a stock restore via Odin, after which TouchWiz would never load an icon (crash loop). Reinstalled TWRP via Odin, then flashed ViSiON X N3 via TWRP.
--
Morning guys,
I've had some reboots lately and a weird situation last week where I had to do operating system surgery to get the thing to boot at all.... HOWEVER things were going quite well for some time, and it's been rooted and non-stock for months.
Nevertheless I woke up this morning and it was off, I figured the battery had died so I swapped batteries... It boots, it gets to the launcher and it loads the app icons then freezes and reboots... over and over again.
edit: to be clear, as soon as the slider bar touches the right-hand side the phone freezes, the vibration holds for several seconds, and then the device reboots. obviously not what one expects from this operation (having done it before). I was able to wipe the Cache separately... trying to wipe the Dalvik cache all by itself in an advanced wipe does this reboot thing.
OK I said, i will just clear and reflash this.
Going into TWRP, attempting to do a factory reset wipe just freezes, buzzes, and reboots immediately (to the not working OS)... in order to make this all stop I pull the battery, because now the button on the side won't seem to do a hardware poweroff for anything. Just ends up resetting the current reboot.
--
Any advice would be helpful now. I was just going to say forget it and grab the tiniest ROM i could find and ride it out until I upgrade the device, but now I'm just concerned with getting it active. The rebooting in recovery when trying to do a wipe does not make me feel too great. First and only problem I've had with android roms.
Thanks,
Chris

help on metro pcs boot animation freeze. sm-g360t1

At times the metro boot logo freezes on start up, and also every ten seconds will vibrate five times. Not stuck on the software boot though. restoring to stock firmware does nothing, removed boot animation but still vibrated at black screen. the reason I would want it fixed is I cant install an app that requires reboot every time its stuck. then the only way to repair is to use odin. any help is greatly appreciated.
Capitah Knight said:
At times the metro boot logo freezes on start up, and also every ten seconds will vibrate five times. Not stuck on the software boot though. restoring to stock firmware does nothing, removed boot animation but still vibrated at black screen. the reason I would want it fixed is I cant install an app that requires reboot every time its stuck. then the only way to repair is to use odin. any help is greatly appreciated.
Click to expand...
Click to collapse
You can always try SlimPickins Rom. It's a lighter, faster, version of the stock firmware and, as such, runs smoother.
http://forum.xda-developers.com/showthread.php?p=63868639
If you have tons of apps or if you're using a bunch of Xposed modules on this device though, then it may hang on the boot screen from time to time anyway, causing you to have to pop the battery and try booting again and again until it eventually starts up. Whenever this happens I usually backup all my data in TWRP, then do a standard wipe of the device, reflash SlimPickins clean and then restore my data. If you have a lot of apps though, it may be even better on this device to just back them up in Titanium Backup and restore them one by one as you need them, so as not to bog the device right back down again.
It shouldn't be vibrating on boot though. That usually indicates a deeper problem in the system or with one of the partitions, which is generally fixed by flashing the stock firmware, but I recommend just trying SlimPickins and making sure your apps aren't taking up too much space or using up too much memory. One thing I did was delete the standard Facebook app and went with a 3rd party one called "Swipe", which pretty much looks the same, but is 300mbs less in size and takes up a lot less memory. I also dialed back my Xposed mods to just the essentials and I haven't really had a problem since.

Categories

Resources