I know several people have gotten Nemesis2all's OTB 1.5 for CM7 working with Jt's CM7 Alpha3. However, I cannot figure out how to get it to work. Everytime I try, The phone just keeps repeating the Samsung logo screen (Samsung keeps flashing on and off.) Then, I can't access CWM unless I use Odin again. Any ideas?
spartan.062 said:
I know several people have gotten Nemesis2all's OTB 1.5 for CM7 working with Jt's CM7 Alpha3. However, I cannot figure out how to get it to work. Everytime I try, The phone just keeps repeating the Samsung logo screen (Samsung keeps flashing on and off.) Then, I can't access CWM unless I use Odin again. Any ideas?
Click to expand...
Click to collapse
I'm betting you downloaded the one navenedrob posted in nemesis's thread. That one is broken. Flash this one and you will be good to go: http://adbdev.com/danknub/SF_GB_OTB-Reloaded_ver1.5.zip
So THATS the problem! Thanks.
EDIT: YAY! IT WORKS!
Related
I had installed Voodoo and went to install one of the AOSP roms available. I didnt realize that it would overwrite the kernel and now upon booting the phone will go into FC loops. I cant get anywhere and cant get into CWM. I thought I would try using ODIN to get back to stock but now its doing the same thing at stock. I'm at a loss. What should I do? Is my phone Perma-bricked?
Was it my rom? I don't think it deletes the kernal?
Sent from my SPH-D700 using XDA App
blue breeze. I didnt think so either but now I get nothing but FC's from startup. So I tried to flash back to stock. Still nothing.
Oh my there are going to be a lot of these...
I don't know. I think that IF I had flashed the ROM first and then Voodoo I would've been fine. Unless I'm wrong and that's not what caused the issue. Any solution or am I out of a phone?
why can't you get into cwm? even by turning your phone off and holding the volume keys and the power button?
It goes to stock recovery, always has. I could only get into CW by going to ROM manager and booting into it that way.
do the update.zip and it should take you to cwm
the reason you're in FC HELLLLLLL is cuz you flashed over voodoo. that's why JT said don't flash over vooodooooo. you can fix it by going back to stock with odin. then i suggest loading bubby's kernal then voodoo over that.
Ive tried going back to stock with ODIN and it still does it. I'm going to try re-downloading the stock files and do it again. BTW the FC's are: android/process.media, and TwLauncher. I cant even get to any kind of homescreen or settings to turn on debugging.
i tried going back to stock with odin because i wanted to remove voodoo anyway before i flashed a rom and still am getting FC's like crazy
Have you tried this?
Have you checked this? http://forum.xda-developers.com/showthread.php?t=807088 ...would be a good idea....
Hey guys. So yesterday I was running Bionix Fusion 1.1 stock and decided to flash their core rom and right after I flashed Bionix fusion 1.2 and killed my phone. I can get into download and have been trying to use odin to get back to the stock vibrant but I keep getting a blank screen after the Samsung boot animation. The screen is black and the buttons light up. I've tried the JFD, JI2 and JI6 .tar files but I keep getting the same results. Anyone have any ideas what I should try next?
vibrant808 said:
Hey guys. So yesterday I was running Bionix Fusion 1.1 stock and decided to flash their core rom and right after I flashed Bionix fusion 1.2 and killed my phone. I can get into download and have been trying to use odin to get back to the stock vibrant but I keep getting a blank screen after the Samsung boot animation. The screen is black and the buttons light up. I've tried the JFD, JI2 and JI6 .tar files but I keep getting the same results. Anyone have any ideas what I should try next?
Click to expand...
Click to collapse
Try the Froyo rom that does not brick and then try going back to stock from there
Yeah thats the last thing I did and the first thing that actually worked. figures haha. Thanks though! So happy to be able to use my phone again
I flashed the DoW rom/kernal using clockworkmod on my vibrant and it gets to the boot screen (the screen with tw in brackets and an atom cloud) and just hangs. Anyone know what's goin on?
rmp5s said:
I flashed the DoW rom/kernal using clockworkmod on my vibrant and it gets to the boot screen (the screen with tw in brackets and an atom cloud) and just hangs. Anyone know what's goin on?
Click to expand...
Click to collapse
As far as I know DoW is a kernal not a rom. Make sure it will work with whatever your current rom is. Working great flashed over nero5.
I would odin back to stock, flash custom froyo rom then kernal....
By chance did you have lag fix disabled?......works fine with nero 4.1 and 5 for me.....but I found nerov5 works great without it
Sent from my SGH-T959 using XDA App
K5C5S5 said:
I would odin back to stock, flash custom froyo rom then kernal....
Click to expand...
Click to collapse
+1
Also remember that not all phones will handle the oc'd kernels
if you can get into recovery, you can try flashing a different kernel or reflashing your rom.
I'm currently running Bionix oc/uv and love it.
I DID undo the lagfix before flashing this.
If I could get a link to the stock odin files to flash so I could give the amazing sounding DoW a shot, I'm sure I could get it working.
Im running DoW 1.3 on AxuraJL5, and it does the same thing. i often have to pull the battery for a successful reboot. its sucks, but ive learned to live with it
wrong section to post this in, not to be a drag but its just that these forums can get clogged up with stuff like this if we dont keep posts in order. Q&A or under the DoW thread would suffice.
funeralthirst said:
if you can get into recovery, you can try flashing a different kernel or reflashing your rom.
Click to expand...
Click to collapse
With all due respect, if I could get into recovery, I wouldn't be posting this...
I made a fresh Nandroid before trying this but I can't get to recovery or anything.
brandonkahn said:
wrong section to post this in, not to be a drag but its just that these forums can get clogged up with stuff like this if we dont keep posts in order. Q&A or under the DoW thread would suffice.
Click to expand...
Click to collapse
I understand. If a mod moves it, it's all good. Just looking for help...my phone is sitting stuck at the atomic bomb screen still. It's been 2 hrs...just lookin for a hand. :-D Thanks!
have you tried getting it into download mode? i know you said you cant get into recov. but download mode is different.
first, do you know how to get into download mode?
well in short if you dont, when ur phone hangs.. pull the battery. with the bat. out hook it up to ur comp with odin running... as ur holding down the vol. up and down buttons stick in the batt. then you will be in download mode. then flash back to JFD
Maybe im wrong but isn't the dow kernel for 2.2. Didn't he say he was on bionix and isn't that a 2.1?
Powered by Axura with a dash of Voodoo
you are correct, i missed that he stated he was using bionix. OP there is your problem, you flash a 2.2 kernel with a 2.1 rom. flash back to stock via my instructions and you willl be fine.
you will need this http://forum.xda-developers.com/showthread.php?t=734475
Glad we got that taken care of.before he hard bricked his phone.
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
Glad we got that taken care of.before he hard bricked his phone.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
lol...I did this with my wife's phone...no boot and no recovery is very disheartening to say the least. lol
So...I flash back to stock using the thread provided and then flash DoW?
rmp5s said:
lol...I did this with my wife's phone...no boot and no recovery is very disheartening to say the least. lol
So...I flash back to stock using the thread provided and then flash DoW?
Click to expand...
Click to collapse
after you flash back to stock you of course are going to want to root your phone again, then youre going to want to go to team whiskey and download Nero... a 2.2 rom that works with the kernel. then you will want to flash DoW. I would also consider downloading setcpu because that kernel will drain the heck out of your bat. make sure you dont set to boot with setcpu, and just use the conservative setting.
team whiskey http://teamwhiskey.com/DownVibrant.html
again make sure its a 2.2 rom.
DoW works with any Nero (2.2) Team Whiskey Rom. You have to disable Vodoo LF before flashing, otherwise you will get stuck in a boot loop. Make sure to let the Rom run for a few minutes after flashing before replacing the kernal. You can always pull a logcat to see what your phone is doing when it hangs.
brandonkahn said:
after you flash back to stock you of course are going to want to root your phone again, then youre going to want to go to team whiskey and download Nero... a 2.2 rom that works with the kernel. then you will want to flash DoW. I would also consider downloading setcpu because that kernel will drain the heck out of your bat. make sure you dont set to boot with setcpu, and just use the conservative setting.
team whiskey http://teamwhiskey.com/DownVibrant.html
again make sure its a 2.2 rom.
Click to expand...
Click to collapse
Very fist, I wanna say thanks a million to all the replies and help. :-D
Ok...now...to set the record straight, my phone just tries to boot to the DoW and does nothing after. It just hangs.
Yes. I was running a 2.1 rom (Bionix) with a 1.2ghz oc, the uv kernal and the voodoo lagfix (which WAS DISABLED before flashing) but I thought I did everything right. If I had known that switching from a 2.1 rom to a 2.2 rom would have been this much more involved than I thought, I might have reconsidered...lol
I did a Nandroid backup using clockworkmod prior to doing anything else. I got to the red recovery (not 100% sure how I did it, to be honest) and tried to flash my backup and it didn't work.
I'm going to try the previous post about flashing back to stock, then doing the DoW flash but that's kind of a last resort. I'd like to not wipe my data, nandroid, etc before flashing but it's kinda whatever at this point since my phone doesn't work at all right now...lol
Thanks once again all of you!!! This is what makes Android what it is.
A little background first:
I came from a stock vibrant with JI6, rooted it, and installed Trigger 2.6.4 along with Overstock 1.1 and then 1.2.1. Everything was working fine.
So Trigger 2.7 came out and I ODIN back to stock, flash Trigger, and let it sit for at least 10 minutes. I then reboot, reboot again into recovery, and proceed to install Overstock 1.3. It is then that I'm stuck on the Overstock boot screen and end up having to go back to download mode to stock to get things working again.
Here are the steps I've been taking: (tried this a few times and redownloaded/checked file hashes just to make sure)
1. I go from stock to root to rom manager to CWM
2. I wipe to factory default and wipe cache partition
3. I install Trigger 2.7 from zip
4. I wipe Dalvik and fix permissions
5. Reboot and let it sit for 10-15 min after phone finishes booting
6. Reboot again and let it sit for about 5 min
7. Reboot to CWM recovery and flash Overstock 1.3
8. Wipe Dalvik and fix permissions
9. Reboot and stuck at Overstock bootscreen (waited about 10 min)
Am I missing any steps? If not, I cannot seem to get this combination. I loved the Trigger + Overstock combo when I had it but I cannot seem to get it to work. Any help would be appreciated!
You said you checked the md5, right?
Why wipe/fp after flashing the kernel? I just reboot.
How long is it stuck at the Vibrant screen?
No md5 present for the kernel but I did check the md5 of the rom. I also redownloaded the kernel a few times and each time the md5 was the same.
I just tried your method of not wiping or fixing permissions. I get the same problem of it freezing at the Overstock boot screen. It sits at this screen indefinitely. It only shows the Vibrant screen for a few seconds before it gets stuck at the Overstock screen.
Hmm... consider me stumped. I will continue to research.
BT confirmed that OS works with 2.7. That said, looking over the last posts in the thread, it sounds like some people are having issues.
Maybe try s0niqu3s kernel man? I used it and loved it. Basically the same thing but without the RAM hack. Very close to stock and you may have a more stable kernel.... or atleast one that will flash for you.
Androidium said:
No md5 present for the kernel but I did check the md5 of the rom. I also redownloaded the kernel a few times and each time the md5 was the same.
I just tried your method of not wiping or fixing permissions. I get the same problem of it freezing at the Overstock boot screen. It sits at this screen indefinitely. It only shows the Vibrant screen for a few seconds before it gets stuck at the Overstock screen.
Click to expand...
Click to collapse
I'm using 2.7 with Overstock 1.3 right now. I've never had that issue.
When you tried it without wiping cache or fixing permissions was it after a fresh flash? Or did you flash over OverStock (lol).
birgertime said:
I'm using 2.7 with Overstock 1.3 right now. I've never had that issue.
When you tried it without wiping cache or fixing permissions was it after a fresh flash? Or did you flash over OverStock (lol).
Click to expand...
Click to collapse
Yes it (Overstock) was over a fresh flash of Trigger 2.7. Per the suggestion above, I also tried the CWK and that one works just fine. Overstock just does not play nice on my phone for some reason? I just tried flashing CWK and then Overstock to see if that stepping stone method worked and I'm stuck at the Overstock screen again...
I'm pretty stumped at this point.
Back to ODIN...
Edit: Is there any way I can combine Overstock and Trigger together in one flash? I'm wondering if that would solve my issue.
After poking around the zip file for the Overstock kernel and comparing it to the CWK that worked, I noticed that there is an extra file called NOTICE in the Overstock one. What is that file used for? Would it be safe to remove it? Does anyone think that might be the issue? Another possible theory of mine would be to just transfer the two kernel files from Overstock to the CWK zip and replace those 2 files there. What do you think?
I'm running Trigger final and os and never happens to me. I do not wipe anything before or after flashing overstock. Once done with a fresh trigger, simply flash os.
Sent from my SGH-T959 using XDA Premium App
Is it possibly the RAM hack in Overstock that might be an issue?
Are you running anything else: per say set CPU?
Sent from my SGH-T959 using XDA Premium App
Nope just a fresh flash of Trigger.
I'm having the same exact problem as Androidium. Only difference is Ive tried flashing Overstock on multiple roms with no luck. I've noticed the problems after using Deadhorse. Could that be the source of the problem?
dvdbouchard said:
I'm having the same exact problem as Androidium. Only difference is Ive tried flashing Overstock on multiple roms with no luck. I've noticed the problems after using Deadhorse. Could that be the source of the problem?
Click to expand...
Click to collapse
How about Odin back to stock with repartition checked and starting over?
Sent from my SGH-T959 using XDA Premium App
Hello. A friend of mine recently bought a Vibrant that is stuck at a constant boot loop. I have a heavily modified Captivate, so I know that as long as the phone boots up, it can get to Download Mode. I am in the process of reverting the phone to JFD using Odin. My question is, which is the most recent OFFICIAL f/w available for the T-Mobile Vibrant?
"Official" Froyo I believe was KB1. But KB5 is the last leak we got (and most likely will ever get). I can't think of a reason why you shouldn't use KB5. Most will agree that it's better than the "official" KB1.
excellent, i'll look it up and install it. thanks a lot bro!
No problem. There's a stock deodexed KB5 somewhere in Vibrant Dev forum but if you want a slick custom rom I'd suggest either ZenDroid or Project-V.
Project v is a sweet 2.2 custom rom....only issue ive ever had with it is you dont get a notification for voice mail,so if you see a missed call...it doesnt mean you dont have a voice mail message....better go check.
Other than that its perfect with everything working.
Granted you can download other apps to work around the voicemail notification
I just flashed JFD via Odin 3, and I'm stuck in a boot loop. Any suggestions on what to do?
Sent from my SAMSUNG-SGH-I897 using XDA App
kafepuya said:
I just flashed JFD via Odin 3, and I'm stuck in a boot loop. Any suggestions on what to do?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Pull battery, sim, and ext sd if you have one. Wait 10 seconds or so. Put only the battery back in. Hold vol up+down and plug in usb to boot into Download mode. Try flashing JFD again. See if that works for you.