Ok so I ran Jt's vanilla gingerbread for about week and a half and even tho I loved what I saw the rom was to unstable for me. No fried sd card issues but recovery problems and bootlooping issues. So I odined back to stock ed05(full odin) and after flashing CWR v4 decided to go with powerwash debloated ed05. After and foreclosure issue I did a complete wipe and factory reset and flashed a recovery for the powerwash from the sd card (that I had made right after I had flashed the recovery thru odin) Here's the strange part, the recovery had an error and the phone went into boot up. The bootloop from the vanilla gingerbread rom came up (even tho odined over) and now is stuck in a bootloop again. The same as when I was on vanilla gingerbread. No biggie here as verizon is in the process of replaceing the phone just and F.Y.I. maybe help understand some of the issues with gingerbread. P.S. the bootloop starts as triangle with the android robot then right into the cyanogen logo then starts over.
Wait... You sent your borked phone back to Verizon?!
Sent from my SCH-I500 using XDA Premium App
ghostt021 said:
Ok so I ran Jt's vanilla gingerbread for about week and a half and even tho I loved what I saw the rom was to unstable for me. No fried sd card issues but recovery problems and bootlooping issues. So I odined back to stock ed05(full odin) and after flashing CWR v4 decided to go with powerwash debloated ed05. After and foreclosure issue I did a complete wipe and factory reset and flashed a recovery for the powerwash from the sd card (that I had made right after I had flashed the recovery thru odin) Here's the strange part, the recovery had an error and the phone went into boot up. The bootloop from the vanilla gingerbread rom came up (even tho odined over) and now is stuck in a bootloop again. The same as when I was on vanilla gingerbread. No biggie here as verizon is in the process of replaceing the phone just and F.Y.I. maybe help understand some of the issues with gingerbread. P.S. the bootloop starts as triangle with the android robot then right into the cyanogen logo then starts over.
Click to expand...
Click to collapse
..Did you format your phone with the atlas 2.2 PIT file when returning to ED05?
ccampos784 said:
..Did you format your phone with the atlas 2.2 PIT file when returning to ED05?
Click to expand...
Click to collapse
Yes sir. The more I think about it I'm wondering if maybe somehow something from gingerbread remaining on the sd card even tho I also reformatted when I went back to stock.
Skrazz said:
Wait... You sent your borked phone back to Verizon?!
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Yep. But I flashed it back to stock and did to OTA up date.
You flashed an mtd recovery than flashed a bml rom with mtd recovery. cwm4 should not have even been flashed if you had no intention of flashing an mtd rom.
good day.
chopper the dog said:
You flashed an mtd recovery than flashed a bml rom with mtd recovery. cwm4 should not have even been flashed if you had no intention of flashing an mtd rom.
good day.
Click to expand...
Click to collapse
I thought so too. However the first time odined back to stock and flashed powerwash it had it's own CWR v4 are to two different? They look to same except for the logo (rom manger on gb and a banana on pw)
ghostt021 said:
I thought so too. However the first time odined back to stock and flashed powerwash it had it's own CWR v4 are to two different? They look to same except for the logo (rom manger on gb and a banana on pw)
Click to expand...
Click to collapse
Interesting, I hadn't noticed that. I Odined a full stock tar package with the stock recovery when I came off of VGB. Now on Powerwash CWR shows as v4.0.1.4 with a banana background. I don't see any mention of this in the Powerwashed OP. Any clue what's going on? I may try a full reflash tonight if I get the time. It will distract me from debating whether to go back to VGB.
drnihili said:
Interesting, I hadn't noticed that. I Odined a full stock tar package with the stock recovery when I came off of VGB. Now on Powerwash CWR shows as v4.0.1.4 with a banana background. I don't see any mention of this in the Powerwashed OP. Any clue what's going on? I may try a full reflash tonight if I get the time. It will distract me from debating whether to go back to VGB.
Click to expand...
Click to collapse
Wish I knew. I odined the stock packages three times myself. Once my phone was reading only half of the sd card (nothing thru gallery had to use astro to view pictures) music was fine. So I reformatted the card and Odin the stock package just to be safe. Also I just a error status 7 message in recovery and then a bootlloop. So I odined back to stock using the package with pit file thinking maybe I goofed something. I flashed vgb again with no theme(just in case that was the problem) it ran great for a couple of days, then I pulled my sd card to load some wallpaper onto it from my ps3 and when I placed the card back in the phone same problem nothing could be viewed in gallery even tho phone showed card was present thru setting and under sd card and storage.. When I booted into recovery again I got status 7 error cant' mount recovery followed by the bootloop from hell. So using the odin package I odin back to stock and this time only flashed cwr v4 recovery (that's when I noticed the different logo) I did nothing else I was running debing,debloated Ed05 did a factory reset cause my contacts was dulipating bad from 171 to 829. As soon as I rebooted I got the cyanogen logo followed by the triangle with a "?" bootloop from hell. Not sure what happened again wish I knew
drnihili said:
Now on Powerwash CWR shows as v4.0.1.4 with a banana background.
Click to expand...
Click to collapse
Sounds like that is the 0808 PBJ kernel.
xwhofarted said:
Sounds like that is the 0808 PBJ kernel.
Click to expand...
Click to collapse
That would be my guess about the banana, but I'm a bit confused by the CWM4. Does powerwashed routinely install that?
drnihili said:
That would be my guess about the banana, but I'm a bit confused by the CWM4. Does powerwashed routinely install that?
Click to expand...
Click to collapse
I would assume since the PBJ is the latest kernel out there for Froyo and TW. I wouldnt see why it wouldnt be included.
Related
Just updated flashed my phone to Axura 2.3.1.2 and for some odd reason the boot animation keeps rebooting. I've disabled voodoo lag fix and I am still experiencing the same problem. :-?
Previous rom was axura 2.2.1 froyo rom for eclair
diceburna said:
Just updated flashed my phone to Axura 2.3.1.2 and for some odd reason the boot animation keeps rebooting. I've disabled voodoo lag fix and I am still experiencing the same problem. :-?
Previous rom was axura 2.2.1 froyo rom for eclair
Click to expand...
Click to collapse
Which rom specifically?
Also you shouldnt have to disable voodoo if you are coming from another voodoo rom.
have you tried reflashing the rom?
I got the same prob. Try to get back to stock T959UVJFD using odin and reflash.
Axura is nice but it shows many compatible troubles when trying with different kernels/mod.
I tried reflashing several times but no luck so far. And the previous rom I was using was the froyo rom for eclair the download zip file name is AXURA22VE...I'm thinkin I should probably have ODIN to stock Eclair, then update my phone to stock froyo before flashing this rom.
dont bother with stock froyo just odin to jfd then root install cwm and flash the rom
going to stock froyo includes the updated 3e recovery which can be circumvented but requires extra work on your part.
Thx shreddintyres :-D
You know I forgot to state this earlier but I can get to recovery mode (cwm v2.5.1.3 red lettering not green) should I just do a backup and restore from there?!?! I am not sure if the axura 2.3.1.2 file I have is corrupt or is it something I am doing wrong on my end when flashing the rom?
diceburna said:
Thx shreddintyres :-D
You know I forgot to state this earlier but I can get to recovery mode (cwm v2.5.1.3 red lettering not green) should I just do a backup and restore from there?!?! I am not sure if the axura 2.3.1.2 file I have is corrupt or is it something I am doing wrong on my end when flashing the rom?
Click to expand...
Click to collapse
Sounds like a bad download to me. I would redownload it. I flash in the red cwm all the time.
nomadrider123 said:
Sounds like a bad download to me. I would redownload it. I flash in the red cwm all the time.
Click to expand...
Click to collapse
same here
@op when did you download axura 2312? the D4A server went down a couple days ago and we are trying to restore all the files on the new site.
Redownloading 2312 will be not be possible at this point in time, i have posted a download for 2310 in the Axura development thread until the site is fully functional again. there isnt a very large difference between 2310 and 2312.
if you are still able to add files to your phone i would try to flash from CWM first otherwise if you cant jfd will be your only choice.
Hope this Helps
Thx guys I'm in the process of recovering from cwm now, tbh I haven't used ODIN before so before I try it hopefully my nandroid backup will restore everything. I downloaded the 2.3.1.2 rom I believe the day it came out.
the downloads on the d4a webiste are back up for the vibrant rom
http://devsforandroid.com/index.php?topic=23.0
Sweet I just finished dl'ing 2.3.1.3 hopefully it all works out. BTW I was able to easily restore my backup...flashin new rom now will update soon.
thanx men that really helps
All is well :-D I guess the old file I had was corrupted bc I flashed this rom w/ no problems at all...Thx
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
Has anyone tried the ED04 OTA to see if it helps any issues? The only thing it says on the website is that it improves incoming call connectivity, but then there might be other things they don't list.
Just curious.
where do i get it
strauss0829 said:
where do i get it
Click to expand...
Click to collapse
Right now probably only by OTA, which means you'd have to go back to stock.
Sent from my SCH-I500 using XDA App
No, they are just using it to catch people tethering.
how do i go back to eb01 stock if i have the tar file ????
strauss0829 said:
how do i go back to eb01 stock if i have the tar file ????
Click to expand...
Click to collapse
You won't be able to OTA to ED04 from EB01. You can odin to DI01 or DL09 or maybe the ED01 (which doesn't have the modem i believe) Follow this guide:
http://forum.xda-developers.com/showthread.php?t=782204
Hope this helps.
Sent from my SCH-I500 using XDA App
ED04 + CWM 3.x = Can't backup boot
I had to Odin back to stock (long story - but hey we've all been there) and saw there was an update beyond ED01 and thought "what the heck..."
I'm now rocking ED04 and thought it might be a good idea to grab a nandroid backup so I Odin'd ClockworkMod (Times Infinity 5.8.11) and entered recovery on first boot (since the Verizon kernels have a tendency to kill CWM).
So far so good, selected backup and saw "Backing up boot image..." then "Error while backing up boot image!"
(before anyone asks I have over 5GB free on the SD card and it is inserted and mounted)
EDIT: Sounds like this won't work. I guess you need to flash and boot a custom kernel first.
martian21 said:
I had to Odin back to stock (long story - but hey we've all been there) and saw there was an update beyond ED01 and thought "what the heck..."
I'm now rocking ED04 and thought it might be a good idea to grab a nandroid backup so I Odin'd ClockworkMod (Times Infinity 5.8.11) and entered recovery on first boot (since the Verizon kernels have a tendency to kill CWM).
So far so good, selected backup and saw "Backing up boot image..." then "Error while backing up boot image!"
(before anyone asks I have over 5GB free on the SD card and it is inserted and mounted)
Weird error or *tin foil hat* VZW conspiracy???
Click to expand...
Click to collapse
Neither. Known issue with that CWM. I'm trying to find the link to nemesis2all's cwm. I believe that one will do nandroid backups.
Here it is:
http://www.multiupload.com/8VDE8GX69P
Problem with this one is won't wipe dalvik and gets hung up during the data wipe. Data wipe completes, it just doesn't look like it completes because it gets hung up
Well the main issue that was supposed to be addressed is improved incoming call connectivity but today my wife tried calling me twice and my phone only showed one missed call. So I'm not sure it helped at all or not.
Sent from my SCH-I500 using XDA App
Have some employees who had issues with the last update of camera not working, etc. Wonder if this would fix that for them.
vlucchetti said:
Have some employees who had issues with the last update of camera not working, etc. Wonder if this would fix that for them.
Click to expand...
Click to collapse
You reminded me that my camera would fail after using a 3rd-party app that accessed the camera in ED01 or 03. I just tried it, and apparently this update HAS fixed that.
Looks like my OTA just forced the ED04 update. Blew away SU and CWM.
Question is, can I put back the ODIN (red) version of CWM?
ec01 comm rom 2.0
I have com rom 2.0 and currently on the EC01 modem and the OTB 1.6 kernel. CWM v3.2.0.0.otb
I was doing some side by side speed tests with my moms completely stock ed04 fassy and hers was goign about 3 times faster if not more.
We were both at 2 bars of VZW signal and i got about 200-400 kbps and she was getting 1000-1200 kbps.
So I got to get onto the ED04 now. I am at work and will be doing this at home tonight.
From my research I have seen that I need to ODIN back to DL09 and then CMW straight into the ED04 modem
research done
So will this wipe any data or is it just simply just going to revert and then upgrade just the modem. Will CWM Still be there after reverting back to DL09? Or do i need to reflash in ODIN and which version is best if so? And then three button (vol up, vol down, and power) boot into CWM to flash my OTB 1.6 kernel back on? then boot as normal? or will this kernel not work.
Thanks for any feedback
Josh
NRadonich said:
Looks like my OTA just forced the ED04 update. Blew away SU and CWM.
Question is, can I put back the ODIN (red) version of CWM?
Click to expand...
Click to collapse
Yes
10 char
Jduke705 said:
I have com rom 2.0 and currently on the EC01 modem and the OTB 1.6 kernel. CWM v3.2.0.0.otb
I was doing some side by side speed tests with my moms completely stock ed04 fassy and hers was goign about 3 times faster if not more.
We were both at 2 bars of VZW signal and i got about 200-400 kbps and she was getting 1000-1200 kbps.
So I got to get onto the ED04 now. I am at work and will be doing this at home tonight.
From my research I have seen that I need to ODIN back to DL09 and then CMW straight into the ED04 modem
research done
So will this wipe any data or is it just simply just going to revert and then upgrade just the modem. Will CWM Still be there after reverting back to DL09? Or do i need to reflash in ODIN and which version is best if so? And then three button (vol up, vol down, and power) boot into CWM to flash my OTB 1.6 kernel back on? then boot as normal? or will this kernel not work.
Thanks for any feedback
Josh
Click to expand...
Click to collapse
You are only changing the modem so no data will be wiped or lost. I did this last night, ODIN DL09 modem, reboot, confirm baseband of DL09, boot to CWM, flash DL09 to ED04 zip file, boot phone, confirmed baseband of ED04. Didn't lose root or CWM and process took all of 10 minutes. Phone does seem snappier now.
landshark68 said:
You are only changing the modem so no data will be wiped or lost. I did this last night, ODIN DL09 modem, reboot, confirm baseband of DL09, boot to CWM, flash DL09 to ED04 zip file, boot phone, confirmed baseband of ED04. Didn't lose root or CWM and process took all of 10 minutes. Phone does seem snappier now.
Click to expand...
Click to collapse
Shark, can you link to those files or the thread?
I know you know your stuff Landshark. Appreciate the fast response and now just impatient to get home and do this myself
Thanks again
vlucchetti said:
Shark, can you link to those files or the thread?
Click to expand...
Click to collapse
If you look at my first post there. I Have it linked in research http://forum.xda-developers.com/showthread.php?t=1097355
scarfman4 said:
Has anyone tried the ED04 OTA to see if it helps any issues? The only thing it says on the website is that it improves incoming call connectivity, but then there might be other things they don't list.
Just curious.
Click to expand...
Click to collapse
Updated last night to ED04 stock. Had fascinate sitting on desk this morning, called it from land line and it just sat there and went to vm.
Has not fixed anything
Sent from my SCH-I500 using XDA Premium App
Running CommROM 2.0. Performed ED04 update as per LandShark instructions. Unquestionably, the phone seems much smoother and snappier. Called phone from home landline, no problems. Quite content with the improvement resulting from the ED04 update.
I can't seem to get CM7 installed. This is the process that I am following:
1. ODIN EB01, let boot, pull battery
2. ODIN CWM 4.0.1.0 (The blue one)
3. Boot into recovery
4. Install CM7 from zip on SD card
Every time I do that, it shuts down, and reboots back into recovery, and says waiting for SD card and does a countdown. Once it goes to 0, it starts over again.
Any ideas?
I decided to jump to CM7 tonight...Installed cwm4 for cm7...wiped data,cache,dalvik...stuck on reboot loop to mount SD card as well.
JJHunterx said:
I decided to jump to CM7 tonight...Installed cwm4 for cm7...wiped data,cache,dalvik...stuck on reboot loop to mount SD card as well.
Click to expand...
Click to collapse
Nice to know someone else is in the same situation....
Any help?
eteusch1 said:
Nice to know someone else is in the same situation....
Any help?
Click to expand...
Click to collapse
Just curious...What size sd card are you using?
eteusch1 said:
I can't seem to get CM7 installed. This is the process that I am following:
1. ODIN EB01, let boot, pull battery
2. ODIN CWM 4.0.1.0 (The blue one)
3. Boot into recovery
4. Install CM7 from zip on SD card
Every time I do that, it shuts down, and reboots back into recovery, and says waiting for SD card and does a countdown. Once it goes to 0, it starts over again.
Any ideas?
Click to expand...
Click to collapse
Make sure you are also using the pit file with eb01...I'm sure you were but just saying....that said, do all the steps you posted exactly but use the 3-30 fix all recovery, make sure you wipe everything and flash cm7..after words you can power button menu to your new blue recovery and flash the glitch kernel if you want or any other kernel, radio, or gapps zip files
Sent from my SCH-I500 using XDA App
I followed the steps Here using the ED05 file, odin'ed the cwm4 for CM7, and then installed CM7.
Every time CM7 boots, it boots into safe mode. At the loading screen it does a long vibrate.
I finally gave up because it refused to mount my sd card in cwm4...couldn't install gapps or any other mtd rom.
Going back to comrom 2.1
I'm using the original 16GB SD card. I cleared it out and even formatted it. I also used the PIT file everytime I Odin'd EB01...
JJHunterx said:
I followed the steps Here using the ED05 file, odin'ed the cwm4 for CM7, and then installed CM7.
Every time CM7 boots, it boots into safe mode. At the loading screen it does a long vibrate.
I finally gave up because it refused to mount my sd card in cwm4...couldn't install gapps or any other mtd rom.
Going back to comrom
did you try using the 3-30 fix all recovery?
I've gone back and fourth a few times and the 3-30 fix all recovery is the only one that works for me...the cwm4.x.x.x for some reason doesn't like my phone until I'm on a cm7 build.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
A few things I'm not clear about before jumping to a CM7.
Do you need to use the EC09 modem for a gingerbread rom?
Does it matter what CWM you use to get from ComRom to CM7? (need to odin the CWM 4 first?)
Thanks
sfd0124 said:
A few things I'm not clear about before jumping to a CM7.
Do you need to use the EC09 modem for a gingerbread rom?
Does it matter what CWM you use to get from ComRom to CM7? (need to odin the CWM 4 first?)
Thanks
Click to expand...
Click to collapse
The ec09 radio is not necessary...but I've had the best results with it.
Jt has the 4x.x.x recovery in the cm7 o.p. But that is if you are having trouble getting cm7 to take.
I've used the otb 3.x.x.x, and times infinity's 3x.x.x, with no problem but I know some folks have had issues...I recommend the 3-30 fix all because it supports amend and edify scripting so it seems to work better, for me at least.
Other than that it really is the same way of flash any other rom, wipe everything and flash. its going from cm7/miui/to any other rom because of the different formats...cm7/miui/(mtd)
To go from an mtd build back to a non mtd build you must flash an official verizon build with the atlas 2.2pit file to properly repartition your files.
Also once on cm7...no more three finger boot...power button menu...reboot recovery, or
Terminal emulator..reboot recovery only, it will be the blue 4.x.x.x.
once your on cm7 you only use that recovery to flash kernels and zip files.
Sent from my SCH-I500 using XDA App
efan450 said:
The ec09 radio is not necessary...but I've had the best results with it.
Jt has the 4x.x.x recovery in the cm7 o.p. But that is if you are having trouble getting cm7 to take.
I've used the otb 3.x.x.x, and times infinity's 3x.x.x, with no problem but I know some folks have had issues...I recommend the 3-30 fix all because it supports amend and edify scripting so it seems to work better, for me at least.
Other than that it really is the same way of flash any other rom, wipe everything and flash. its going from cm7/miui/to any other rom because of the different formats...cm7/miui/(mtd)
To go from an mtd build back to a non mtd build you must flash an official verizon build with the atlas 2.2pit file to properly repartition your files.
Also once on cm7...no more three finger boot...power button menu...reboot recovery, or
Terminal emulator..reboot recovery only, it will be the blue 4.x.x.x.
once your on cm7 you only use that recovery to flash kernels and zip files.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I made it to CM7 after I started fresh with the offical ED05 + Pit file. After CM7 was installed, the cwm that came with CM7 refused to mount my sd card.
At one point while in CM7, it told me my sd card was damaged so I wiped it (everything was backed up)
I'm back on ComRom 2.1 and it's working fine.
Forgot my other question: do you need new drivers after cm7, does your computer see it as a new device?
Yes, (correct me if I'm wrong) I think they are the same ones used for the Nexus.
JJHunterx said:
Yes, (correct me if I'm wrong) I think they are the same ones used for the Nexus.
Click to expand...
Click to collapse
The build is from a nexus s, so you may need the drivers for the nexus,however I have never needed them...my pc still recognizes my phone...I don't think it actually says fascinate like it used to, but I can still move files with no problem and (more importantly) odin still recognizes my phone!
You may even need the samsung generic drivers but either way those aren't hard to find either.
As side note I'm using vista home edition, in case yet matters, a lot of complaints I've heard are from windows 7?!?...hope some of this helps
Sent from my SCH-I500 using XDA App
What version of the rom are people using? I've been following the wiki here and using the versions linked.... Still haven't had any luck.
eteusch1 said:
What version of the rom are people using? I've been following the wiki here and using the versions linked.... Still haven't had any luck.
Click to expand...
Click to collapse
I used the cwm and CM7 from JT's thread since he has mms working in that build...I had sd card problems in cmw (cannot mount sd card) and in the rom (damaged sd card) itself so idk what the problem is.
sd card works fine on ComRom.
JJHunterx said:
I used the cwm and CM7 from JT's thread since he has mms working in that build...I had sd card problems in cmw (cannot mount sd card) and in the rom (damaged sd card) itself so idk what the problem is.
sd card works fine on ComRom.
Click to expand...
Click to collapse
I tried those as well with the same result. Currently running ComRom as well.
Try and odin the 3-30 fix all recovery...immediately 3 finger boot...wipe every thing and flash cm7
Sent from my SCH-I500 using XDA App
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...