• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The I borked my SF support group thread

can't get past samsung screen... originally i knew something was f'd up because the lady wasn't talking when it was supposed to be converting back to rfs ... fk voodoo i'm never using that again once i get back up.... damnit it takes me like allll day to restore since i dont use a nandroid i just use my tb apps and install everything else from scratch, the new market, omfg everything... i'mma be up here in the morning lookin for some help
Damn buddy sorry Im going to sleep now I tried to hit you up on irc but you were already gone. Its probably too late but for the future if you ever try it again remember 2 step process 1]disable lagfix 2]allow system conversion of whatever its called you need to execute both operations and then reboot.
Also and this is only a theory if you go from a OV kernel dont go right to a UV/LV Im not 100% sure but it seems to be problematic for whatever reason.

I'll be around in the AM hopefully you are good or one of the east coasters can hook you up
 
i was running the 1100mhz ultra low kernel from saps OP. in about an hour my odin restore file should be done from verizon the stock image... im going restore from that if noone can help me, i already got the directions to do the odin restore and everything right here on my other tab.is there a quicker way then redoing EVERYTHING? i have a nandroid

Edit: and i have removed it before but i did it while in IRC and nitsu and geeknik and some other peeps walked me through it that time

Edit 2: Thx Nitsu for sparking this idea, after i finally, somehow, got into red cwm, i flashed the 1100 ul kernel again, wipe cache, and phone went back up everything is looking fine... i'll report back on here if it crashes, or anything weird happens. Bout to smoke a bowl in celebration! ITS A CELEBRATION B!T%#$!

Edit 3: The crazy robot lady is singing her sweet song and taking me back to StupidFast land lol..." time left for operation - 10 minutes". 12.15.10 test here i come! (finally after 3 hours)
 
can't get past samsung screen... originally i knew something was f'd up because the lady wasn't talking when it was supposed to be converting back to rfs ... fk voodoo i'm never using that again once i get back up.... damnit it takes me like allll day to restore since i dont use a nandroid i just use my tb apps and install everything else from scratch, the new market, omfg everything... i'mma be up here in the morning lookin for some help

u haz teh bork? :)

What voodoo were you running? Have you removed voodoo before?

i was running the 1100mhz ultra low kernel from saps OP. in about an hour my odin restore file should be done from verizon the stock image... im going restore from that if noone can help me, i already got the directions to do the odin restore and everything right here on my other tab.is there a quicker way then redoing EVERYTHING? i have a nandroid

Edit: and i have removed it before but i did it while in IRC and nitsu and geeknik and some other peeps walked me through it that time

Edit 2: Thx Nitsu for sparking this idea, after i finally, somehow, got into red cwm, i flashed the 1100 ul kernel again, wipe cache, and phone went back up everything is looking fine... i'll report back on here if it crashes, or anything weird happens. Bout to smoke a bowl in celebration! ITS A CELEBRATION B!T%#$!

Edit 3: The crazy robot lady is singing her sweet song and taking me back to StupidFast land lol..." time left for operation - 10 minutes". 12.15.10 test here i come! (finally after 3 hours)

yeah it seems like with voodoo5 just reflashing a v5 kernel will in many cases rectify whatever went wrong (not always, but a lot more frequently than with old voodoo)

its a "kindler, gentler" voodoo :cool:
 
Yeah but I was stuck on samsung screen for a lonnnnnnng time before i pulled the battery because the robot lady wasn't saying anything yet. I, only then, after many reboots trying to get into red cwm, it finally worked, then i flashed my way back to non-voodoo and i'm not delving into that until the ocs get more stable, i dont get nearly as many lockups with geekniks. the ext4 system on my n1 was flawless... notsomuch with this . i'm still trying to get the 1.15 ghz geekniks running at 1225mv! I get wayyyy better battery life also, my girls fascinate, now rooted, with dI01 clean on there, adw, flies. its at sometimes smoother than mine, and she's not on dj05. after reading some threads, I decided to try a dj05 adw test since i use LPP, maybe that will shed some light, for me, as to how the different versions and kernels are and if the launcher is the difference, I also run just about all of the lpp widgets, she doesn't really have any but bw, fb, a picture frame, gv settings, and a recipe thing. right now, we get about same battery life, her screen stays brighter for some reason on di01, and of course the gps is not as functional, but all in all, we're happy with our new FREE phones... better than the 570 i spent on the n1... now i can save money to buy the new LTE dual core tegra 2 LG Star (hopefully) or optimus 2X.
 
