[Q] ED04 - Fascinate Q&A, Help & Troubleshooting

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.

Related

[SOLVED] voodoo help. Please.

Ok, So I flashed superclean 2.7 and it borked my phone. So I used Odin and the EB01 and PIT files mr.adrenalyne gave us as a fix for the situation. So after flashing via odin, I flashed CWR ALL tar file. Up until this everything worked great and I thought my ordeal was over. I opened root explorer and noticed a file called voodoo saved. So I booted into recovery and it went straight to red. Used to go to blue recovery then I would have to apply update.zip to red. So I checked the voodoo in recovery and it said lagfix and voodoo were both enabled. Im very puzzled by this and really only have 2 questions. How did I get voodoo and more importantly how do I get rid of it? As in total stock no traces of voodoo. Any help is appreciated. Thanks
Sent from my SCH-I500 using XDA App
http://forum.xda-developers.com/showthread.php?t=979744
read.
Whats up mike, I followed this method over at the AC forum, It doesnt work. After I disable lagfix and flash a new non voodoo kernel I then go into odin and flash back to stock EB01, boot, flash new CWM all and boom. Back to.voodoo enabled. I think im gonna have to format internal SD card to rid myself of this. Something is off and I cant seem to get of voodoo.
Sent from my SCH-I500 using XDA App
Try adrynalyne's 2.7 fix. There is a tar/odin in there that you should flash. It sounds like a dbdata issue.
After flashing the eb01 all in one, you can flash whatever rom you like.
GrainOsand said:
Whats up mike, I followed this method over at the AC forum, It doesnt work. After I disable lagfix and flash a new non voodoo kernel I then go into odin and flash back to stock EB01, boot, flash new CWM all and boom. Back to.voodoo enabled. I think im gonna have to format internal SD card to rid myself of this. Something is off and I cant seem to get of voodoo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
it does work. you are missing something. if you flash nonvoodoo kernel and you can boot your phone then you dont have lag fix enabled. get quadrent from the market and run it. what is your score.
Ok I finally got it, I took a little trip over to the IRC, where one of the devs helped me figure it out. Turns out I must of picked up a corrupt file somewhere. Ive flashed my phone so many times since DL30 leak showed up I couldnt tell you where it came from, but no matter what I did or flashed I was still showing voodoo. To make a long story short I ended having to use heimdall to go back to the original build, the one before DI01. After that was done I was able to build my way back to EB01. Thanks for the help its all good now.
Sent from my SCH-I500 using XDA App

[Q] Phone seems bricked after flashing OMFGB

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.

[Q] Atlas v2.2.pit causes constant recovery

