Is it me or the phone?

[jackmei2]

ever since I've gone from the original GB leak to Froyo and now back to the MR2 leak and GB I've been having issues with ROM's.

it first started when I went back to froyo, after a few days of being on das bamf 1.7, my phone would go on an endless bootloop and I couldn't get back into it. so I tried reflashing the radio, the rom, fixing permissions, but nothing would help. I wasn't OC'd or anything with das bamf. so I wiped the data and flashed the rom again and I was back up and running on das bamf. About 5 days later, the same thing happened, endless bootloop and I couldn't get back into my phone. Luckily the MR2 leak came out and so I flashed to that along with gingeritis test IX. everything worked well, then I flashed to gingeritis 1.0 when it first came out on Monday.

Today, as I was on the phone with someone, my phone suddenly rebooted and got stuck in an endless bootloop. I cleared cache and did a fix permissions and luckily I was able to boot back up. That is, until I called VZW to report that 4G is out in my area (it wasn't my phone since I had 4G at the office 10 mi away, but not at home and I know of a few other people in my area that didn't have 4g either). I rebooted and now I'm stuck in a bootloop, but this time clearing the cache and fixing permissions didn't work.

I ended up having to re-flash the ROM to get back up and running... I guess my question is, am I doing something wrong, or is something wrong with the phone? I hadn't had any reboot issues at all until I switched back from the leaked GB radio and rom.

 

[aBoldPatriotsFan]

ever since I've gone from the original GB leak to Froyo and now back to the MR2 leak and GB I've been having issues with ROM's.

it first started when I went back to froyo, after a few days of being on das bamf 1.7, my phone would go on an endless bootloop and I couldn't get back into it. so I tried reflashing the radio, the rom, fixing permissions, but nothing would help. I wasn't OC'd or anything with das bamf. so I wiped the data and flashed the rom again and I was back up and running on das bamf. About 5 days later, the same thing happened, endless bootloop and I couldn't get back into my phone. Luckily the MR2 leak came out and so I flashed to that along with gingeritis test IX. everything worked well, then I flashed to gingeritis 1.0 when it first came out on Monday.

Today, as I was on the phone with someone, my phone suddenly rebooted and got stuck in an endless bootloop. I cleared cache and did a fix permissions and luckily I was able to boot back up. That is, until I called VZW to report that 4G is out in my area (it wasn't my phone since I had 4G at the office 10 mi away, but not at home and I know of a few other people in my area that didn't have 4g either). I rebooted and now I'm stuck in a bootloop, but this time clearing the cache and fixing permissions didn't work.

I ended up having to re-flash the ROM to get back up and running... I guess my question is, am I doing something wrong, or is something wrong with the phone? I hadn't had any reboot issues at all until I switched back from the leaked GB radio and rom.

I would say most of the time issues stem from not properly loading things onto your phone. Wiping all the know things to wipe. I usually wipe them 3 x's. I do know that coming and going from GB to Froyo has some issues. I usually return my phone to stock rooted when i do so. I have never had any problems that i didnt cause with the exception of the charging issue and the rebooting due to a radio. If i loaded something wrong i usually can rule out Radio or ROM being the issue. Sometimes i am too excited and load something wrong.

I would try to slow down and do everything slowly maybe you are missing something? Wrong radio/kernel? Forget to wipe Davlik/Partition?

 

[jackmei2]

wrong radio or kernel would cause problems immediately, no? I did the 3x wipe before flashing the rom along with the dalvik and reg cache. it's just odd since it works fine at first, then a few days later, bam! bootloops!

I think I'll try returning to rooted stock as you suggested and then going back to gingeritis and see if that gives me problems. thanks for the help!

 

[jackmei2]

oh, also, I was getting force closes with the phone and messages, constantly so I couldn't use my phone without a message coming up for me to force close it. this was on das bamf 1.7, not a bootloop. the bootloop was only with gingeritis.

I restored a backup of gingeritis after doing a wipe so we'll see how that goes.

 

[zero neck]

A mismatched kernel will probably result in immediate bootloops. A. Mismatched radio just wont work correctly but the rom should work.
You shouldn't have the fcs on 1.7, what steps did u take to flash

 

[jackmei2]

1. wipe data
2. wipe cache (even tho wipe data takes care of this)
3. wipe data
4. wipe cache
5. flash rom
6. wipe batt stats
7. pull batt, boot to hboot
8. flash GB radio
9. reboot

things are fine for a few days, and then suddenly the phone acts up without me doing anything except for rebooting. I had my phone OC'd at first using setcpu (disabling the min/max in speedtweak.sh), but the 2nd time it wasn't even OC'd.

 

[zero neck]

1. wipe data
2. wipe cache (even tho wipe data takes care of this)
3. wipe data
4. wipe cache
5. flash rom
6. wipe batt stats
7. pull batt, boot to hboot
8. flash GB radio
9. reboot

things are fine for a few days, and then suddenly the phone acts up without me doing anything except for rebooting. I had my phone OC'd at first using setcpu (disabling the min/max in speedtweak.sh), but the 2nd time it wasn't even OC'd.

You need to clear dalvikcache under advanced in recovery

 

[jackmei2]

sorry, that was part of the cache, should have written cache(s)

 

[zero neck]

I dont know what it is that's causing your phone to act like this.

How many of the froyo radios have you tried with bamf 1.x.x series rom?

BTW batt stats should be wiped only when you are are 100 percent charge.

Maybe try reflashing 1.7 with complete wipes, let it reboot and settle in a few min, then try a different froyo radio and see if you can at least avoid the reboots.

If your phone reboots on all radios (gb, and the froyo combinations) i would definitely consider getting a different unit.

 

[jackmei2]

yup, I only flash roms/kernels when 100% charged.

I only tried the original froyo radio that came with my phone and the MR1 radio. no issues before upgrading to GB. never had reboot issues.

before upgrading to GB with the 1st leak, I had no issues whatsoever with reboots and I was on the MR1 radio. I downgraded to froyo after the GB radio bootloop scare. I ran das bamf 1.7 fine for about 5 days, no issues whatsoever. on that 5th day, it was constant FC's every few seconds with the phone and messaging apps, basically made the phone unusable. I couldn't even get to my messages anymore. I ended up having to do a complete wipe of data and caches, and reflash of the MR1 radio and das bamf 1.7 again. a few days later, same thing, phone and message apps were FC. then the new GB radio came out.

I upgraded back to GB leak with the MR2 radio and then after a few days of working perfectly, it was constant reboots. so it's like something goes off after a few days and bam! non-functional phone. I think I might try going back to rooted stock and start over from there. I'm not sure what I could have screwed up flashing as I flashed a whole bunch of stuff before downgrading from the first GB leak. so I'm confused as to what's going on with it.

 

[zero neck]

Did you try bamf 1.6.3? I found it to be more stable than 1.7 actually.
As long as you clear everything there shouldn't be any ghosts or what have you when you switch roms, unless you allow titanium to restore app data, particularly system data.