ha ha... The ole force close hell has come back to haunt me :(
So I installed the retrokid theme and decided I liked the origional one I had on there better, for today anyways:) . Couldn't find the original theme on my computer to reflash, so I did a nand-restore of a fresh backup I had on the sd with the theme I wanted on there.
Using the pwr button option I pressed recovery, red cwr came up which was odd as green cwr had been coming up since I disabled voodoo over 2 weeks ago. I made sure lagfix was still unabled and red cwr said it was currently disabled and that upon boot would be disabled. Also made shure sys conv was off.
So I went ahead and restored the backup. When it re-booted and opened it went right to force close hell. No idea why as I had done this prob 6 times in the past week. So I figured maybe that backup somehow became corrupted. We"ll I have about 4 backups on the sd, so I chose another one. What I had noticed while it was doing the restore is that when it got to the data part it just skipped it and the devlik cache was skipped also. System and datadata loaded fine.Now I am starting to think, I only have 2 backups left. Tried the 3rd bu file and the same thing happend no complete data, dalvik cache and force close issues again.
I then went ahead and did a complete wipe and fact reset from green cwr and tried to install the same backup. No dice same prob with data and dalvik. Damn, only one backup left which was pretty old and would be some work restoring everything. So I restored it and it worked, I could tell it was gonna work right away too because the data and dalvik both loaded this time. Phone working again.
This is where I am at and puzzled as to why those other backup files will not install. If anyone has any ideas I sure would like to hear them as this is the first time I have run into this.....
I still can't restore the fresh backups that I have without the fc issues, but the phone is working fine so far on the old backup.
 
There is a thread on xda about how to get rid of red recovery, involves flashing one of jt's non voodoo, I think 11/29.
 
ha ha... The ole force close hell has come back to haunt me :(
So I installed the retrokid theme and decided I liked the origional one I had on there better, for today anyways:) . Couldn't find the original theme on my computer to reflash, so I did a nand-restore of a fresh backup I had on the sd with the theme I wanted on there.
Using the pwr button option I pressed recovery, red cwr came up which was odd as green cwr had been coming up since I disabled voodoo over 2 weeks ago. I made sure lagfix was still unabled and red cwr said it was currently disabled and that upon boot would be disabled. Also made shure sys conv was off.
So I went ahead and restored the backup. When it re-booted and opened it went right to force close hell. No idea why as I had done this prob 6 times in the past week. So I figured maybe that backup somehow became corrupted. We"ll I have about 4 backups on the sd, so I chose another one. What I had noticed while it was doing the restore is that when it got to the data part it just skipped it and the devlik cache was skipped also. System and datadata loaded fine.Now I am starting to think, I only have 2 backups left. Tried the 3rd bu file and the same thing happend no complete data, dalvik cache and force close issues again.
I then went ahead and did a complete wipe and fact reset from green cwr and tried to install the same backup. No dice same prob with data and dalvik. Damn, only one backup left which was pretty old and would be some work restoring everything. So I restored it and it worked, I could tell it was gonna work right away too because the data and dalvik both loaded this time. Phone working again.
This is where I am at and puzzled as to why those other backup files will not install. If anyone has any ideas I sure would like to hear them as this is the first time I have run into this.....
I still can't restore the fresh backups that I have without the fc issues, but the phone is working fine so far on the old backup.

even if you disable voodoo5, red recovery is still there unless you flash 11/29 nonvoodoo from jt (i dont know of any other kernels specifically eleminating red recovery)
 
Stupid Verizon keeps trying to cram that update down my phone's throat. It will run my battery dead trying and not working while I'm asleep. And then occasionally it will just lock up my phone. If I kill the InfoPath process my phone will run fine for several days until it tries to force itself onto my poor, unsuspecting phone.

None of the fixes except the button backlighting even apply to me. My GPS works fine. Calls work fine. The internet and my custom launcher work fine. My phone doesn't need fixed. Verizon can contact me when they have 2.2 available. Scratch that. I'll contact the internetz once a clean 2.2 ROM of VZ's update is available....
 
Back
Top Bottom