I've read a couple times that after rom upgrade one should hard reset.
What is the and is it really necessary? If yes when should I do it after all settings and customization is finished or immediately after flashing finishes?
Thanks
mosec said:
I've read a couple times that after rom upgrade one should hard reset.
What is the and is it really necessary? If yes when should I do it after all settings and customization is finished or immediately after flashing finishes?
Thanks
Click to expand...
Click to collapse
Hi there.
Well I will point this out, if you don't do it. Your rom (that maybe is bugfree), can contains some strange bugs. And when you ex. say it to a cook, he can't figured out of the problem, because he don't have it
I always do this.
Put diamimg on internal storage.
Flash the phone.
Hard reset it, right after.
Now you phone is ready
Related
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
ezsoulja said:
any time now on any rom, i'll soft reset my phone and all of a sudden it goes to the windows mobile start screen with the screen calibration.. (basically a hard reset to a clean os)
how do i fix this, i been trying to find a solution to this problem for some time now but haven't got a concrete find for it
Click to expand...
Click to collapse
I am sure I have advised this when you wrote on one of the threads. Try flashing a shipped rom first, it is in my 4shared, doesn't matter if you have AT&T 8525 or not as it works for my jasjam. Flashing too many radios may kill your phone. So ... flash that and then flash the one you want ..
I have not in my time flashing my phone and my customer's phone that a soft reset causes a hard reset after following the doctors instructions
i will try that but what does the regular att rom have that customs dont to stop this from occuring
ezsoulja said:
i will try that but what does the regular att rom have that customs dont to stop this from occuring
Click to expand...
Click to collapse
As I mentioned no issues for me yet touch wood/knock on wood as your part of the world probably accustom to.
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
it has something to do with the big storage/non big storage flashings etc and that shipped rom sorta resets it all to an acceptable state to the phone's brain so to speak .. the doc's never wrong
ezsoulja said:
ok so far so good, no more hard resets but i just wondered what the original att stripped rom is actually doing to stop this from happening and how much more to reflashing the roms before it happens again..
Click to expand...
Click to collapse
In a normal rom, the flash rom is split into two pices, ext rom and storage rom.
In a bigstorage rom, this boundery is removed.
Now, over time, this causes instability in the way windows access and manages the rom, leading to data loss (random hard resets).
Flashing a OEM rom with a OS partition and a Ext rom parition acts as a spring clean on the memmory layout, thus, stability.
As with windows, most things are solved by formating your HDD and starting again, its the same kinda thing!
Great.. Thanks guys, im back to normal now with no hard resetting.
I think I've managed to semi brick my phone. I was playing around with flashing my phone with some roms and also tested out Android. I've had my phone for months now, and have flashed many times with no problems.
My problem - after using the phone somehow the phone storage gets corrupted and I can't run any programs. The start button and settings don't work. This is fixed by a hard reset.
Anyone else had this??
Now hat are you finally have and after this problem happened, did you try a different ROM?
yep, tried a different rom. first I had udK's beta 5 ROM. i thought it was that so I tried AZTOR v7. but the same thing happens. The phone storage seems to eventually get ocrrupted and the phone won't boot up or randomly boots up as If I did a hard reset but then touchflo won't install properly and only a proper har reset will cure this (for a short while)
benssson said:
yep, tried a different rom. first I had udK's beta 5 ROM. i thought it was that so I tried AZTOR v7. but the same thing happens. The phone storage seems to eventually get ocrrupted and the phone won't boot up or randomly boots up as If I did a hard reset but then touchflo won't install properly and only a proper har reset will cure this (for a short while)
Click to expand...
Click to collapse
i had a similar problem in udk beta 3 or 4, then i went back to stock rom and its all good now (but after that i change the rom every couple of days - rom junkie)
and also, as far as i know, the phone is not bricked as long as it can enter in boot loader mode.
its eather bricked or not.
nblakqori said:
i had a similar problem in udk beta 3 or 4, then i went back to stock rom and its all good now (but after that i change the rom every couple of days - rom junkie)
and also, as far as i know, the phone is not bricked as long as it can enter in boot loader mode.
its eather bricked or not.
Click to expand...
Click to collapse
Thanks. Seems your right. I've flashed the stock Orange ROM and it all seems to be okay now. seems you can't semi brick you phone
benssson said:
Thanks. Seems your right. I've flashed the stock Orange ROM and it all seems to be okay now. seems you can't semi brick you phone
Click to expand...
Click to collapse
Furthermore I suggest you the complete hard reset, including the internal memory. It solved me a problem with stability of the operative system.
paolo the doctor said:
Furthermore I suggest you the complete hard reset, including the internal memory. It solved me a problem with stability of the operative system.
Click to expand...
Click to collapse
Thanks, The stock rom seems to be working well anyway but I'll give that a go.
Of course it is always recommended to do a hard-reset after flashing a new rom.
Now I was just wondering WHEN it should be done.
Should I flash the rom, do the set-up (time, auto-configuration et cetera) and wait until it's really running for the first time or should I do it right after flashing without waiting for the whole set-up thing?
I do it right after flashing. I don`t know is it right, but everything seems to work fine.
cerisu said:
I do it right after flashing. I don`t know is it right, but everything seems to work fine.
Click to expand...
Click to collapse
Yep, that's right.
Okay, thanks.
beckbln said:
Of course it is always recommended to do a hard-reset after flashing a new rom.
Now I was just wondering WHEN it should be done.
Should I flash the rom, do the set-up (time, auto-configuration et cetera) and wait until it's really running for the first time or should I do it right after flashing without waiting for the whole set-up thing?
Click to expand...
Click to collapse
Wouldn't the hard reset wipe all the config anyhow? You'd be stuck in a loop forever.
Will hard reset format the Internal Storage?
Can i just click the Clear Storage command in the WM6.1 Settings?
Is that the same?
When hard-resetting, you'll get the option to format the NAND or leave it intact.
I've seen people say to flash a stock ROM before flashing a cooked one - why? Surely all the data from the last ROM is overwritten by the cooked ROM anyway, isn't it?
iridium21 said:
I've seen people say to flash a stock ROM before flashing a cooked one - why? Surely all the data from the last ROM is overwritten by the cooked ROM anyway, isn't it?
Click to expand...
Click to collapse
I'm not sure about the TP2 but on the hermes it was always recommended for going from an extended storage rom to a normal rom. Might have just carried over since then.
Doesn't make a difference, its a myth. The flash chip gets rewritten.
petard said:
Doesn't make a difference, its a myth. The flash chip gets rewritten.[/QUOTE
If custom ROM without radio You should flash stock ROM first(if you would like to have it)
Click to expand...
Click to collapse
petard said:
Doesn't make a difference, its a myth. The flash chip gets rewritten.
Click to expand...
Click to collapse
Not a myth, at least to some devices like the diamond, HD and the HD2 where members who decide to skip this step are finding themselves with very unstable devices that often turn off or restart on there own.
Flashing a stock rom or using the mtty tool erasers any artifacts that can be left behind when flashing cooked roms.
Flashing Procedures I use:
• flash stock rom or mtty tool found in sig.
• flash cooked rom
• hard reset twice
Never had any issues from automatic resetting of any kind!
ive been flashing since the wizard, and probably after 20 phones ive never flashed stock rom first. i actually stop hard resetting to.
intruda119 said:
ive been flashing since the wizard, and probably after 20 phones ive never flashed stock rom first. i actually stop hard resetting to.
Click to expand...
Click to collapse
As mentioned, some devices are more prone to it perhaps. There are a lot of threads that speak to members dealing with device resetting and other glitches and the remedy recommended is always the same.
For me, it's just habit now....
Only do this as a last ditch effort. Say u flash a custom rom, hard reset as u should, then configure the rom. But u seem to be getting odd screen freezes and problems that only u seem to get and not anyone else for that particular rom. U go into the thread of the rom asking and everyone says its just u. Well at this point u would flash stock rom, hard reset, flash same custom rom, hard reset, now the custom rom works perfect! Why? How th hell should i know? I just know what works!
I think that flashing a whole stock ROM each time is a bit over the top. If you want to be on the safe side, then do a hard reset on your old ROM, then flash the new ROM, then hard reset again. That should do as much as flashing the stock ROM would do.
I think main the benefit is because the CustomRUU doesn't perform a Hard Reset after flashing, where as the Stock RUU does.
Some people prefer to do a "task 29" nand format. Unless you've been flashing dodgy ROMs that go outside of where they are meant to then I think you'll be OK.
JM2c's
Dave
DaveShaw is the man so take his advice.
I have flashed over 40 ROMs (all from XDA or HTC) on my TP2 and I never flash back to stock. I have had no issues. I also did the same with my Tilt1.
had my wildfire s about 4 months been rooted with stock rom for around a month.
past few days while texting it seems to be running really slow, like 3 words behind my typing.
tried slowing my text speeding but still seems to crash then wake up and type on its own.
cleared space from 22.5mb to 61mb of rom but still slow.
move apps to sd card, and ran a memory clearer in settings
no background, no fancy apps running, just Lookout security.
any help or info will be thanked?
emokid09 said:
had my wildfire s about 4 months been rooted with stock rom for around a month.
past few days while texting it seems to be running really slow, like 3 words behind my typing.
tried slowing my text speeding but still seems to crash then wake up and type on its own.
cleared space from 22.5mb to 61mb of rom but still slow.
move apps to sd card, and ran a memory clearer in settings
no background, no fancy apps running, just Lookout security.
any help or info will be thanked?
Click to expand...
Click to collapse
Did you try a factory reset?
Sometimes when you flash a new ROM (usually when battery is low) it can be sluggish, a factory reset usually sorts it out....
Failing that, sounds like the dreaded lockscreen bug that plagued 2.3.3
there is a solution here somewhere, if I can find it I will link it.....
Found it, if the factory reset does not work, try this, worked for me :
http://forum.xda-developers.com/showthread.php?t=1436314
Ko_Ka said:
Did you try a factory reset?
Sometimes when you flash a new ROM (usually when battery is low) it can be sluggish, a factory reset usually sorts it out....
Failing that, sounds like the dreaded lockscreen bug that plagued 2.3.3
there is a solution here somewhere, if I can find it I will link it.....
Click to expand...
Click to collapse
i did download an app called No lockscreen.
it was fine before.
factory reset will loose root will it not?
guess il have to back-up my contacts and give it ago.
fed up with the phone to be honest, should of got a nokia 6230, nothing ever went wrong with them bad boys lol
and thanks for the link, will save it to desktop just incase i need it
emokid09 said:
i did download an app called No lockscreen.
it was fine before.
factory reset will loose root will it not?
guess il have to back-up my contacts and give it ago.
fed up with the phone to be honest, should of got a nokia 6230, nothing ever went wrong with them bad boys lol
Click to expand...
Click to collapse
What ROM you using?
Shouldnt lose ROOT if it is pre-baked in the stock rom....
Ko_Ka said:
What ROM you using?
Shouldnt lose ROOT if it is pre-baked in the stock rom....
Click to expand...
Click to collapse
just stock rom, have been tempted to put custom rom on but darnt do it. just going to back up my contacts now then do a restore
hmm wfs cant find htc sync on my pc, even though its all open and on, just a guess but i think i have a virus/malware on it.
must be a dodgy app.
time to factory reset and get it back up and running i think.
will post back if it works. thanks
Ko_Ka said:
What ROM you using?
Shouldnt lose ROOT if it is pre-baked in the stock rom....
Click to expand...
Click to collapse
ok, ive factory reset, at the moment all seems fine, still rooted too which saves me a good amount of time i will reply later along the weeks if it ever does it again. thank you