TP2/MightyRom getting wiped?

[DrewTheRat]

It happened with 6.1 ROMs also. Seems like it happened no matter what ROM I tried. Sounds like task 29 is the way to go.

Thanks for the feedback. I will follow-up with results.

[DrewTheRat]

Okay, a month and a half later and I finally got around to doing this, and....

SUCCESS!

Looks like task29 was what I needed. Here's my upgrade process:

1. Started with stock SPL, MR1
2. Upgrade to Hard SPL
3. Ran task29
4. Flashed MightyROM FF
5. Ran clearstorage

Several days without a hiccup.

Thanks again everyone!

[eric12341]

i think running task 29 before and after stock is unnecessary because a similar process is done as the stock rom is being flashed. task 29 is for flashing from custom rom to custom rom. ive never done task 29 and havent had any serious problems.with my old TP that was a different story.

[DrewTheRat]

Okay, that would explain things.

My problems started when switching from one custom ROM to another. Even reverting to an earlier custom ROM wouldn't fix things. Ultimately I went back to the stock ROM. Based on what eric is saying, that did about the same thing as task29, so that's probably why things worked with the stock ROM.

In my procedure above, I used task29 before installing a custom ROM. I'll probably do that in the future regardless of whether the ROM I'm replacing is stock of custom.
However, since I'm up and running of MightyRomFF, I probably won't need to do that any time soon.

[demonlordoftheround]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

Originally Posted by eric12341

i think running task 29 before and after stock is unnecessary because a similar process is done as the stock rom is being flashed. task 29 is for flashing from custom rom to custom rom. ive never done task 29 and havent had any serious problems.with my old TP that was a different story.

That is correct. Shipped ROM does a Task 29 process zeroing all registry entries.