Flashing Instructions to Ensure Full ROM Functionality - Page 2

Tilde88 · #1 (**permalink**) 08-08-2009, 01:02 AM

My mistake I figured since it was actually about flashing and theres a flashing sticky, I thought it would be here. Mod move to HTC Touch Pro forum please?

Also, any device that has RAM and or ROM will always have temporary cache files, which eventually can go corrupt on an abrupt soft reset just like in a PC when you reset it while it is doing something. The original reason why soft resets started being performed on Smartphones/PPCs was due to these corrupt files which would become then engraved into the ROM or RAM chip until it were forcefully overwritten or released from any electrical current. Which is why I flash with the battery off and unplug it when it is done. Then the hard reset ensures moreover that anything still miraculously 'alive' within said system storage is properly overwritten. On a PC you can simply take out the CMOS battery and reset the BIOS as to where on the phone I flash and then remove all power. On phones however we do not yet have a BIOS. I'm tired of typing and what not... If it helps anyone great... If you guys don't think it helps... Ask around the Tech1 CDMA thread and see how many people had ghost bugs... Later guys

**Carla** · #2 (**permalink**) 08-08-2009, 01:14 AM

Quote:

Originally Posted by Tilde88

Ask around the Tech1 CDMA thread and see how many people had ghost bugs... Later guys

From what a lot of peoples problems with that rom seemed to be I don't think it was all attributed to them not flashing your way.

obamaftw08 · #3 (**permalink**) 08-08-2009, 02:18 AM

Quote:

Originally Posted by CarlaDarla

From what a lot of peoples problems with that rom seemed to be I don't think it was all attributed to them not flashing your way.

Lol precisely. Please don't bring up another thread's misdeeds tilde.

In the meanwhile either flash method works its just a matter of who is or isn't lazy to go through with it.

Tilde88 · #4 (**permalink**) 08-08-2009, 11:18 AM

Yes it is quicker to flash from the Bootloader, and do a hard reset right after the flash rather than waiting for a full customization only to hard reset again. I'm glad to see that quite a few people agree with my approach. I have flashed every popular ROM on this site... Noticing that some people would post bugs that none other would ever see... It was not only in Techs thread... It was merely the thread I chose to point out... Even after a few people did some hard resets, these bugs persisted... Once they flashed in the OP method, I'm guessing it was the placebo that made the phone believe it could do better?

All I am saying is that this method can help some, if not speed up the flash process for others...

Request to delete or close thread please, AdminMOD...

Tilde88 · #5 (**permalink**) 08-10-2009, 12:35 AM

its best off not to flash to stock first... see, be it a custom ROM or a shipped ROM, there is still data being transfered throughout the flash. flashing a stock rom only adds an extra step to the flashing instructions i posted way back and on a new thread even... and it can add its own files which may corrupt some cache within the NAND, meaning that another flash with battery removal would be necessary to release these corrupted files which cannot be overwritten from within Windows[Mobile]...

flashing means transfering files (some files of which can be fractions of kilobytes in size even)... during the flash process, it is possible to not fully flash the rom because the old ROM (Read Only Memory) cache files cannot be replaced with the new ones, due to the old ones being -besides old- corrupted (broken) and stuck...after flashing a new ROM, and taking out the battery, this depletes (kills) any +-ionization (electrical currency) within the device since it does not have a CMOS Battery (a button cell battery which goes inside Computers to keep the clock accurate and certain hardware settings which cannot be controlled from an Operating System... An example of an OS is Windows, also Linux... etc...)after all the power has been released from the device the NAND then has no place to store its old ROM data, the device then routes what it can [unneeded crap] to the RAM (Random Access Memory). every time that there is no direct power (no battery and no USB connection to PC or wall charger), the RAM is released to be never again seen. ROM, however is stored into firmware. Firmware is neither hardware (like a video card, keyboard, monitor) etc, nor is it software (programs, games, drivers) it is pretty much a software that is permanent into the hardware's chip to enable its functionality.

thats as english as i can put it down... i dont know how else to explain it... you either understand or you dont...
nonetheless I know that this is a good thing to do before using your phone with its newly flashed ROM. it prevents countless errors over time

cd85233 · #6 (**permalink**) 08-08-2009, 01:04 AM

Will receiving a test message while the phone is going through the customization detrimental? Or what about if the phone turns itself of before you are able to calibrate the screen, meaning you waited too long before taping the screen when it asks.

Thanks for the right up. I hope this will take care of some random bugs int the ROMs that I have used. I never understood why some people had a perfect ROM while I had a buggy one.

Tilde88 · #7 (**permalink**) 08-08-2009, 11:11 AM

Quote:

Originally Posted by cd85233

Will receiving a test message while the phone is going through the customization detrimental? Or what about if the phone turns itself of before you are able to calibrate the screen, meaning you waited too long before taping the screen when it asks.

Thanks for the right up. I hope this will take care of some random bugs int the ROMs that I have used. I never understood why some people had a perfect ROM while I had a buggy one.

No they are not. Once the precached files have been flashed over or deleted none of these issues are detrimental... Just be sure to watch the crosshair to check for any skipping or lagging.

**indagroove** · #8 (**permalink**) 08-08-2009, 03:11 PM

Quote:

Originally Posted by Tilde88

Just be sure to watch the crosshair to check for any skipping or lagging.

Um, well, um..

That could easily be a result of provxmls being loaded still or the OS getting fully loaded. It doesn't mean a bad flash necessarily.

Tilde88 · #9 (**permalink**) 08-08-2009, 05:42 PM

Quote:

Originally Posted by indagroove

Um, well, um..

That could easily be a result of provxmls being loaded still or the OS getting fully loaded. It doesn't mean a bad flash necessarily.

this is true... but even after long wait periods with the screen on, long after all the background provisioning occurs, i've noticed still some lag [not often], but it could be an early indication of an unstable flash... or even it could be a beginner cook whom just has a beta build which needs further tweaking... but if no other is reporting any lag and you see the crosshair on first boot be glitchy then, well you know...

well im out pplz... be back later

**raidzero** · #10 (**permalink**) 08-08-2009, 09:30 AM

interesting approach. I always wondered why sometimes the calibration crosshair was choppy and sometimes it was smooth. What I always did was flash from bootloader, then just let it reboot, align screen (not waiting just doing it - usually choppy) then letting customizations run, then hard resetting via clear storage and doing it over. this method is definitely faster. may be a bit overkill but it gets the job done. for one I have never thought of removing the battery when flashing..