Related
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.
It will not charge, turn on, connect to pc even while using power+back button.
It's around a month old, i flash it 2 times with Floyo v0.20 using xrecovery. it has been dropped about 4 times... i attempted to install something which corrupted the os. It then crashed and i removed the battery then attempted to turn back on and it turned on a few times but i was unable to access xrecovery pushing back over and over again. I then attempted to flash using my pc and it came up with some errors and now the phone will not even turn on. I used the X10FlashTool thread that is compatible with the x8. Is the phone completely dead or is there a way to recover it.
Thanks in advance.
NOTE: These errors on the flash program wasn't while it was flashing. It was while it was trying to connect... I don't think the software killed it.
Sorry m8 to here this I have done the same and my motherboard cook it self I hope it not the same for ur phone if so you need a new board m8
my civic
I hope not too, i guess your most likely right .
Try eBay for a bricked phone so it nice and cheap and look online on how 2 replace the screen it show u how to get the motherboard out so u can replace it with the bricked phone.PS I have seen the x8 going for a 5pound becouse it was brick I got the bird a bricked x8 for 20pound
my civic
Hopefully one goes on there soon since i couldn't find any... the phone is on contract so i might be able to get it replaced since i haven't had it that long and really i've done nothing to kill it.
Try to recover it using PC Companion or SEUS
I hope it helps... Good luck bro!
I'm not sure that will work since my pc doesn't even detect it's there.. i don't eve get the sony ericsson screen when i try and turn it on.
If you want to reinstall firmware with SEUS or with FlashTool you don't need to turn phone on. Try to look here maybe this will help you:
http://forum.xda-developers.com/showthread.php?p=12442257#post12442257
I've attempted this also, it doesn't detect the phone. I will give it another attempt in a moment... FINGERS CROSSED. Other wise i will try and get a replacement.
Update: I'm now sending it away for repair, i've tried everything i can find to repair it... It's obviously completely DEAD!
m8 try holding back key(the on on the right )and plug in the usb in at the same time seus should find it just did it 2 my old phone to try and help u
sooooo hold back button and plug in your usb while holding the back key untill phone driver install just done it less than ten min ago ( my old phone didnt turn on no se logo or anything i think this is the same as you and it may help you ps it take a bit of time like 2min to start but it work back to factory 2.1
Okay i will give this a try, Hopefully it recognizes that it's plugged in if i wait.
Mine doesn't even light up when plugged in to the charger or pc.
This didn't work either, i think it's completely dead since it does nothing at all.
I'm sending it away for repair, will they know i used a custom filmware though it's dead?
erm... maybe use pc companion?
I have the same problem. I got my phone back from repair (mainboard was changed) and decided to install the floyo v0.25 ROM. Installed it succesfully, but then my phone freeze and I took the battery out, same as he did also. After that my phone was dead, the SE logo wont appear. I tried to repair it with SEUS, but It didnt change anything.
Flashtool didnt work for some reason, said that I should turn my phone on and enable something..
I installed that rom just before mine broke...
i will stick with 0.20
so 0.25 is bricking everyones phones. Good to know ._.
If I manage to fix my phone somehow I will stay on original firmware. Thanks to the 0.25 developer
One thing ive seen you all state that made it go kaboom more or less is that you remove the battery, also i belive it isnt the FW you put in since im using 0.25 without any hickups or any bugs at all (well battery icon <60% but its fixable).
So don't blame the developer, you put this in with full knowledge it could brick your phone.
Try and think about what you did and what went wrong, because i seriously doubt that you did it 100% like you should, Backup org ROM->Restore 0.25 ROM-> wipe cache->factory reset->reboot into 0.25.
Also on a side note, dont be afraid to root and put in custom ROM, learn something from it instead. every "negative" experience is GOOD experience since you learn what NOT to do then
Best of luck to you all in the future and may the custom ROM gods be with ya !
Mine is partly dead...
Hi all,
A few days ago installed the newer floyo v0.25. For a day or 2,donno how long,but till my battery flatted out completely,did not have any probs with the rom.Than after recharge,think it was not a full recharge,turned on and left it on till next morning. Still everything ok,started music app and could not turn off music (pause) as the touchscreen didnt respond. Nothing helped yet so far to get it working properly.Did a restore,full wipe did a Seus update back to stock Eclair. Now at this point lemme mention that I`ve made service tests and everything was in mint order Yes the touchscreen too.(!) Started to be happy,could do a few things like making calls,navigating within menu,then it just went back to its sad state.Cannot even unlock the screen,as there is no reaction whatsover...No matter which backup am restoring,all of them reproducing the error. Now 2 things I`ve learned so far.
1.) when I installed (restored from xRecovery) floyo v0.25, did an advance restore and restored system only,as it was mentioned in other post,its possible,because I am upgrading from floyo v0.20
2.) did not make a full wipe AFTER restored custom rom.
I donno if these 2 mistakes lead me where I am now,just hoping I need not a new motherboard or dont have any hardware issue.
Sorry for the long post,hopefully someone can learn from it,also could help me to move forward,as am still working on it to make the touchscreen back in properly.
I also had the music issue and touchscreen not responding. After removing the battery and rebooting it worked at first, but then the phone froze and didnt want to reboot after I removed the battery the second time.
There is really no sollution to fix the problem?
So that filmware killed it , thing is my phone was only just over a month old...
I've sent it away for repair will they know i used a custom filmware on the phone?
Since it's dead really they shouldn't be able to find out.
Hi all,
Nasty problem with my 1 month old Motorola Defy+ (MB526)
Last weekend I installed ICS9 from Quarx (20120318 build). I did this using 2ndinit CWM. Made an android backup of my stock setup, I did this over my stock SBF 4.5.1.-134_DFP-74. Used the gapps.zip and battery fix.
The system worked pretty well, but time by time it was unstable. When turned off, it had lots of difficulty to boot up again, lots of reboots and 2-3 battery pulls.
I was planning to flash another ROM when I had the time. Yesterday it worked well, started fully loaded, used it as MP3 for long time, when I went to sleep it was 48% (the accu).
This morning, I stepped in car and phone turned out to be dead. Connected it to my car charger, and it came back to life. However, immediate reboot etc. So I decided to (while driving) put back my stock nandroid backup.
It all turned out well. Stock ROM booted but gave the notice (translation from dutch): "Battery of your device is invalid and cannot be charged. Replace the battery with a battery from your Motorola"
hmm, tried it with my USB cable at the office, and now at home again with the normal charger..
What happened? Any ideas on how to solve this?
The complication is that now my device is rooted and has 2ndinit starter, warranty is more difficult.
Solution: red lens battery fix
I’m not sure it’s exactly the same issue, but my Defy+ totally refuses to charge with Quarx CM9 build 20120318 + CM9 kernel from [1].
Unfortunately I noticed only once the battery was dead empty.
I couldn’t even get it to boot with the USB charger pluged in, and the only way I could get it to boot again was to charge my battery pack in friend’s Defy.
Then I applied the « Battery fix for red lens » provided here [1] which kind of fixed the problem. Now the battery charges again, but it won’t charge over 80/85%.
I had done a « Clean battery stats » from the boot menu after installing CM9 before this whole story, so I don’t know if it had any effect.
If anyone knows better please let me know!
The instability you noticed may be due to the Android debug bug… in CM9 builds. You have to leave Android USB debug (from System params->Debug features, translated from french on, otherwise it will lag like hell most of the time and drain the battery due to the init process eating up the CPU.
[1] http://forum.xda-developers.com/showthread.php?t=1432100
Hi, I installed the battery fix immediatly after flashing the Quarx ROM, so that should not be the problem.
In the meanwhile I have been trying some things with the battery calibration software. That one flawlessy sees that my battery is 100% charged (i did that using the mcguyver method). But, resetting the calibration file on the phone won't help.
In the meantime I have been able to delete all traces (2ndinit boot, titanium backup and unrooted my phone) so I am considering to RMA the phone, no matter the fact how long that is going to take..
Unless, someone here has a last excellent advice..
fokkeh said:
...the mcguyver method...
Click to expand...
Click to collapse
Great! You have just fried your battery (like a few others who tried going McGyver). Get a new battery now and don't use the McGyver method again
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
fokkeh said:
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
Click to expand...
Click to collapse
Well now that your phone is alive, then go to stock and reclaim warranty! Do RMA.!
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
fokkeh said:
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
Click to expand...
Click to collapse
I understand that bro!! Even my phone was away for couple of weeks recently! Just pray they don't flash the latest SBF(BL7_ as they did in mine!
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Puckying said:
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Click to expand...
Click to collapse
Hi, this morning everything changed again, I decided to give it one more try with the latest Quarx CM9 nightly (20120330), wiped data, flashed nightly.zip, gapps and kernel but waited with the battery. After that I wiped cache, dalvik and battery stats.
Reboot and battery seems alive? very strange. But I don't want the kind of buggy CM9 builds anymore, so decided to put back my 2 hours old nandroid backup, using Restore.
Strangly, battery problem was back again. ****! Than just for fun I did data/cache/dalvik/battery stats wipe on stock, and that did not help either.
Now I am back on CM9 again, but thats running O.K. (battery is working!) but not stable enough for me. CM7 (cannot remember which build) gave the problem as well.
With the latter in mind I think (and thus agree with you) flashing a fresh SBF will probably solve the problem, but I am not 100% sure. I want to be able to put back my stock setup for possible RMA. My stock is 4.5.1.-134_DFP-74 and I cannot find that one on internet. And I cannot put it back to stock otherwise right?
The one Pranks gave you in your post (4.5.1-134_DFP-1321) is that a deblurred one? Because when I put a new one, I would like it to be a deblurred. I hate all the bloatware.
I have no idea, but I think he said it was from his own defy so I am guessing it the complete original blurred thing.
---------- Post added at 01:57 PM ---------- Previous post was at 01:31 PM ----------
I redid the cm9 flashing too and now at least it is telling me the battery is charging. But it stays stuck at a big battery icon and a red led is on.
Will see if it goes past that screen with a bit more juice.
---------- Post added at 02:06 PM ---------- Previous post was at 01:57 PM ----------
Yessss, it started up!
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
fokkeh said:
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
Click to expand...
Click to collapse
Cardiotrainer however for me is one of the most imp app!!
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
sounds like a voltage prob....or mem prob... id redownload a new rom..wipe wipe wipe..reinstall and that should fix it
Sent from my SPH-L720 using xda app-developers app
Insufficient voltage at idle was my first thought too, but if you haven't undervolted (since you aren't even rooted), that seems less likely. If I were you, I'd root the phone so I could do more to figure things out. Maybe try bumping up the voltage a little on the lower clock speeds.
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Edit: did you buy this phone new or used? If you bought it used, more than likely somebody ruined it for you. And more than likely, you can fix it. If this was a new device, more than likely it will be a warranty issue. That's why you shouldn't do anything to void the warranty.
If you're going to use odin for anything, just make sure you follow someone's directions step by step. Otherwise very bad things can happen.
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
I'll look into Odin before I root. The phone was also purchased new. I spent most of today monkeying around with different settings to see if I could trigger the issue as well. As it turns out, the phone will only restart at idle if it's plugged into the charger, or the wifi is on. If wifi is off and it's not plugged in it's fine. I am also using the stock Samsung charger that came with the phone. Again though, if I'm actively using the phone it doesn't happen (charging or connected to wifi). I did turn the phone off earlier to charge it but would keep freezing at the sprint logo upon boot up. I thought it was bricked for a second... I wiped the cache (didn't do a factory reset) and that fixed it, but now I have that stupid issue where videos won't play on wifi, only on 4G or 3G. It's an issue I thought I had solved.
Le sigh. This is frustrating. The Odin option is looking to be my best bet it seems.
Tizamarou said:
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
Click to expand...
Click to collapse
Since you are running a custom source-built ROM, first thing to do would be to ODIN a stock ROM. If the problems go away, you have your answer. If not, this would likely be a warranty issue. Of course you tripped KNOX most likely already.
sputnik767 said:
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Click to expand...
Click to collapse
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Dfeeds said:
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Click to expand...
Click to collapse
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
rebooting
i had this problem once and it was related to a corrupt file on my sdcard believe it or not. there are Defraggers out there for your android file system and internal SD card but your Ext sc you would have to do on your PC. it worked for me. the one i used is called CLEAN i got it off amazon app store.
cyberweasal
Dfeeds said:
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
Click to expand...
Click to collapse
sputnik767 said:
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
Click to expand...
Click to collapse
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Dfeeds said:
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Click to expand...
Click to collapse
Great, I am glad it worked out, and hopefully your problem is resolved. I doubt that your old battery failed due to a bad partition, and I have to wonder how your partition got messed up in the first place, but that's just a curiosity and is irrelevant in the grand scheme of things. Just remember that if you decide to root, cf_autoroot works but will trip the KNOX bootloader and potentially void your warranty.
I had Gnabo v8 running fine of my 8013. Then the battery started draining fast and would not recharge. I had the rom, SU, remove phone, and wifi fix all on my ext SDcard.
Wiped and reflashed all using Philztouch recovery.. Got back to KitKat but no wifi. Flashed the wifi fix again. Now unable to do anything. Can't get to recovery. Battery at zero, so can't use USB.
Oh well..........I am in the market for a new tablet. I might try the Note 12 pro, but not unless they release an official Lollipop version.
Try replacing the battery.
I've just replaced my N8000 battery & it looks like new now
There is always a way back. If you have odin you should be able to reflash stock with it.
If you are looking for a new battery take a look at
http://www.amazon.com/dp/B00AFJ5JF2/ref=cm_sw_r_awd_BYbPub1S17QER
A hand full of people have been saying this is an awesome deal!
All fixed
Once I got my charger/cable problem fixed, I charged, reflashed Gnabo, SU, boot, phonefix, and wifi fix.
Back in business. Ordered a backup charging cable, since I know the one I have must be positioned just right
in order to maintain contact at a break in the wire.
Thanks for all the help/comments/advice.
What a great forum.