Related
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.
Hey guys, I am kind of a noob but have successfully been hacking with my Touch for a while now...or so I thought. I flashed to the 3.37.78 radio a while back and have been keeping up with NSFAN's ROM's for over a year now with no problems....until a few months ago. My phone locked up and I had to soft-reset but to no avail. It got stuck on the startup screen and would not do anything so I did a hard reset and all was good. Then it happened again weeks later. Now it has been happening a lot more recently. I will be texting or on the internet with it and then all of a sudden it will lock up, I do a soft reset and it will hang up either on the startup screen or seem to boot up but then contacts will be missing and there will be no signal. Sometimes the today screen will show but I cannot do anything on it.....all of this requires a hard reset to fix. This happened after I flashed NSFAN's latest ROM so I flashed back to some of his older ROM's that I had no problem with in the past and still the same problem. It has been happening every week or 2 now to the point that I can't even bother setting up the phone the way I want because I know it will happen again. Can any of you guys tell me what the problem is? I really need to get this resolved because I am losing information everytime. Please help!!!
Im a GSM Phone user... and as a general rule, if things start to go wrong.... Flash the OEM rom. That would be the stock ROM. And then flash back to your "custom" rom... Ive had to do that with my phone(s) as well.... It basicly puts things back to 'ground zero'. BUT. Use the phone with the stock rom for a day and see if you still have the same problems... it may be a problem in the phone. In which case you may need to replace and/or send the phone back for replacement to your carrier.
Hope this helps....
Thanks for the reply.....What I ended up doing is reflashing my radio to the 3.42.50 version and then reflashing my ROM to NSFFAN's again. So far so good. I am really hard on my phones and the fact that I drop my phone on a regular basis can't help either....I just need it to last me a few more weeks until I get a new one. Thanks again...
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.
Hi,
I am reading from time to time here at xda about random reboots issue with ZUK Z1, so here is my short story.
I am the user of ZUK Z1 since last year at the time there was only COS12.1 and CM12.1 available. The phone was working great for the first few months, no single random reboot, even with heavy usage and tons of root tools like xposed framework, greenify (with exp. mode), amplify and other experimental tools etc. Rock solid stability, CM12.1, ZUI, COS12.1, no matter which one.
Some day, somewhere beetween feb/march this year I started to see occasional random reboots, sometimes once a week and sometimes three times a day. After the last one of this random reboots, the phone refused to boot. No recovery mode, no charging screen, no fastboot, even no access to qualcom recovery port for use with QPST and QFIL tools.
Tried to drain the battery and charge again with no success, tried to soft-restart by power button - no success. The thing that helped after phone sitting on desk for next three months, was to dissassembly the phone and reconnect battery. After this, the phone boots up again, bot the random reboot issue is back, no matter CM12.1, CM13 or COS12.1
And now the questions time:
The question is, is this a software issue after some of the updates or hardware issue?
Are there users with the random reboots problem with the newest firmware?
How to debug and catch this random reboot on the logs without ADB connected to see what is going on?
What have i done to fix the issue:
- reflash phone many times with different versions of COS12.1 and CM13
- flash fresh .zip from recovery
- flash directly from fastboot with official COS images the support page
- fsck, partirion check for errors, etc.
- formated phone by QFIL tools
- tried to track the problem from logs, but so far no value information are stored after reboot
What i am going to do:
- install ZUI 1.6 to verify that the issue comes back
- as much as i can, use the device with ADB logcat connected by cable, to catch the occasional reboot
- recompile kernel with enabled options to store crash reason after reboot ( kernel pstore feature or last_kmsg )
I am in the same situation as you, investigating....
Please update your results, very interested to find if software or hardware problems....
Thank you.
Carlos
Are you restoring apps after you flash your phone? If so, try not to. Just install basic apps you need and see if problem persists, since Google restores app with it's data.
Phone rebooted in recovery, so I think it's a hardware problem.
Phone is traveling to China again.
After what perio of time your problems started? I have my z1 for 2 weeks and it works perfect. I keep it on heavy usage for a few hours daily.
Fenomen007 said:
After what perio of time your problems started? I have my z1 for 2 weeks and it works perfect. I keep it on heavy usage for a few hours daily.
Click to expand...
Click to collapse
Phone arrived 25th may, 20 days with no problems, reboots were increasing to the limit that icons on main screen didnt load, rebooted inmediatly. So phone became unusable.
Hope your unit to be the good one!
errecez1 said:
Phone arrived 25th may, 20 days with no problems, reboots were increasing to the limit that icons on main screen didnt load, rebooted inmediatly. So phone became unusable.
Hope your unit to be the good one!
Click to expand...
Click to collapse
I love everything in that zuk so hope it won't brick. When it happen i will just chargeback money from gearbest
Hello,
I'm in the same situation !
My phone randomly reboots and also freeze (have to do an hard reset).
Have you find any solution ?
I am also having this issue... I will probably send it for the warranty. I have tried a few different roms, even restored back to CyanogenOS and the reboots continued...
I got mine since October, haven't had any reboots so far.
I'm running the latest update from cos without root or custom rom.
Seems like a hardware issue to me, I have tried everything software side.
same issue
I'm also having the same issue,any fixes??
Random reboots just stopped happening on my device a week ago. Before that I was trying different ROMs and flashed different versions of TWRP but the reboots were still happening. Then the reboots just stopped from happening and now everything is working perfect. I think it is a hardware fault. Probably some electronics (cables or what not) on my device are now having contact but were not having it before, I don't know. But if you are experiencing rebooting issues, just send your phone to the repair.
Any fix to this?
Whenever I do dirty flash, my zuk z1 random reboot twice a week. It is highly recommended to do a clean flash if you want to avoid random reboot.
Clean flash = No random reboots. @sebeqone