I tried to re-install packages after I flashed clockworkmod recovery and got an error
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
How to fix this. Someone suggested re-root with a simple script included. .... Sorry I'm a noob and learning everything
Doesn't work with the latest stock ROM
I am a noob like you. I reinstalled the stock ROM using the AIO Vibrant Toolbox. Than I upgraded to the latest stock ROM using the Kios. But the Clockworkmod recovery did not work just like yours.
After spending hours and trying several different ways without any luck, I decided to start over. This time I did not load the latest ROM update with Kios. This time I was able to load Clockworkmod recovery. I think it has a problem with the latest stock recovery software.
with the stock 2.2 you need a modified recovery. stock uses 3e recovery so you need to odin supercurios ka6 voodoo kernel or go thru the dev section and do the steps for the modified 3e recovery.
the drugstore said:
I tried to re-install packages after I flashed clockworkmod recovery and got an error
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
How to fix this. Someone suggested re-root with a simple script included. .... Sorry I'm a noob and learning everything
Click to expand...
Click to collapse
I posted a link for you over in the Trigger thread to the recovery hack you'll need, but here it is again since this would have been the correct place for me to have placed it in the first place!
jmcghee1973 said:
with the stock 2.2 you need a modified recovery. stock uses 3e recovery so you need to odin supercurios ka6 voodoo kernel or go thru the dev section and do the steps for the modified 3e recovery.
Click to expand...
Click to collapse
How do I ODIN supercurios KA6 Voodoo Kernal. I have the .tar file... Then can I flash the overstock kernal on top of it
Droidificator said:
I posted a link for you over in the Trigger thread to the recovery hack you'll need, but here it is again since this would have been the correct place for me to have placed it in the first place!
Click to expand...
Click to collapse
Tried that and it no worked. Can I Odin Supercurio's KA6 Voodoo kernal like another user stated...If so How do I ODIN it.....Also can I flash the Overstock kernal after that
Download Odin
open it up on your pc
turn off your phone & plug the USB into your phone
hold down both of the volume keys (not the power key)
plug the other end into pc
should be in download mode
check to see if you have a yellow COM port in ODIN
if you do, place the KA6 voodoo.tar in the PDA line of ODIN and hit start
it will take some time 5 or 10 mins...and your phone will reboot on its own..
DONOT do anything to it while this process is happening..
find an app on market called Quick boot and then you can CWM recovery flash the Overstock kernel or use Kernel Flasher to flash Overstock kernel.
there is also the AIO toolbox in the DEV section you could use
try this on for size...worked for me. Hopefully for you too.
Let us know your results.
http://board.teamwhiskey.com/viewtopic.php?f=3&t=309&p=18097&hilit=grendel905+recovery#p17971
I did odin and it said not enough space on partion and something else enabled.
I re-booted into red recovery, YEAH.... What did it mean not enough space on partion?... Should I use SGS Kernal flasher and load over stock? I think I did it last night and overstock never booted
I Give Up, Somebody please help me
I'm trying to load the the overclocked kernal with voodoo sound for my Vibrant. I have rooted it, I used Odin to load supercurio's KA6 Build With Voodoo, it loads however the voice says said not enough space on partion and something else enabled.
I re-booted into red recovery, YEAH.... What did it mean not enough space on partion?... Should I use SGS Kernal flasher and load over stock? I think I did it last night and overstock never booted
I loaded Overstock through red recovery and it bricked my phone
I even tried using clockworkmod recovery, but cant get the 3e to 2e converison to work. Any idea's. I have odin back to stock so many times. Im frusterated
Related
Just to make sure I am doing this correctly. Im using a TMO Vibrant, running stock 2.2 froyo KA6. This is not the 4G model. I wanna load the kernal from cmered Overstock with voodoo
1. Rooted phone using superoneclickroot
2. Download SGS Kernal Flasher from market, and gave it superuser permission
3. moved Overstock to my external sd on phone which has 5.33gb left
4. opened SGS Kernal flasher and will choose kernal to load
5. After flashing kernal will go to market and download Voodoo app and BLN app
Am I missing anything?
Anybody
I would just backup your current kernel with kernel flasher and reboot into recovery to flash overstock. Do you have clockwork installed from rom manager?
Sdobron said:
I would just backup your current kernel with kernel flasher and reboot into recovery to flash overstock. Do you have clockwork installed from rom manager?
Click to expand...
Click to collapse
no i dont have clockwork rom manager installed, I thought I could just use the SGS kernal flashing app? am I thinking wrong
No biggie people get wound up about backing up you can reinstall apps if you lose them
I would download Rom manager and titanium backup
Here is what i do:
1. Copy my internal sd card to my external card in a folder called "back up int" (this is in case you lose everything from a bad flash)
1.A. If you have Titanium backup I would back up everything to that.
2. Then flash your new rom
3. Then root the phone
4. Then Down load Rom manger
5. Restore from Titanium backup
Then you are good to go......
5. Then restore with
I tried to re-install packages after I flashed clockwordmod recovery and got an error
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
the drugstore said:
I tried to re-install packages after I flashed clockwordmod recovery and got an error
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
If you are on 2.2 you have to use superone click root again and run a script there is a thread on how to do this its simple but the clockworkmod wont work unless you go back to 2.1.
Sent from my SGH-T959 using XDA App
why cant I use sgs kernal flasher?
Nobody really uses that around here. Everybody flashes from clockwork. Id look up the info a few posts above and get rom manager working on your phone.
Trigger + Overstock = Awesomeness
do i placed overstock file on internal or external sd card.
the drugstore said:
do i placed overstock file on internal or external sd card.
Click to expand...
Click to collapse
Internal...the 16 gig
I moved zip file to internal memory
Flashed via SGS Kernal Flasher. I couldn't figure out how to get clockwork recovery to work, anybody have any pointers?
the drugstore said:
Flashed via SGS Kernal Flasher. I couldn't figure out how to get clockwork recovery to work, anybody have any pointers?
Click to expand...
Click to collapse
Here is the link: Please Click Here!
Once you have followed the instructions provided in that thread, you SHOULD be good to go. If you are having issues with getting the 3e mod/hack to work, hook up to SuperOneClick one more time and "Shell Root" right before you try to do the mod hack, this worked for me.
Let us know how it goes.
PS: this hack only pertains to you if you're running the official 2.2 ROM, not 2.1
Please don't forget to thank the people who help you!
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
RepAZ said:
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
Click to expand...
Click to collapse
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
phonefiend said:
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
Click to expand...
Click to collapse
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
What I meant to say is what you said above: you can boot into CWM right after you flash it, but if you restart again it will go into stock recovery.
fitti28 said:
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
Click to expand...
Click to collapse
I've ODIN'd CWM multiple times but it still gets overwritten with the stock recovery. I'd like to stick with the stock ED01 kernel but can't find any ZIPs to flash this kernel via CWM.
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I can't find anything on that, can you point me to the thread you followed?
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
imnuts said:
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
Click to expand...
Click to collapse
This is unfortunate because I used to run a version of CWM just fine with the stock EB01 kernel. With the current CWMs I finally found a way to get it to work with the stock kernel: rename /system/etc/install-recovery.sh.
got it working yay
BlackHoleSlam said:
got it working yay
Click to expand...
Click to collapse
Tell us how.
i just waited some time and placed the debinged rom from adrenylne on my sd card then used the 3-30 tar and put my self in red voodoo flashed a different kernel theme then rom and all is good
So, disclaimer. I'm an idiot today. Don't mind me.
So today I decided to go to jt's CM7 from ComRom 2.1 (non gingerbread)
Backed up everything, made a nandroid, wiped everything installed cwm 3.x.
Went and started to flash CM7. That didn't exactly like me too much as it went into a 45min long bootloop saying that it failed. No big deal. Nows the fun part. Rewiped everything, started to reinstall the ComRom. That didnt like me either, it says that it cannot mount Cache/recovery/log etc. So I thought. Okay, well I can always ODIN!
Ideas folks?
Thanks in advance.
Sorry about the bump/post, forgot to edit this one instead.
OK! Ignore above, used odin so now im on stock eb01 but still when i use odin to flash cwm 3.0.2.8x it still says it cannot open or mount cache/recovery/log and recovery/last_log.
At this point, I just want to get it so I can nandroid back to where i was on comrom.
Ideas?
What I did, ODIN the atlas2.2 and ebo1 Froyo package, boots up to stock fine no problem.
Attempted to flash CWM 3.0 in ODIN. flashes fine.
3 finger salute. doesnt boot, have to hold it for about a second then cwm just pops up saying it cant mount recovery.
Then I re ODINd eb01, deleted all voodoo, cwm, update.zip etc from sdcard.
re tried to flash cwm 3.0
same thing.
Completely lost haha
New ; odin's dl09, OTA'd up to current. What steps should I take next given my issues with CWM?
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
schu9120 said:
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
Click to expand...
Click to collapse
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
tkirane said:
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
Click to expand...
Click to collapse
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
efan450 said:
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
tkirane said:
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
Click to expand...
Click to collapse
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
efan450 said:
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
Click to expand...
Click to collapse
I definitely know my way around odin and recovery haha thank you very much for the help. I'll try it out once I am out of work and let you know how it goes. I was doing just that only with cwr 3.0 not the fix all. so hopefully that does the trick. Hopefully I wont be seeing and mount cache errors.
So I did use the recovery-all last night to no avail, still says that it cannot mount certain items.
I have to three finger salute it, then let go after a while for it to boot to CWM, then it cannot mount cache:recovery/command and recovery/log and dev/block/st111
Also when trying to wipe data it cannot mount datadata
Then I do reboot system now and it reboots to CWM with same errors.
EDIT : Found an ODIN for EC01 ComRom 2.0
Going to try that out and see what happens.
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
tkirane said:
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
Click to expand...
Click to collapse
Lol glad to hear your up and running...I've had my share of idiotic moments and lucky our phones are pretty brick proof...and now we can add to the list that using a pit file and trying to odin cwr while it won't allow your phone to work..... you can still recover even from this with out perma-bricking!
Sent from my SCH-I500 using XDA App
Well, I was previously running Comm rom, and i decided to switch to CM7 7/13
This didn't go so well. I Odin'd DL09 with atlas and repartitioned then installed Cmw and still Status 7 when I try to install. Then I tried installing 7/4 and it would just say something like "Checking BML" Or something, i forgot... and it would just reboot into cwm. I was running JT's cwm fix, and i tried with cwm all... I don't know what to do. Now my fascinate won't install comm rom, and every rom install just leads up to booting up in cwm.. no samsung logo.. Help??
Edit: Phone is now in "Manual mode"
i guess samsung recovery? but it wont boot. It just reboots into the same recovery after i press "reboot system now"
please? :'(
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
xwhofarted said:
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
Click to expand...
Click to collapse
That's the thing... It wont boot to anything i install on it.. But it sure as hell boots to ANY cwm i install... and it also boots to normal recovery in the absence of a cwm....
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
jamespweb1503 said:
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
Click to expand...
Click to collapse
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
efan450 said:
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I love you <3
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
alemondemon said:
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
Click to expand...
Click to collapse
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
I have same thing, but I cant get the phone to show in download mode to odin anything
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Edit: Just tried to do a restore and the MD5 Sums don't match. I've had to do Odin reset three times today.
I think I might do Vodoo and try to restore that way. I will report back.
alemondemon said:
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
Click to expand...
Click to collapse
No I don't think its omfgb related cause I've never ran that rom but I do think it has something to do with all the different recoveries we have floating around and so many different builds with different formats things are bound to get screwed up...my problem came from forgetting to wipe before flashing a different kernel and got me stuck in a boot loop.
Sent from my SCH-I500 using XDA App
I've had this problem ever since I got my Fascinate and tried to get CM7 on it. (2 days ago) I was always able to flash new builds just fine if I managed to get into the orange recovery and not the CM7 one. I believe the one I used was the one on ROM Manager.
This is kinda upsetting...
Hyphnx said:
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Click to expand...
Click to collapse
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
efan450 said:
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We are having problems with the recovery he posted in his post.
Tried CWM-Recovery-All, turned my phone into muffed up phone. UGH!
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Hyphnx said:
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Click to expand...
Click to collapse
So what rom are you running now?
Sent from my SCH-I500 using XDA App
efan450 said:
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
alemondemon said:
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
Click to expand...
Click to collapse
Yup...boot into the otb 3x.x.x recovery and flash the times infinity.zip and then select reboot recovery while in cwm and it should go from the otb one to the times infinity one...at that point wipe everything and flash cm7 build 7/17..not the nightly....once your on the mtd build you can flash the nightly if you wanted
From the power button menu
Sent from my SCH-I500 using XDA App
Edit: I suppose you could just odin times infinity's recovery...I just happened to have the zip on my sd handy so thats why I did it that way...it was that recovery that worked so you could odin it if you wanted it's in the link you posted try flashing it from ti's recovery..I just got there a little differently
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
humblewarfare said:
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
Click to expand...
Click to collapse
unfortunately a boot loop normally requires odin...use the eb01 tar and the atlas 2.2pit and your phone will be back up and running
From there I would flash com rom and reboot then if you wanna take a stab at cm7...try and flash it with the com rom recovery...if it doesn't work you can just try odin'ing different recoveries as long as you don't let the phone boot fully you can simply pull the battery and try to odin a different recovery.try the one from com rom, the 3-30 fix all, ti's recovery, or jt's fixed recovery...I don't know where I got the file but I also have a recovery named fixed 3 x.x for cm7 but I came remember where I got it.it is important that you let eb01 sit for a few minutes after booting and also let com rom sit for a few minutes after flashing also...I just skipped all the setup stuff to get the main screen and then pulled the battery and started flashing
Sent from my SCH-I500 using XDA App
humblewarfare said:
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
Click to expand...
Click to collapse
I'm running vista home edition...if it matters and I'm using odin v.1.7 try the samsung generic drivers also.but once I'm on cm7 my pc says it doesn't recognize my phone but if I put it in download mode and hook up odin recognizes it...so I'm not sure on that one
Sent from my SCH-I500 using XDA App
alemondemon said:
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
Click to expand...
Click to collapse
Try holding the down button while you plug into your wall charger then just move it to your pc...if that doesn't work...clean the contacts with rubbing alcohol...with the phone off.at worse case there is a jig you can manually force download mode...you can buy or make them
Sent from my SCH-I500 using XDA App