Ok so I was in the process of trying to install CM7 from Superclean 2.9.2 and tried installing CM7 through CWM (red). Didn't work...so I tried installing the fixes for the recoveries in case it didn't work via Odin...
My phone stayed in the boot animation screen the whole way rebooting into the same animation...
So i flashed dl01 all in one to get it to stock...tried reading up and saw that I was supposed to re-partition with atlas v2.2.pit through odin in conjunction with a full stock app...
everytime I flash something with atlas 2.2 ...it always ends up booting into blue recovery with no way to boot into phone. I've tried the Stock DL09 and I've tried it with the dl01 all in one package...no cigar...
At one point I thought it worked and I saw the boot animation with the cyanogenmod logo...but it errored and kept booting into error in which I could only catch a glimpse of the words...some include "mount"
How can I fix this and be able to install Cyanogenmod 7? Please include step by step...I am aware that it is noob to ask such things, but I've tried searching and came up with solutions that didn't work for me.
Thank You
Did you have "re-partition" checked in Odin when using Atlas? Also, double check the MD5 on the .pit in case the download was corrupted.
Sent from my SCH-I500 using XDA Premium App
Reflash that .pit file with a froyo odin file. EB01 or ED01 will work. Then boot up fully. Then flash the dl09 odin file by itself, no .pit then boot OTA and profit.........
Just a heads up. Dont flash a froyo .pit file with an eclair .tar file. Youll boot into recovery evertime.
Just do what I said and youll be good.
check the repartition box and odin the atlas file first(wait for "pass"message)
reset odin
put phone in download mode again
odin dlo9 or eb01 package (no repartition)
Quick caveat on going OTA from DL09: VZW's updates now skip ED01 entirely and go direct to ED04. Keep this in mind if you prefer ED01
Sent from my SCH-I500 using XDA Premium App
laureanop said:
check the repartition box and odin the atlas file first(wait for "pass"message)
reset odin
put phone in download mode again
odin dlo9 or eb01 package (no repartition)
Click to expand...
Click to collapse
This might work too. but I havnt tried it. I did same thing as you and was told by adryn how to get phone booted back up. This was awhile ago tho..... Good luck.
Sent from my SCH-I500 using XDA App
Jazz848 said:
Quick caveat on going OTA from DL09: VZW's updates now skip ED01 entirely and go direct to ED04. Keep this in mind if you prefer ED01
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
That is true. But you prob want ec09 radio anyway. Best ive used...
Sent from my SCH-I500 using XDA App
no ec09 radio for me anymore. I was running cm7 and decided to install ec09. Stuff started disappearing from my sd card (I mean like entire huge folders). I'm sticking with the EDs
Just re-read OP and noticed you asked for step-by-step. There are a few guides out there, but this one by kidserious is the most up-to-date one I've found and it has yet to give me a single issue: Hope this helps!
EDIT: When using the aforementioned guide, I have always used the DL09 .tar and cannot speak for the EB01 .tar. YMMV
I have been messing with my phone alot lately and have had a bunch of issues(not booting, boot loop, different colore recoveries). So I put together a little folder for myself that gets me back to ED01 TW Debloated and OTB 1.6 kernel. If you would like me to post it or send you the folder with everything you need I can. at work now so it wouldnt be till later tonight
So I've tried starting off with kidserious's way of returning to stock...and it seemed to have worked for me because I was able to see the logo with no problem booting into recovery (red).
But when I tried installing CM7 Test Build 10 via CWM, and it didn't work...it went into repeat boot (blue) and before it started doing that after I saw "Installation aborted"
I'm actually now at a stump of how to install CM7 now...
If your using the DI01 file in ODIN you dont need to have the .pit file. Its a full stock ODIN it already has it. If you flash that to eclair your fine.
Fasinationinmotion said:
If your using the DI01 file in ODIN you dont need to have the .pit file. Its a full stock ODIN it already has it. If you flash that to eclair your fine.
Click to expand...
Click to collapse
I apologize, but I'm confused by this. It's my understanding that the .pit is necessary if you're coming from a Voodoo setup. Are you saying that the DL01 .tar reverts the file system to stock on its own? Not challenging you, per se, just making sure I understand properly.
Sent from my SCH-I500 using XDA Premium App
Jazz848 said:
I apologize, but I'm confused by this. It's my understanding that the .pit is necessary if you're coming from a Voodoo setup. Are you saying that the DL01 .tar reverts the file system to stock on its own? Not challenging you, per se, just making sure I understand properly.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
You've got it right, thats the whole reason for using the atlas and repartition checked, it's to format everything back to rfs(non voodoo) from ext4.( voodoo) or in this case mtd
This it's especially important when coming from an mtd build..ie. Cm7 and going back to an old rfs or ext4 rom. I'm no dev, just a flash a holic but I think of it like this, voodoo is just a lag fix modification of our original rfs(non voodoo) format, while mtd is a completely different format so we no longer have the luxury of a recovery that supports this ability to enable and disable our lag fix (voodoo)...which your new mtd format doesn't support. I don't even think it is possible to make a recovery that will repartition your system in preparation to flash any rom format you want
Again I am no dev and this is how I think of it to make sure I take the appropriate steps...it's just my way of remembering what to do when flashing
This is why every time you want to go back from an mtd build you must repartition with the atlas 2.2 to re format your previous mtd format back to the original rfs
Everyone I've helped with issues going from mtd to rfs/ext4 or vice versa I always suggest
rfs (non voodoo)--->mtd
Odin the 3-30 fix all recovery...immediately boot to cwr
wipe everything and flash newest cm7...(I used the 7/4 build but I see it's no longer available but the newest one works too) and reboot
power button menu to recovery...flash gapps/mtd kernels/misc.zip files you may also have with out wiping and reboot.
odin desired radio...reboot.. done.
Mtd---> rfs/ext4
Odin vzw eb01 with atlas 2.2pit and repartition checked
Fully reboot...then pull batt.
Odin desired recovery..(I still use 3-30 fix all cwr).....immediately three finger boot to cwr wipe everything and flash new rom/kernel (voodoo our non voodoo)...reboot
Hasnt done me wrong yet...no fc...no boot loops just flash a holic goodness!
Sent from my SCH-I500 using XDA App
go to this thread, read about the files you need, flash back to stock. here
Then root, install CWR, follow part of odin heimdall guide on how to keep root on ed builds, then get jt's Cyanogen MTD, supposed to have install issues fixed. here
Hope this gets you what you are looking for.
leonvx671 said:
At one point I thought it worked and I saw the boot animation with the cyanogenmod logo...but it errored and kept booting into error in which I could only catch a glimpse of the words...some include "mount"
Click to expand...
Click to collapse
That happened to me. The download was corrupted. I odined EB01 then odined jt's new recovery, redownloaded cm7, and reflashed.
Sent from my SCH-I500 using XDA App
GrainOsand said:
Reflash that .pit file with a froyo odin file. EB01 or ED01 will work. Then boot up fully. Then flash the dl09 odin file by itself, no .pit then boot OTA and profit.........
Just a heads up. Dont flash a froyo .pit file with an eclair .tar file. Youll boot into recovery evertime.
Just do what I said and youll be good.
Click to expand...
Click to collapse
Please help! I have tried this numerous times, and my phone just keeps booting into stock recovery. It won't let me get past it.
I originally tried the .pit file with dl09 (mistake - I know), and it started the recovery mess. Then I downloaded the "stock" rooted eb01 file (EB01_DXC.tar.md5), and flashed it with the .pit file (atlas v2.2) and re-partition checked.
I have no other clue what's going on. I was just trying to wipe completely fresh to be able to load the CM7 Espresso on my phone. I've been running old CM7's for a while with the glitch kernels.
Help, please - I've been without a phone for the past 2 days. A huge thanks to anyone that can help me out!
I only use the DL01 or the ED05 stock packages. I think you should try those. I restored my phone when I was running SuperClean w/Voodoo with the DL01 package, no pit file.
Here is a link to ED05
OhioYJ said:
I only use the DL01 or the ED05 stock packages. I think you should try those. I restored my phone when I was running SuperClean w/Voodoo with the DL01 package, no pit file.
Here is a link to ED05
Click to expand...
Click to collapse
I'm scared that I've already messed something up by using the pit file, because I actually had the full dl01 file, and nothing. Not really sure what would be different about the ed05 file. I mean, I'm gonna try it, but does any one else have a suggestion? Thanks.
brettdacosta said:
Please help! I have tried this numerous times, and my phone just keeps booting into stock recovery. It won't let me get past it.
I originally tried the .pit file with dl09 (mistake - I know), and it started the recovery mess. Then I downloaded the "stock" rooted eb01 file (EB01_DXC.tar.md5), and flashed it with the .pit file (atlas v2.2) and re-partition checked.
I have no other clue what's going on. I was just trying to wipe completely fresh to be able to load the CM7 Espresso on my phone. I've been running old CM7's for a while with the glitch kernels.
Help, please - I've been without a phone for the past 2 days. A huge thanks to anyone that can help me out!
Click to expand...
Click to collapse
a pit file is a pit file, they are no different for eclair or froyo from my understanding. I have no problems odin dl09 w/ pit...I actually got that tip from the stickies on the galaxy s forums.
http://www.galaxyforums.net/forum/fascinate-rs-guides/2911-how-upgrade-cyanogenmod7.html
as you can see by reading the link alot, there are alot of different guides out there with different methods and I have tried them all... Thats why I created my own guide with pieces from all the other guides that I felt worked the best. My best advice to you is spend alot of time doing research and form your own opinion on what works best. DO NOT take one posters advice as it being the correct way because there is alot of misinformation on teh internet!!

Vanilla gingerbread Warning!!!

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.

[Q] Everything FCing

Hey, everyone. I've been having this problem a lot... when I was on CM7, about once a month everything would force close. First an app (xScope, Twicca, anything), then GApps, then my keyboard... the phone starts FCing everything within about an hour of being turned on. In the past, I've just fully wiped the phone... I'm on Pool Party now (the version before the newest one right now), and everything is FCing again. Is there a solution that isn't just "wipe everything?"
Did you make any drastic changes before it started force closing everything or has it been that way since you flashed the new ROM? Or was your ROM working fine in the past and it mystically started happening
Sent from my SCH-I500 using XDA App
This just mystically started today. It's been about a month and a half since the last time this happened, on CM7.
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
GApps is GApps, man. Wondering if it's a sync issue...
mvmacd said:
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
Click to expand...
Click to collapse
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
obsidianchao said:
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
Click to expand...
Click to collapse
Yeah I understand you on that...makes you sick to your stomach when you lose everything. Did you not have any backups of when your phone was in its working state? Backups are one of the most important things in my opinion. I learned the hard way
Sent from my SCH-I500 using XDA App
I haven't done a proper backup in a while. I should really start doing that, sigh.
obsidianchao said:
I haven't done a proper backup in a while. I should really start doing that, sigh.
Click to expand...
Click to collapse
boot into cwm and wipe cacnhe and dalvik. I normally do this once a week. Also if you have alot of apps downloaded to the internal memory this can happen. Check rootzwiki out for a thread about fixing the datadata force close issues.
http://rootzwiki.com/topic/5635-problems-with-datadata-causing-force-closes-for-google-apps/
Ahhh, thank you so much, this is perfect!
kadin.zimmerman said:
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ah nice. I was hoping to see a stable ICS. So, it says there's no video hardware acceleration.. does that mean future updates will bring hardware acceleration for the fasciante? like h264 mkv's, or h264 mp4's, or even mpeg4 avi's? tsm/jt's rom doesn't have good video hardware support, MX video has to use SW almost all the time.
So I think I would like to check it out, but I wish I knew about it before I went through all the trouble last night to reflash and reinstall all my apps.. [was up till 3am working on it] lol
any major troubles with it? Also what CWM do I use? Perhaps the one on the CM7 fascinate wiki? [cwm4-bml-i500.tar] or the cwm 5.0.2.7 in vanilla gb?
Also do I need to odin it to anything? or can I go from what I've got now [tsm pool party]?
I've had no major troubles with the past 2 builds and definitely build 6 is the best. Not exactly sure what is meant by the hardware acceleration but everything about this ROM runs smooth. As for cwm version, just install any cwm and the ics ROM has its own that it will install. Once it installs it's own, it is recommended to not flash a new kernel once it does it's own because the one it puts on has stuff built in to make all the features work.
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ok so how come I should install build 5 first?
mvmacd said:
Ok so how come I should install build 5 first?
Click to expand...
Click to collapse
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
awesome... yes I was planning on Odin'ing again, because I've found it gives the rom you flash after it better chance of survival.
It is a inconvenience though because I have to boot up W7 [Dual boot Linux] every time I wanna Odin.. haha, same thing back when I used my ipod touch for iTunes.
So what radio does the ics build 6 have? can they not use the eh03 radio [I'm assuming is superior to whatever it has]? And I assume heimdall can flash the "modem.bin" radio that I untar from the "CI500_VZW_EH03_GB_CM.tar.md5" like so:
heimdall flash --modem modem.bin
right?
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
kadin.zimmerman said:
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
Click to expand...
Click to collapse
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
mvmacd said:
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
Click to expand...
Click to collapse
Use the program "odin" to flash all your .tar.md5 files. You don't extract those files, you leave them in the .tar format. I gave you the link to download specifically the eh03 radio, but if you have it already on your phone you dont need to worry about it. As for the boot animation, the ics rom will install its own boot animation so no worries there.
You know about odin right? It is definitely the easiest way to flash kernels, radios, and stock firmware.

Categories

Resources