[ Discontinued ][ v4.2 ][ 6.5.x / 6.5 / 6.1 ] Calkulin's Visual VGA Kitchen & ROMs

[kris926]

Originally Posted by jregehr

1. I flashed another maker of rom to try the new Rhodium manilla (I think it was Energyrom)
2. I had some stability issues with it so I tried to go back to the Calkulin rom that was out one version newer than 7-21. I started having this issue where the rom would come back up after my hard reset and run nicely it seemed for a few minutes then it would run into some lockup or infinite wait cursor at varying places the when i power cycle it it either does not get past the bootloader screen (Touch Diamond) or it comes back as another hard reset. Usually it'll lock up within a minute.

Are you restoring any data using a backup program? I was having stability issues on the Mighty4 and MightyGroovy ROMS. I thought it was the ROMS but they were supposed to be rock solid. I noticed it seemed to be tied to my contacts. I flashed Calkulins 6.1 ROM and did not use SPB backup to restore the contacts. So far, so good. I've seen it mentioned that people have had problems after using PIM backup.
I'm not sure if this is related to your problem but it's worth a look.

[mshnayde]

Originally Posted by mshnayde

Hey guys,
I was on the NRGZ ROM prior and loved the In Call Screen Tweak being active.
I installed it on Calkulin's basic ROM but can't get it to work. If anyone has it working properly would love some advice about getting it running.
Thanks.

Just bumping to see if any suggestions at all.

[w0rdie]

Is there a cab for Nikoan89 Rhodium EzInput (v2.2)?

[KBZL]

All of you guys having flash problems. Have you tried flashing on a different computer? Its possible that there may be something on your computer that may be corrupting the flash process. Just a suggestion.

[WithoutRemorse]

Ladies and Gentlemen with flashing problems should go here http://forum.ppcgeeks.com/showthread.php?t=51508 for a possible soln.. I experienced this several months ago... and it seemd to work... I honestly think it is related to backup type software...... I think the key for me was formatting my internal storage.... I also tried turning off the synconizing files in active sync....

Trust me this isnt a permanent problem you have not been striken by the ROM flashing gods (or should it be Official Carrier Rom Gods?).... anycase good luck

Cheers,

[jregehr]

Are you restoring any data using a backup program? I was having stability issues on the Mighty4 and MightyGroovy ROMS. I thought it was the ROMS but they were supposed to be rock solid. I noticed it seemed to be tied to my contacts. I flashed Calkulins 6.1 ROM and did not use SPB backup to restore the contacts. So far, so good. I've seen it mentioned that people have had problems after using PIM backup.
I'm not sure if this is related to your problem but it's worth a look.

I've seen what you're talking about. Unfortunately I am not using any backup or restore function at all. Just clean flash.

[jregehr]

Originally Posted by WithoutRemorse

Ladies and Gentlemen with flashing problems should go here http://forum.ppcgeeks.com/showthread.php?t=51508 for a possible soln.. I experienced this several months ago... and it seemd to work... I honestly think it is related to backup type software...... I think the key for me was formatting my internal storage.... I also tried turning off the synconizing files in active sync....

Trust me this isnt a permanent problem you have not been striken by the ROM flashing gods (or should it be Official Carrier Rom Gods?).... anycase good luck

Cheers,

Again, I know of what you're speaking of if you have a ROM that won't boot past the initial bootloader screen, yes, we can go into the bootloader and re-flash. Unfortunately that doesn't address why any ROM I/we flash other than stock seems to be flaky to the point of not running for more than a couple minutes after the initial flash and reset.

Thanks for the support!

[gorestfump]

Originally Posted by jregehr

Again, I know of what you're speaking of if you have a ROM that won't boot past the initial bootloader screen, yes, we can go into the bootloader and re-flash. Unfortunately that doesn't address why any ROM I/we flash other than stock seems to be flaky to the point of not running for more than a couple minutes after the initial flash and reset.

Thanks for the support!

Just to update - my latest flash from last night seems to be going good. Pretty heavy use today and no problems. The last few things I did include (not sure which did the trick):

• flashing the telus radio (from the bell radio)
• flashing the bell stock (shipped) rom
• clear storage
• flashed the latest energyRom standard.
• clear storage
• restored all contacts and calandar via activesync
• installed all my apps, setup email accounts etc...

I also now will always keep a copy of the shipped rom on my internal storage incase something like this happens again. I know that was a rookie mistake but after a few dozen flashes on my diamond I guess I was a little over confident hehe. (I did previously have Calkulin's there which wasn't flashing after this issue started.) It would have saved me a few hard resets

Good luck folks! Thanks for all the tips as well!

[piscesjoey]

Originally Posted by gorestfump

Just to update - my latest flash from last night seems to be going good. Pretty heavy use today and no problems. The last few things I did include (not sure which did the trick):

• flashing the telus radio (from the bell radio)
• flashing the bell stock (shipped) rom
• clear storage
• flashed the latest energyRom standard.
• clear storage
• restored all contacts and calandar via activesync
• installed all my apps, setup email accounts etc...

I also now will always keep a copy of the shipped rom on my internal storage incase something like this happens again. I know that was a rookie mistake but after a few dozen flashes on my diamond I guess I was a little over confident hehe. (I did previously have Calkulin's there which wasn't flashing after this issue started.) It would have saved me a few hard resets

Good luck folks! Thanks for all the tips as well!

Yes that is a wise thing to do, I always keep my shipped ROM on my internal storage and flash custom through usb just incase something goes wrong and my phone becomes unresponsive while at work or etc, that way I can quickly flash stock ROM

[mwalt2]

Originally Posted by gorestfump

Just to update - my latest flash from last night seems to be going good. Pretty heavy use today and no problems. The last few things I did include (not sure which did the trick):

• flashing the telus radio (from the bell radio)
• flashing the bell stock (shipped) rom
• clear storage
• flashed the latest energyRom standard.
• clear storage
• restored all contacts and calandar via activesync
• installed all my apps, setup email accounts etc...

I also now will always keep a copy of the shipped rom on my internal storage incase something like this happens again. I know that was a rookie mistake but after a few dozen flashes on my diamond I guess I was a little over confident hehe. (I did previously have Calkulin's there which wasn't flashing after this issue started.) It would have saved me a few hard resets

Good luck folks! Thanks for all the tips as well!

You might want to reverse steps 1 and 2. Shipped ROMs also flash the radio (at least with Sprint, but I imagine it's probably the same).