|
Ive had this issue appear three times now over the 8 revisions of the custom rom I've been working on...
From what Ive seen, Performing a hard reset RIGHT after the rom flash is finished seemed to prevent the issue from happening. But I could be wrong being Ive only had 2 chances to test the theory so far, First appearance of this possible bug was after I had made Rev.1, And I just soft reset and it hadn't re-appeared till I was on Rev.6 and again on Rev.7, At which point I remembered how the older 3.3 and 3.5 roms often needed a hard reset after the initial flash...
|