[Vibrant Q&A, Help & Troubleshooting] dseldown:
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! :confused: I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways! :mad: