simple really, everyone says to hard reset when you install a new rom, but at what point do you do it??
i normally wait till it pops up to tap the screen to set the phone up and then take the battery out, reinsert it and do it then.
is that the right time, or can you do it anytime?
sning said:
simple really, everyone says to hard reset when you install a new rom, but at what point do you do it??
i normally wait till it pops up to tap the screen to set the phone up and then take the battery out, reinsert it and do it then.
is that the right time, or can you do it anytime?
Click to expand...
Click to collapse
Personally I do it straight away, i.e. when phone is in splash screen. Just take out battery and hard reset. Obviously only real difference between this and yours is the time waiting for device to initialize to tap screen
so i'm correct in saying that it dosetn really matter when you do it, so long as you do.
in the same vien, why are some cooks now suggest 2 hard resets?
I've noticed in the screen where it says it is setting up you blackstone and there is a progress bar, that it seems like the first reset is quicker and the second and longer. I think that just insures stuff gets installed correct. There may be remnants of other ROMs still there that could cause issues.
I do mine after it has got to the Windows splash screen. I then do a factory reset.
Personally I flash straight from the SD card, so I get a white screen says "Update Done" when flash process is complete.
(in my case it doesn't automatically takes me to splash screen).
Then I take the battery out and perform first hard-reset. Right after I set up everything and i get the manila screen,
I perform a second hard-reset.
Normally I do it straight after it finish flash and the first screen when it start up..
sning said:
... why are some cooks now suggest 2 hard resets?
Click to expand...
Click to collapse
In most cases, some members just want to make sure. I always do the one hard reset with no issues. Mind you, I also use the mtty tool as well before flashing but that's just me....
I actually do the hard reset before flashing... since it is just to remove any traces of the old sys from RAM, it shouldn't really matter if one does it before or after flashing.
Plus: I don't have to watch the flash process and can just leave the phone unattended.
Semicuda said:
I actually do the hard reset before flashing... since it is just to remove any traces of the old sys from RAM, it shouldn't really matter if one does it before or after flashing.
Plus: I don't have to watch the flash process and can just leave the phone unattended.
Click to expand...
Click to collapse
Actually Hard Resetting After a flash is highly recommended, not before. Although it won't hurt to hard reset before, however it will not help avoiding bugs unless you hard reset after your flash.
Care to explain why? The non-ROM parts are cleared either way, and I have yet to encounter any bugs that are fixable by hard-resetting again...
Semicuda said:
Care to explain why? The non-ROM parts are cleared either way, and I have yet to encounter any bugs that are fixable by hard-resetting again...
Click to expand...
Click to collapse
i cant explain it, but a HR has cured some bugs for me. (i've had bluetooth fail to work on cooked roms; HR fixed it).
for the 20seconds it takes, why not! saves you having to spend 30mins later on reconfiguring/reinstalling
There seems to be a belief by many uneducated users in these forums that multiple hard resets somehow make a difference, or that there may be bugs/issues with phones that haven't had a hard reset done to them after flashing.
Somehow, people have it in their mind that the reset that the phone does after the flash has been done >doesnt< totally clear out the RAM/ROM/memory of the device, and that traces remain of the previous ROM, or perhaps bits in memory are not set correctly.
This doesn't happen. Phone memory isn't made of putty or clay. Flashing a stock phone with a cooked ROM doesn't leave some bits of memory set with their old values. Flashing a phone with a ROM that's slightly smaller than the previous one doesn't leave those extra bits unset. Hard resetting a phone multiple times doesn't miraculously reset "stuck" bits that didn't quite get flipped earlier.
Sorry people, but memory doesn't work this way. ROM and RAM in your phones doesn't somehow act differently than ROM/RAM in any other computer. These beliefs are almost always generated by people that aren't quite clear on what actions they are following when flashing their phone. They may be installing additional code after flashing, making configuration changes, or have an auto-install feature active. Or their phone performs different actions based on their location, native language, or carrier. Or the phone's radio ROM interacts differently with the new ROM.
All of these can cause a newly-flashed phone to act unpredictably. NOT because they didn't hard reset their phone twice. NOT because they didn't flash their phone back to a base ROM before updating to a cooked ROM.
When a phone is flashed, ALL memory (ROM + RAM) is re-initialised, regardless of the new ROM's size. There are NO traces of previous ROMs remaining in memory. Safeguards in the flashing process ensures that the code being flashed does not have errors in it. The flashing process also checks for errors in the phone's memory chips to ensure that no hardware errors exist.
These are fundamental activities that happen during all flashes on all phones. There simply isn't any way for a flash to "not quite work". It either completes successfully and reboots, or it doesn't complete successfully and you brick it or are forced to try again.
Resetting a newly flashed phone multiple times is pointless and is simply an act of the uneducated masses rubbing their lucky rabbit's foot or praying to their deity. Do it if you like, but please don't post messages instructing others to do so because it's a necessary step. It's not.
douginoz said:
There seems to be a belief by many uneducated users in these forums that multiple hard resets somehow make a difference, or that there may be bugs/issues with phones that haven't had a hard reset done to them after flashing.
Somehow, people have it in their mind that the reset that the phone does after the flash has been done >doesnt< totally clear out the RAM/ROM/memory of the device, and that traces remain of the previous ROM, or perhaps bits in memory are not set correctly.
This doesn't happen. Phone memory isn't made of putty or clay. Flashing a stock phone with a cooked ROM doesn't leave some bits of memory set with their old values. Flashing a phone with a ROM that's slightly smaller than the previous one doesn't leave those extra bits unset. Hard resetting a phone multiple times doesn't miraculously reset "stuck" bits that didn't quite get flipped earlier.
Sorry people, but memory doesn't work this way. ROM and RAM in your phones doesn't somehow act differently than ROM/RAM in any other computer. These beliefs are almost always generated by people that aren't quite clear on what actions they are following when flashing their phone. They may be installing additional code after flashing, making configuration changes, or have an auto-install feature active. Or their phone performs different actions based on their location, native language, or carrier. Or the phone's radio ROM interacts differently with the new ROM.
All of these can cause a newly-flashed phone to act unpredictably. NOT because they didn't hard reset their phone twice. NOT because they didn't flash their phone back to a base ROM before updating to a cooked ROM.
When a phone is flashed, ALL memory (ROM + RAM) is re-initialised, regardless of the new ROM's size. There are NO traces of previous ROMs remaining in memory. Safeguards in the flashing process ensures that the code being flashed does not have errors in it. The flashing process also checks for errors in the phone's memory chips to ensure that no hardware errors exist.
These are fundamental activities that happen during all flashes on all phones. There simply isn't any way for a flash to "not quite work". It either completes successfully and reboots, or it doesn't complete successfully and you brick it or are forced to try again.
Resetting a newly flashed phone multiple times is pointless and is simply an act of the uneducated masses rubbing their lucky rabbit's foot or praying to their deity. Do it if you like, but please don't post messages instructing others to do so because it's a necessary step. It's not.
Click to expand...
Click to collapse
nice,thanks
@douginoz - thats exactly what i beleive too (or used to!)
however as i mentioned before, i had issues with a cooked rom (wifi or bluetooth wouldnt work correctly)
a HR cured it.
now this could of been a bad initialization of the rom from the get-go, however based on the fact that a flash resets the phone completely, it didnt correctly work *immediately after the first flash*.
weather it's placebo affect, i dont know but i've also experiencing slightly slower performance on no HR rom, vs a HR after rom flash.
as always, a bad install could happen at any time. i'm merely going off my own personal experience between doing a HR and not doing one. no HR after rom flash has given me atleast 2 issues. HR after flash has NEVER given me an issue.
Related
Recently, my phone has become very unreliable and crashes, requiring a soft reset, every few hours.
And to make things much worse, the phone never wants to turn back on again. I have to take the battery out, replace it, and try to turn it on again, about 20 times before it actually vibrates and turns on.
Happens on several ROMs, including 1.66 with stock bootloader, so I'm pretty convinced its gone defective.
Also the phone has a habit of getting very warm when it crashes, and the battery doesn't last very long at all.
Had the phone since the start of December, so what are my options in sorting this out? Bought from mobiles.co.uk
Will Vodafone replace it, as I've heard they no longer stock the HD2, and offer Nexus One as a replacement. Is the nexus one worth having? I don't know much about Android.
sound like you have flashed several roms? you should give mtty a try. find the mtty sticky in the rom development section.
Sorry but what does MTTY actually do?
different roms are different lengths.when you flash a new rom it doesn't erase the old one just flashes over the top.this can leave data from the old rom "sticking out"past the end if the new rom, leading to instability.
mtty formats the rom memory ready for a new rom.
I always perform a hard reset after flashing, so will this still have affected me?
Hard reset doesn't wipe the rom chip. It just reloads the rom from scratch.
Mtty may not help you, yours may be a different issue, but instability and boot problems are symptoms of exactly what mtty prevents.
samsamuel said:
different roms are different lengths.when you flash a new rom it doesn't erase the old one just flashes over the top.this can leave data from the old rom "sticking out"past the end if the new rom, leading to instability.
mtty formats the rom memory ready for a new rom.
Click to expand...
Click to collapse
Thanks for that! Despite endless threads re: MTTY, this is the first simple explanation I've seen.
If you are running apps installed to mem card then try a boot without the card.
The heating up sound like a result of "hard work" by the phone and if you run apps from mem card the current draw is significantly increased.
If this is the prob then don't install anything to mem card that you don't have to. They have been known to cause exactly the symptoms that you report + more apps on card and greater access to them reduces the overall speed of operation which can cause freezes and resets!
first things first: the hd2 is my very first windows mobile device. i've already read the wiki and searched the forum/the internet for help, but i didn't find a solution for my problem. i'm also not a newcomer when it comes to flashing (i've gained some experience from my psp/wii/nokia n82/creative zen).
so i got my htc hd2 a few days ago and one of the first things i tried was flashing a rom (i didn't like the t-mobile branding).
i had absolutely no problems installing hspl (this forum was very informative) and flashing the artemis rom (i strictly followed the instructions), which i found in the rom developement sub forum. since everything seemed to work fine, i started adding my contacts and some applications, still no problems.
but after a while one of the apps seemed to have crashed and the phone became unresponsive.
i removed the battery and turned my phone back on, but it was stuck in the boot screen (the very first screen on which it says "r g d" in red at the bottom). since i didn't know what to do, i simply flashed the artemis rom another time and so the story repeats: at first everything worked fine and after a while the phone got stuck again.
after 4 tries i decided to switch to the shock star r9 rom (also found on xda), which also seemed to work fine at first, but it didn't take long for the phone to freeze again. i took out the battery again and turned the phone back on. this time (to my surprise) it didn't get stuck on bootup, but instead it (automatically) performed a hard reset. the phone now does a hardreset everytime i turn it back on, which makes it pretty much unusable...
since i'm getting REALLY tired of adding my email accounts/favorites/application shortcuts (by now i'm just installing them on the sd card, so i don't have to reinstall them)/facebook associations for my contacts/etc and i thought i'd better ask for help.
does anyone know what causes this issue and/or how i can solve this problem? help would be appreciated!
and since i'm here, what should i use to backup my phone (once it's running perfectly)? i already tried pim backup (sadly it doesn't create a backup of everything) and spb backup (freezes on registry recovery). would it be possible to create a rom that contains ALL of my information (settings/contacts/favorites/applications/registry tweaks/...)?
tl;dr:
my hd2 automatically performs a hardreset on bootup, how do i fix it?
please ignore any grammar errors, i'm tired and not a native english speaker
I have the same problem exactly regarding self-hard-reset. I still did not find any reasonable cause for this problem which is starting really to push on my nerves
This sounds to me like a corrupt file system, which can happen after ROM flashes. I would try this:
http://forum.xda-developers.com/showthread.php?t=644781
@Moandal: thanks for the answer. i just flashed the shock star rom again and the phone boots up normally again. but i really doubt that it will stay like this, unless i know what caused the problem. next time it happens, i'll try the program from your link.
but if i'm not mistaken, that program also hardresets the phone (correct me, if i'm wrong), so i could just flash a rom instead and that's what i'm trying to prevent (as i said, i don't want to have to enter my personal stuff again and again and again...).
what exactly could cause a corrupt file system? could it be a problem with the rom(s) or am i just doing something completely wrong?
A "simple" custom ROM flash only overwrites the ROM's contents without prior erasing, which on the HD2 has been found to sometimes cause trouble like the continuous hard resets you've suffered.
The solution is a full erase of the ROM before flashing the new ROM, which this mtty command does. So, you obviously can't do it without hard resetting/reflashing.
@kilrah: ok, that made things much clearer. i'm going to use the program posted above and flash the rom again, i hope that will fix future issues.
thanks for the fast help, guys
I had the same issues, at first I thought it was the artiums rom but having done MTTY walkthrough I'm 1 week into the Miri rom without much issues (apart from the odd program crash)
since it started pretty much straight away on the first rom, id be a little concerned that it might be an issue with the phone.
if it continues after you mtty/task 29 then id flash back to stock, including spl, and monitor that for a few days.
Code:
@samsamuel: since my last post the phone crashed only once (i was using opera 9.7 when it became unresponsive again), but this time it didn't perform a hard reset!
the main issue seems to be solved and that's good enough, for the time being.
if the problem occurs again, i'll follow your advice.
opera 9.7 - have you moved the cache to the memory card? I've had a lot of freezes the last few days with opera 9 7, turns out it was cos the cache was on the sd card (default 2 gig that came with it).
moved the cache to the phone yesterday, not a crash in 30 hours.
no, but i was actually going to. won't do it now, obviously
please help cause it went crash and hardreset by itself over again..... how can I fix this??
Ahoy, beloved XDA!
I never thought I'd end up posting something like this, but it seems that my phone is near-screwed as of this last month. I've held off jumping the question for as long as I could, but one failure after another has lead me to this.
My HTC HD2 has become unstable. It first manifested in my phone shutting down at random and getting stuck on a white screen (while nothing had changed for months), and now it can never hold a fresh installation down for longer than a day.
I've done multiple fresh from-the-ground-up installs. I installed the stock ROM through my microSD-card, which will fail 24/25 times before finally allowing the Radio to be overwritten.
The steps I take:
Reinstall stock through SD-card
Install HSPL
Task24
Install Radio 2.15.50.14
Install MAGLDR
Install CWM
Flash ROM
The Task24 step also includes Radio installation, though skipping the additional radio installation step doesn't change the outcome.
Completing these steps usually allows me to use my phone for about half a day or so before it begins to randomly freeze or reboot, ultimately leading to the phone never getting past the white screen.
Is there anything I can try to do to get things fixed?
Try to use the phone in Stock mode (Winmo stock) and see if you face the same symptoms, just to eliminate the hardware defect possibility .
Ah yes, I intended to do this earlier but looking at WinMo made me a bit too impatient to wait with installing Android.
I'll do so now and I'll keep you updated.
Hey guys, i received a Samsung Focus i917 rev 1.3 from a guy who wanted to put that phone back to factory state. Im dont have a lot of experience on windows phones other than the HTC versions. Anyway, i performed a factory reset on the phone but the data didnt deleted at all. Now, i understand as far as i know that those phones need the SD card in order to work fine. That phone didnt have one, but it was working though. Thing is i decided to flash it with stock ATTJK2 and when i flashed it everything went fine. But the phone now stays on the Samsung logo for some minutes and reboots. When i say this case is different is because i can get to download mode as many times as i want, i can perform factory reset using hardware buttons and everything. In fact, i even installed MAGLDR and a custom rom trying to solve this but even though everything went well phone is still stuck on that logo. So my question is, should i insert a working SD for that phone and then flash it? Is it worth the try? Or is this phone just a brick? Cus my guess unbricking it wont solve it since the phone can reach download mode.... Help please and thanks for your help as always
enelyam said:
Hey guys, i received a Samsung Focus i917 rev 1.3 from a guy who wanted to put that phone back to factory state. Im dont have a lot of experience on windows phones other than the HTC versions. Anyway, i performed a factory reset on the phone but the data didnt deleted at all. Now, i understand as far as i know that those phones need the SD card in order to work fine. That phone didnt have one, but it was working though. Thing is i decided to flash it with stock ATTJK2 and when i flashed it everything went fine. But the phone now stays on the Samsung logo for some minutes and reboots. When i say this case is different is because i can get to download mode as many times as i want, i can perform factory reset using hardware buttons and everything. In fact, i even installed MAGLDR and a custom rom trying to solve this but even though everything went well phone is still stuck on that logo. So my question is, should i insert a working SD for that phone and then flash it? Is it worth the try? Or is this phone just a brick? Cus my guess unbricking it wont solve it since the phone can reach download mode.... Help please and thanks for your help as always
Click to expand...
Click to collapse
You can definitely try inserting a SD card and see. I'd say it's definitely worth trying. It would be best to match the original SD card it had, if possible. But even so, remember it's not guaranteed it will work.
If you'd search the forum for "stuck in loop" or "stuck at samsung logo" you'd see it's not a rare problem, unfortunately.
I have same problem with two different phones, the one started with be stuck in the loop. No matter what I have tried it will not break the loop, everything flashes fine but never boots. Second one started out working, but factory default wouldn't completely clear data. Very odd...
Well, seems like these phones are not worth a penny then. Its incredible that something like that could happen to a smartphone, So many things that go wrong with them, Im going to put them in the no no list togheter with the Razr. Worst phones to deal with... And yes ive seen its very common to find this issue. Which is why i think theyre worthless
enelyam said:
Well, seems like these phones are not worth a penny then. Its incredible that something like that could happen to a smartphone, So many things that go wrong with them, Im going to put them in the no no list togheter with the Razr. Worst phones to deal with... And yes ive seen its very common to find this issue. Which is why i think theyre worthless
Click to expand...
Click to collapse
I'd say that is your experience and your perspective. Normally, you are NOT supposed to flash custom ROMs and you have been warned that if you do it you RISK bricking your phone. This is a new platform and the process of flashing is not yet 100% understood.
I've warned folks several times about flashing MAGLDR, it seems that only *some* phones have this "stuck" issue and in 99% cases they are related to flashing custom roms. To add more, no one has a fix (not even the guru's), which tells me the issue is most likely unfixable by software (much like an old bios reflash, might require taking out a chip). It might be a later batch of phones that use a specific chip, it might be something else. Point is you're flashing something on your own risk. And saying the phones aren't worth a penny just because you don't want to accept the risk of doing something potentially dangerous is a bit stretchy. And that's my perspective. To add on that, all phones should be looked for the capabilities and what they do, not just for modding. Focus has a replacement for the custom roms, you can achieve the same by installing packages yourself, without unnecessary risks.
Well, im sorry if something was misunderstood. I didnt mean to hurt feelings in here M8. But the thruth is that the phone was completely stock, i just wanted to delete the old data. So decided to flash it with official ATT firmware, it wasnt custom firmware. But since the phone didnt wanted to delete the data after factory reset(which for starters its odd) i tried flashing it and it flashed perfectly according to the flashing software. But it was stock Att, and the phone got stuck in samsung logo after the flash. Never made it further, i mean its not an unusual issue around here so thats why i said that. After that happened is when i tried to install MAGLDR, which installed perfectly also. But when i tried to flash a rom the phone just did the same, stuck in samsing logo also. In fact, i can still flash whatever i want on it, it goes to download mode perfectly, but no matter what i flash on it, it will stay on the samsung logo after that... Anyway, my bad on saying that those phones are not worth it. There maybe more people willing to have a phone which they wont know if it will boot when they turn it off, or maybe not delete their data when they wan to factory reset the phone. Im not one of those thats all. But i do respect your work dont get me wrong, its just that some odd situations like this makes people think twice when buying a phone.
Right mate, I get your point. No harm
If it makes any difference, happened to my wife's phone during normal Zune update, got the logo-loop. Was fixed by reflashing stock rom. Painful, but it worked. In your case it seems something was wrong with the flash, not being able to delete data after factory reset is indeed at least weird. Sorry you had a bad experience, I guess some of those happen every now and then...
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.