FLASHING TO STOCK JUST TO FLASH CUSTOM ROM's

[AlexAuran]

Originally Posted by AlexAuran

Apparently there is mass delusion then...http://forum.ppcgeeks.com/showthread.php?t=96190

Let me clarify: I don't think it is a common occurance to have any issue from flashing, but if the potential is there (the thread I referenced was just the first flashing related issue could think of, though I'm sure there are others), and the problem is easily prevented, then I see no reason not to do so.

I have flashed roms without flashing to stock, so I'm not saying it is a procedural requirement, but I personally have had stability issues that flashdancing cured. Not flashing stock may not have been the cause, but flashdancing removed the effect. I still feel it is a good idea.

[AlexAuran]

Originally Posted by austin420

whats up with you editing your comments then removing your edits. youve edited this post about 3 times now. how about just continuing the discussion new posts if you have something to say. we dont all wanna go rereading your every post.

I added the point I just clarified, but when I refreshed afterwards there were posts there, so I removed my edits and made a new post to keep the discussion flowing in order. Relax, I made sure the content is exactly the same as when the others posted for that reason.

[AlexAuran]

Originally Posted by austin420

i still dont think its nessecary either. this thread you linked to is trouble shooting for random hard resets, not telling every one to do this just because. ive never experienced them and i flash about twice a week. ive only flashed back to stock when a rouge cab jankifies my phone. also, i used the elite team rom when they first dropped the hspl, and it changed my splash screen and it wouldnt change back. then i had to flash back to stock. the flash dance is bs.

Based on what you just said, I'd think you'd agree flashing stock would seem to be a good idea then. Custom ROMs are one big rogue cab, and even though it might not jankify your phone to the point it is broken, some things that can slow your phone or give unexpected results *CAN* linger, and provided one quick example. If ensuring that nothing does isn't worth your fifteen minutes, don't do it. YMMV.

That was my two cents, I'm not trying to come off as a jerk or attack anyone, my only point was that flashing stock fixes/prevents some issues. I'm done with the topic.

[edsladey]

if i'm not mistaken, someone said to hard reset, and then hard reset again to make sure you got everything out that shouldn't be there. i wanted to try mighty's updated ROM if it's done so i think i'll give this a go. i THOUGHT i had to flash back to stock but if i don't have to, i wanna hurry up and get the new ROM on my phone!

[cbreze]

I've flashed dozens of times(yeah,I'm a tad compulsive)and have occasionally had issues if I didn't revert to stock first. So my personal rule is stock first then flash. Using this method I have not had issues. I stick with what works for me, takes maybe ten extra minutes. I hate to get all my stuff/settings reloaded the way I like it on a new rom and then start having issues. But thats just me and my $.02. To each their own.

[Paragon]

I have not seen one single speck of evidence, ever, that supports flashing to stock first. Yes, I have read plenty of posts from people saying they had a problem after flashing and they then flashed to stock, then back to the custom ROM, andthe problem was solved. It is much more likely the problematic ROM was corrupted in some way, and by reflashing they fixed the problem. Going to the stock had nothing to do with it....IT IS MYTH that has gained some legs in this forum. Remeber...ROM flashing completely overwrites the chip. The ability to flash at the file level is possible, but not done.

Dave

[animez]

Wirelessly posted (Opera/9.80 (Windows Mobile; WCE; Opera Mobi/WMD-50369; U; en) Presto/2.4.13 Version/10.00)

I have to agree that flashing back to stock seems unecessary. I've lost count of how many times I flashed my last 3 WinMos and I never flashed back to stock. I've never had a random hard reset. I generally will hard reset after my first full boot, but that's about all I do extra.

Originally Posted by Paragon

I have not seen one single speck of evidence, ever, that supports flashing to stock first. Yes, I have read plenty of posts from people saying they had a problem after flashing and they then flashed to stock, then back to the custom ROM, andthe problem was solved. It is much more likely the problematic ROM was corrupted in some way, and by reflashing they fixed the problem. Going to the stock had nothing to do with it....IT IS MYTH that has gained some legs in this forum. Remeber...ROM flashing completely overwrites the chip. The ability to flash at the file level is possible, but not done.

Dave

I'm one such case where flash dancing solved my problem.

I ran the stock ROM for several months... finally caved in and built myself a ROM using calk's kitchen. All was well.

He released a new version of the kitchen and my phone crapped out. tmail.exe would lock up every 20 minutes or so and any texts after that point were lost, I'd have no way to know. The alarm would randomly not work. I had quite a few random problems. It happened with every build I made, no matter what options I chose.

I gave up fighting it after he had two more beta releases of the kitchen with no change. I was still having the same problems which no one else was having.

I flashed malatesta's ROM and didn't have those issues (built with SSK kitchen)... and it worked well for a while till it started locking up about a week later. The lockups got worse till it got stuck at launching Sense, then at the loading windows screen, then finally at the Touch Pro 2 screen. A hard reset brought it back for a day but it wasn't long before it acted up again.

I went back to Calkulin's kitchen because he had a new release. Built a ROM with a brand new sys/xip... Same problems as before!

Got frustrated and flash danced... poof, problems gone. I never used any other ROMs between having problems. It's been 4-5 days without major problems... which is a record since I started having issues almost a month ago. I'm about to make a week without a hard reset, FINALLY

[Paragon]

Originally Posted by ShadowDrake

I'm one such case where flash dancing solved my problem.

Once again, there is no evidence that flash dancing as you call it did anything. Afterall you reflashed what had become a poorly operating device.....Again....remember.....Flashing a ROM completely overwrites a chip. If you fllash to any ROM there is nothing remaining of the data that was on it before.

Dave

[kymikes]

Originally Posted by Paragon

Once again, there is no evidence that flash dancing as you call it did anything. Afterall you reflashed what had become a poorly operating device.....Again....remember.....Flashing a ROM completely overwrites a chip. If you fllash to any ROM there is nothing remaining of the data that was on it before.

Dave

As a relative newcomer (a few months and 6 - 7 ROM flashes), the opinion as I have read it is that there is some difference in the 'flash' process on a 'signed' ROM (stock) and an unsigned ROM (custom). MightyMike had suggested the 'flash dance' toward the end of last year on the MightyROM forum because an unsigned ROM didn't always do a completely 'clean' flash on the NVRAM. Subsequent to this however, Mike also had a post that two 'hard flashes' (from the buttons) followed by a 'clear memory' before flashing (if you were having problems) was sufficient before flashing a custom ROM. Apparently there is some change in opinion on what is necessary even among the Cooks. I don't have enough experience personally to recommend one path over the other. Just an FYI from someone trying to come 'up to speed'.