[Q] i9500 Won't Boot After Uninstalling setCPU - Galaxy S 4 Q&A, Help & Troubleshooting

Hello everyone. I have a i9500 international 16gb. I rooted it with cvm method. And installed setCPU. Then i have check set on boot. And altered governor settings mindlessly. After this I uninstalled setCPU. And right after that restarted the phone opened like a charm after couple of seconds crashed and rebooted itself when opened it sayed 0% battery and rebooted again then again saying no battery. I opened and looked at the battery, it is NOT Flat anymore. And phone smelled a little (not too much).
Before this happened i have used phone without a problem for days. Now it is booting just to reboot right after.
Is it because Battery or Did i need to Format it? And I am a complete beginner so if you could explain details it would be appreciated. I dont know which other information to supply. So let me know.
Thanks in advance.

Related

i9505 black screen after reboot

Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Same problem on same phone
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
I was using a CM10.1 nightly build for my i9505 and attempted to install the AVAST Anti-Theft feature using the root install method. On the first attempt at installation there was a free-space error, in which the amount of free space shown in the /system partition had overflowed and showed negative free space. To work around that error I filled up my /system partition until there was only 100mb free and then the install worked. All went well until I did a reboot; the phone hung at the i9505 screen.
I tried rebooting the phone and removing the battery for a short while, but nothing worked - the phone still hung at the i9505 screen. However, all other functions worked, so I just reflashed CM10.1 after wiping /cache, /data (but not /data/media), /system, and the Dalvik-cache (though that is in /cache AFAIK so pretty redundant). All was fine after that reflash, other than the annoyance of having to set everything up again (didn't make a backup recently).
Obviously the Anti-Theft wasn't very secure if it could be removed by a simple reflash. But to be fair, I highly doubt any software can protect itself from a format!
Anyway, just letting people know that I can confirm this this problem exists, and how I fixed it on my phone.
ingvarr_zaag said:
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock firmware using odin
Go to stock recovery there factory reset and wipe
Reboot
Note all data will be lost take backup b4
.
sheomualjy said:
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
Click to expand...
Click to collapse
I had Clockwork Recovery installed but I couldn't use it, because after reboot the screen was black. I managed to get to android recovery and flashed stock Samsung ROM by Odin. It didn't help.
After 2 weeks in service it's possible that today I get my phone back. Finally, because two weeks with Samsung Galaxy Advance were miserable.
Actual status on service's page says, that they replaced main board in my phone.
BTW: no Avast Anti Theft ever again.

Could I have blown my Galaxy S 4 i9505?

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

[Q] Stuck on samsung logo after battery dies out Note 4

Hi,
I have a SMN910F rooted on stock kitkat downloaded from sammobiles, also having TWRP and a few xposed modules. A couple of weeks back after my phone's battery died, I couldn't get it past the samsung logo when trying to reboot after connecting the charger. I suspected a s/w malfunctioning and performed a clean flash, rooted again and installed TWRP. It has been working fine since then until the battery ran empty again this morning. The same problem seems to occur again now. On a normal reboot it works just fine.
I have tried removing sd card and trying, restarting through TWRP and connecting to PC for the restart and none of these helped. I bought the phone from UK and have now moved to India so am not sure if I can claim warranty even if I managed to reset the Knox counter to 0.
I came across a similar thread for i9300 where the asker says he had an empty /efs folder. Is that likely to cause this problem and how can I check the /efs on my system now without factory reset. I'm having to reconfigure the phone with every factory reset and is tiresome. Also if /efs was the problem should the clean flash last time not have fixed it?
Thanks in advance,
Vish
Vishwa308 said:
Hi,
I have a SMN910F rooted on stock kitkat downloaded from sammobiles, also having TWRP and a few xposed modules. A couple of weeks back after my phone's battery died, I couldn't get it past the samsung logo when trying to reboot after connecting the charger. I suspected a s/w malfunctioning and performed a clean flash, rooted again and installed TWRP. It has been working fine since then until the battery ran empty again this morning. The same problem seems to occur again now. On a normal reboot it works just fine.
I have tried removing sd card and trying, restarting through TWRP and connecting to PC for the restart and none of these helped. I bought the phone from UK and have now moved to India so am not sure if I can claim warranty even if I managed to reset the Knox counter to 0.
I came across a similar thread for i9300 where the asker says he had an empty /efs folder. Is that likely to cause this problem and how can I check the /efs on my system now without factory reset. I'm having to reconfigure the phone with every factory reset and is tiresome. Also if /efs was the problem should the clean flash last time not have fixed it?
Thanks in advance,
Vish
Click to expand...
Click to collapse
Go to download mode by pressing and holding volume down+home+power, then try flashing the stock firmware again, or if you want boot to recovery first and wipe cache and dalvik and try to boot it again, if not go back to step 1, cheers:fingers-crossed:
Thanks for your reply. I have done it and it's now back to working condition.
But worried that this is continuing to happen every time my battery drains out.:silly:
Vishwa308 said:
Thanks for your reply. I have done it and it's now back to working condition.
But worried that this is continuing to happen every time my battery drains out.:silly:
Click to expand...
Click to collapse
Good to hear mate, you should try calibrating your battery also, use your phone until it reaches 15%, then charge it to 100%, reboot into recovery wipe caches, boot it again, and let it on the charger 20-30 min after its fully charge, and repeat step 1, keep doing this as much as you can, your battery will calibrate and it will improve in longevity, cheers:fingers-crossed::highfive:
Thanks mate. Will do that!!
Sent from my SM-N910F using XDA Free mobile app

[Help]Note 4 Battery draining fast :(

Hello.. I'm sorry for my bad English grammar, if you don't understand, please ask me.
I don't think I understand my phone well so I'll just tell you what happened then.
My note 4 is 1 year old. I think it is Thailand's model as I checked the model number when I'm rooting it.The battery life is long lasting when the first time I got it, I'm not sure when the battery life start to get worse. I'm pretty sure it is happening after Lolipop update, not sure if happens before that. I do not install much games, I do have like 5 or below games from playstore, small sized one. I do installed Clean Master to clear junks when I started feel lagging.
Until recently, because I needed root access to backup my game app data so I went root my note 4 using the odin method. I'm still in my stock firmware. I did faced a problem when Security & Policy update pop out , I did update and it went bootloop(I think it's called that) until I can't access into my phone, I did pull out battery then insert back few times and seems like it rolled back. These few days I was researching how to extend my battery life, I read lots of post said some apps is draining apps as it still not yet adapt to lolipop update? also saying Clock apps draining apps, not even wakelock detector able to detect it. I tried SetCPU and set my CPU below 800 Mhz and even 400min 500max(Just a question, why I didn't see On Demand ? Only Interactive, Performance & userspace) , I did not see any obvious results after doing all these things. Oh , I even went uninstall some bloatwares, I did download Greenify and hibernate some apps.
Now, I'm trying this method to see if it solves the problem. http://forum.xda-developers.com/andr...-life-t3095884
When I was about to Nandroid Backup my datas, to confirm it is it
1. Boot into recovery mode
2. Backup?
But then I couldn't boot into Recovery Mode( Volume Up + Home + Power ) just now, It stucks at boot screen, before the animated samsung appears, just Note 4 with model names something. There's no blue text above, and it just stucked there. The only way to exit from there is pull out battery and insert back again. I'm planning to download QuickBoot and try if can access to Recovery Mode.
Seriously, I don't know much about mobile technology, I just wanted a smooth phone with great battery life. I suggest to stay with the stock firmware, I'm still considering flash it to CM12.1 , people said it help with the performance and battery life, I do not like the interface of it, unless it solves all problems if not I'll not choose to flash into that. (Oh, can I use Odin3 to flash this? Can I use Odin3 to flash every rom? I don't really understand about rooting, is there any newbie guide for these kind of things?)
My questions are:
Can you suggest me few ways to solve this problem?
Is the method does help to my phone?
Why I can't boot into Recovery Mode?
What happened actually?
Edit: Or even factory reset or wipe partition(if I'm able to boot into recovery mode) helps? i did not try it yet.
Thank you for reading this even you can't help me.

N910F stock crash and bootloop after 6.0.1 update

Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!
Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update

Categories

Resources