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
Related
So, my gf's white fascinate running superclean 2.9.2 has booted into safe mode randomly each of the last 3 days. Has anyone else had this problem? And are there any solutions? I've flashed the rom more than once and sometimes it reboots at 30% battery.
Mine boots into that safe mode thing after I run the script to wipe battery stats in terminal. Another reboot and it boots into the normal mode. I have no idea why it does that.
Same problem, she reboots and its fine for a day. My phone has the same setup and no problems. Hoping someone can help me out.
i used to have that problem on 2.9.1 all the time, but since 2.9.2 i havent had any problems
Sent from my SCH-I500 using XDA App
Did you do a full wipe when you threw on 2.9.2?
s13_slider said:
Did you do a full wipe when you threw on 2.9.2?
Click to expand...
Click to collapse
I did. Tomorrow I think ill do an Odin back to stock, then flash 2.9.2 again and see if it works.
Ok. My girlfriend's Fascinate has been doing this while mine hasn't and we're both running 2.9.2. It may be time to wipe her phone to get everything working properly again. I tried running fix permissions on Thursday, so I'm gonna wait to see if that fixes the problem. If it doesn't, it's wipe city.
Yeah, the whole "deep clean" where you manually wipe all the partitions from Clockwork (twice, if you're paranoid) *before* you do a full Odin may be good, just to be safe.
i just got my phone running ED01 today and it unrooted my phone. i rerooted it and all that jazz but my question is this...
i can't reboot into cwm recovery?
it just reboots me back into stock recovery.
do i download the latest cwm, rename it to update.zip (not update.zip.zip) and problem solved?
Put a new kernel on your sd card. As soon as you finish rooting, boot immediately into cwr and flash the kernel. If you let the phone boot before you do this, the stock kernel overwrites the recovery.
This happened to me earlier today and had me pulling my hair out. Nemesis2all had the answer.
yes! YES! that was just what i needed.
thank.you.
Ughh. I am having a very similar problem and I have been trying to solve it for the past 4 hours with no luck. Could you please tell me what you did to resolve this?
I was on SC 2.9 with JT's TW voodoo kernel. I decided to go back to stock and start from scratch by flashing the DI01 all in one Odin package in Odin. (I disabled voodoo before doing this). Everything went smooth as butter. I then got the vzw prompt to OTA Froyo. I downloaded and installed it just fine. I then re-rooted. Now I am having a hard time trying to get CWM to flash/install. I flashed 'cwm-recovery-all' in odin. Odin says it was successful and reboots my phone. When I try to boot into recovery, it goes to the blue android 2e screen. I go to 'apply update.zip and thats when I keep getting errors.
"E: failed to verify whole-file signature
E: signature verification failed "
I'm sure I am forgetting a step or missing something
farewell_goodbye2u said:
Ughh. I am having a very similar problem and I have been trying to solve it for the past 4 hours with no luck. Could you please tell me what you did to resolve this?
I was on SC 2.9 with JT's TW voodoo kernel. I decided to go back to stock and start from scratch by flashing the DI01 all in one Odin package in Odin. (I disabled voodoo before doing this). Everything went smooth as butter. I then got the vzw prompt to OTA Froyo. I downloaded and installed it just fine. I then re-rooted. Now I am having a hard time trying to get CWM to flash/install. I flashed 'cwm-recovery-all' in odin. Odin says it was successful and reboots my phone. When I try to boot into recovery, it goes to the blue android 2e screen. I go to 'apply update.zip and thats when I keep getting errors.
"E: failed to verify whole-file signature
E: signature verification failed "
I'm sure I am forgetting a step or missing something
Click to expand...
Click to collapse
First, grab a TW kernel, for example JT's TW voodoo kernel and place it on ur SD card. Next remove battery and enter download mode so u can Odin CWR. Once it's done u should see that it succeeded flashing CWR in Odin. Next reinstall battery and enter recovery mode by holding down both volume buttons and power button. Once u see the samsung logo, release and it should enter red CWR. Then flash the TW kernel and reboot. U should be golden. There's no update.zip file to worry about.
As mentioned on the previous post, the stock kernel overwrites CWR and defaults back to stock blue recovery. Good Luck...
will survive said:
First, grab a TW kernel, for example JT's TW voodoo kernel and place it on ur SD card. Next remove battery and enter download mode so u can Odin CWR. Once it's done u should see that it succeeded flashing CWR in Odin. Next reinstall battery and enter recovery mode by holding down both volume buttons and power button. Once u see the samsung logo, release and it should enter red CWR. Then flash the TW kernel and reboot. U should be golden. There's no update.zip file to worry about.
As mentioned on the previous post, the stock kernel overwrites CWR and defaults back to stock blue recovery. Good Luck...
Click to expand...
Click to collapse
Thank you so much for the help. I will try this now and report back.
Edit: You are a genius! Back up and running and voodoo enabled in 15 mins thanks to you. It was great hearing the voodoo robot voice again. Haha. Thanks again kind sir and everyone here at xda for being such great help in a time of need. Now off to choose a good rom!
Sent from my SCH-I500 using XDA App
farewell_goodbye2u said:
Thank you so much for the help. I will try this now and report back.
Edit: You are a genius! Back up and running and voodoo enabled in 15 mins thanks to you. It was great hearing the voodoo robot voice again. Haha. Thanks again kind sir and everyone here at xda for being such great help in a time of need. Now off to choose a good rom!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Glad it worked out for u.
As for ROM's, I am currently trying out Evil Fascination v3.3.1. So far loving the rom.
will survive said:
Glad it worked out for u.
As for ROM's, I am currently trying out Evil Fascination v3.3.1. So far loving the rom.
Click to expand...
Click to collapse
that was exactly my problem too but after flashing a custom kernel everything is running smooth. and i'm trying out evil fascination and it is GREAT
djdeaver said:
that was exactly my problem too but after flashing a custom kernel everything is running smooth. and i'm trying out evil fascination and it is GREAT
Click to expand...
Click to collapse
Couldnt agree more. This rom is great. I wouldn't expect anything less from Nitro. Also, I took my phone off the charger an hour and a half ago and im at 99%. I would have been at 87 - 90% before using this new combination.
Edo1 radio
Jts TW voodoo 4/15 kernel
Nitro evil fascination rom.
Sent from my SCH-I500 using XDA App
Allright, so there I was, running a rather stable Comm Rom 2.0 Voodoo Rom with the ED10 Kernel/Radio, and then I saw the thread on the OMFGB GB release, that I, of course, just HAD to have...
So, my first mistake was being impatient and not being able to find any installation notes, and pretending that I knew what I was doing by installing the rom via CWM mod.
Here's the rub, for some reason, whenever I did the 3 finger salute, it would pull a RED CWM that went orange when I applied update.zip ... because if I tried to install rom from sd card with the initial CWM boot, it wouldn't install anything, it would just error out unless I applied update.zip. After selecting apply update from zip, it would boot the orange CWM and allow me to install whatever I wanted...
So after applying the OMFGB rom, it showed the Fascinate/ Cyanogenmod 7 bootscreen, then went to boot loop. I panicked, pulled the battery, then backed up everything to my computer, and formatted the sd card in FAT32 with Windows 7 64 bit...
Shortly thereafter, I was using ODIN and the original "return to stock" files, and ended up getting into the stock OS.
Now I never show 3G or even 1x, and never pull data at all... when I go to place calls, it says that verizon cannot authenticate my phone... when I activate, it reboots and says everything was successful, but was noticeably a faster process than standard activation. Upon reboot, nothing improves... the os is there, everything shows that everything is fine, yet I am still not able to place calls...
Here is where it gets weird... My wife called me today, and the call came through... I received text messages, but still couldn't make calls... My bill is zeroed out, I'm not locked out that I know of, and I just want my phone working again...
Running out of ideas. I have flashed ED01 DL01 and even reapplied the stock .PIT in odin... I am going to try heimdall while I wait for help from here, but any quick help would be GREATLY appreciated...
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I will definately take this into consideration, but first i want to confirm that my phone is in full working order...
I appreciate the quick response, and hope to get some more love from the community.
Sent from my Transformer TF101 using XDA Premium App
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Trying this in about 15 minutes, will report asap...
Again, thanks for help...
Sent from my Transformer TF101 using XDA Premium App
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
martyr2k6 said:
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
Click to expand...
Click to collapse
also, lets assume I am completely as stock as possible... how should I get CWM on, and which version please link...
Also it miht be worth mentioning, though I think I already did... but when I go to activate my pjone, it says its successful, but then I go to make a call and it say that verizon annot authenticate my phone...
Here's a confusing screenshot...
Sent from my Transformer TF101 using XDA Premium App
Alright the issue is resolved, my main concern was whether or not I could use my phone for phone calls... after finally mustering up the guts to call Verizon, it turned out that the main problem in which I was experiencing was due to some form of typical midnight updates that big red does... apparently, my phone, missed some form of update that ended up de-authorizing my phone, but Verizon was able to help out, even at this late hour.
On the good note, everything went through just fine as far as flashing cm7... I just seem a bit conflicted with which rom is best. I guess its just a matter of personal preference, really. So far I prefer jt's rom just fine, but I might be switching back and forth between jt's and omfgb...
Thanks again for all the help folks, I appreciate it more than you could know.
Sent from my Transformer TF101 using XDA Premium App
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Not sure that I totally understand as to why I need to flash cm7 0713, then omfgb, then reflash cm7 0704... seems a bit redundant.
If you could clarify this for me and what improvement this offers, I would appreciate it.
Sent from my Transformer TF101 using XDA Premium App
Because omfgb apparently doesn't convert to mtd but cyan does, so you have to flash cm first
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yup, that was your mistake. prior to flashing omfgb, you need to be on jt's cm7.
I'm too lazy to read all the posts but try flashing cm7 via cwm4. then, Odin back to stock using the right files and configurations. there's a sticky in the development section.
I have been having this problem even after doing everything correctly:
I wanted to try this ROM here:
http://forum.xda-developers.com/showthread.php?t=1195912
So I went back to stock using the ODIN files from here:
http://forum.xda-developers.com/showthread.php?t=734475
Then used the GB bootloaders from here:
http://forum.xda-developers.com/showthread.php?t=1117990
Installed CMW recovery. Once done, I used the zip to install the rom.
Now the phone boots up, goes to the bullet screen after sometime boots up again. Any idea guys?
go back into cwm and wipe data/fact reset
wipe cache
reboot system now
While in your bootloop get back into recovery and reflash the rom (I had to do this on Miui and Simply Honey when I first installed them)
why would they do that though? ^^^
vabeachfc3s said:
why would they do that though? ^^^
Click to expand...
Click to collapse
I don't know why it worked but it worked for me
Sent from my SGH-T959 using XDA App
Tried both the methods. Nothing seems to work.
I tried disabling vodoo and re-flash. The problem I have then is it just loops. When vodoo is enabled it goes to data parition not enough space issue.
Any help anyone?
Did you wipe date/factory reset, wipe cache, and wipe dalvik before flashing rom then wipe cache and dalvik and fix permissions before rebooting?
EDIT: Also I would backup everything on your SD cards. I got that not enough space on partition before and it ended up wiping my sd cards.
Sent from my GingerZen Vibrant using XDA Premium App
yes I did. Well looks like vodoo lagfix did its number on me. The internal data has been cleaned up , I am having MBR checksum errors and still doesn't work.
Also you can try this instead of odining back to jfd stock. It's worked really well for me when I've had major problems. Cleans everything up really good.
(QUOTE=Br1cK'd;16231313]Themes
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.[/QUOTE]
Sent from my GingerZen Vibrant using XDA Premium App
Current issue
Odin recognizes phone. I can get to download mode. it turns off. Ive let it set for 24 plus hours prior to this and there is no change. It will stay on for 10 to 15 seconds then turn off.
I have repartitioned, put in a new pit and kernel. it will not stay on long enough to install a new ROM.
leading up to this i had a sleep of death issue. that progressively got worse. It would turn on and be fine tell it went to sleep i could use all the apps if i stopped and it went to sleep i would have to reboot. I had during this point cleared all the cache devlik etc. to no avail. i then decided to flash to stock. I got about 10 seconds into the ROM flash and it turned off. now I'm at the point described above.
This has been w/ and w/o sim and external flash memmory
Thank you for any suggestions and help.
How old is your battery, and what kernels have you experienced this with?
What is a quick recap of what you were running/tried while this SOD problem started occurring, seems related to the DL mode shutting off.
Battery is the orginal, but i have 2 batterys 2 vibes. i switch batteries every month or so due to im more battery heavy then my wife, i have used them both fully charged.
Icy Glitch or subzero, though i think it was Icy. i was running slim ics. this is the only kernel i have ever had a sod problem.
Only extra apps i have installed or had issue with, 1 kindle stopped working on me well b4 any of this happend around 3 weeks or so. i installed adilko. Also installed calorie counter and myfitness pal these are the only 2 that really can be related. I had started using myfp more then the other for cutting.
only run music for during work, eh and for books, no games. i use advanced task killer to kill extra apps, a couple times a day to save on battery,
otherwise phone calls and txting.
Can you boot to recovery mode? If you can, try a factory data reset. You could use adb to push a kernel zip to your internal sd and flash through cwm but only if you can actually boot into recovery mode. If that doesn't work you could try flashing a different kernel through odin. Kernels usually flash in less than 10 seconds in my experience.
Sent from my SGH-T959 using Tapatalk 2
I have already flashed a new kernel and pit.
i cannot get into recovery.
i can get on odin long enough to put a pit and kernal and repartition.
this made no change to my problem.
Have you tried flashing a custom kernel like Semaphore with CWM included and then try booting into CWM?
eksasol said:
Have you tried flashing a custom kernel like Semaphore with CWM included and then try booting into CWM?
Click to expand...
Click to collapse
flashed semaphore. was able toget into cwm for 10 seconds before it shut down on me. now at least for a few seconds i have cwm. wait a sec it kept rebooting into it i cleared dev init.d cache fixed permissions, i was able to mount my usb, still mounted for a few min i think it might be good. ill update, im thinking init.d was the culprit. ill update in 10 min or so to see if i can ge back on my phone.
Bankai247 said:
I have already flashed a new kernel and pit.
i cannot get into recovery.
i can get on odin long enough to put a pit and kernal and repartition.
this made no change to my problem.
Click to expand...
Click to collapse
I was meaning to flash a stock kernel only, then flash back to stock JFD. I'm pretty sure you don't load a pit file when flashing just a kernel but I could be wrong, it has been awhile since I flashed a kernel through odin.
Sent from my SGH-T959 using Tapatalk 2
So i have been able to finaly get back to stock yay. its staying on long enough to get there. im flashing it now. and its up. SO If anyone has a Download sod error,
1 turn odin set pit and semaphore.
2 download mode , check for sync
3 install from odin.
4 it will reboot into cwm clear everything.
5 i cleared davlik, cache, init.d, then wiped/factory reset/ then cleared nstools, init.d davlik cache and fixed permisions.
6 odin back to stock.
7 look at the stockness get sick puke in local trash receptor. find some amazing devs goodness of your choice. thank them and all the helpfull people on the xda forums.
thank you all for your help im back to stock no SOD im golden.
big time thanks to eksasol for the semaphore tip