Rom Manager glitch

EvoRoy

Well-known member
Jul 14, 2010
156
1
0
Ok, so last night I ran a back up in Rom Manager for Myn's twopointtwo (RLS2) then flashed Vaelpak 2.2 (Which was on my SD card buy just had not gotten around to using yet) Well something was acting screwy cuz I kept getting Force Close issues. So I decided to flash back to Myn's rom to try and figure out the battery issue. I first tried to use Rom Manager I long pressed the stored Rom and hit restore. NOTHING... Hmmmm... so I went to Quick Boot (I was having an issue with this not working in Vaelpak) went to Recovery got to Nandroid chose the Rom did a restore (down the list no,no,no,no,Yes,no,no,no) chose Yes, but then it went to the reboot now instead of the android unpacking the box. Then booted back to Vaelpak. Hmmm...(a little worried at this point) went to Rom Manager chose Cyanogen 6.0.0 and it flashed fine.
 
I'm just thinking that if your installation was corrupt and you were getting all those FCs I wouldn't really blame ROM manager but, people do have problems with it and you were able to install CM6 - which you need hboot .76 for, so I'm just wondering if one of your other nandroids were made with hboot .79.

Also, are you on the latest install of rom manager?
 
I should be on the latest, everytime i flash a new Rom I download straight from the market along with my premium licence.
 
Did you have good battery when you tried the first flashes?

Now that you're on CM6, have you tried to restore other Nandroids?
 
I think I was even plugged in when I tried to flash. No, I forgot how I liked CM6. I want to do more research on Vaelpak. I like it but need to find out what was giving me the force close issues I had along with the Quick Boot not working properly.
 
I think I was even plugged in when I tried to flash. No, I forgot how I liked CM6. I want to do more research on Vaelpak. I like it but need to find out what was giving me the force close issues I had along with the Quick Boot not working properly.

It sounds like either the installation was somehow corrupted, there were file permission errors or all the partitions weren't wiped.

I would try again but not from a nandroid restore, just install it again from ROM manager and make sure to wipe it all down first. Then when you have it going good make a nandroid.
 

Latest posts

Trending Posts

Forum statistics

Threads
964,218
Messages
6,995,764
Members
3,164,609
Latest member
alkarastone