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.
Related
HI i went to put evil eris 4.0 on my phone and it loaded up just fine except my data wasnt working but thats because i had my phone flashed to metro pcs with the data. Anyways i got the celb froyo zip off xda {latest version} and the gapps and tryed to load the zip but first i did a wipe and tryed to load it but it wont load. It just stay on the boot screen with android on the skateboard .Now when in hboot ,my phone says wrong img and when i try to load another rom in recovery it says no space left on device and it wont load any rom did i screw my self. I have adb setup is there any method for me to start fresh and reroot with a custom rom? thanks alot in advance i think i did somehting else to it but i dont remember
Since your using metro pcs I have no idea how to help or what to suggest, but if you can see the splash screen and bootloader then your not bricked.
Sent from my nonsensikal froyo using XDA App
It doesn't matter if I revert back to Verizon and that wouldn't matter anyways since the hex esn number is in metros database but I don't care if I revert back to stock or whatever I just want my phone back no hold bar at this point
Sent from my CM6 Aria froyo using XDA App
Not sure if it will help but did see couple threads about Metro here, I would check those. May give you some ideas on how to fix.
Just do a search on metropcs should get at least one hit, not sure if the other had just metro or metropcs
I don't care about metro I just wanna revert back to stock do you think if I can get the stock 2.1 rom and try to flash it would work?
Sent from my Liberty using XDA App
Did you do a full wipe after flashing the Froyo rom and before attempting to flash another rom? Sometimes you need to wipe more than once for the new rom to load properly.
Sent from my Froyo Eris using XDA App
Yes I did a wipe initialy when I loaded evil eris v4.0 and that booted up fine and then I decided I wanted a 2.2 rom so I got the celb rom for the Eris and the gapps and then I rebooted into recovery and did a wipe and uploaded the celb rom and it wouldn't load after. 30mins I said screw it and poped out the battery and booted into recovery and tryed to wipe and reload but it kept saying staus 7 and no space left on device so I don't know what else to do..
Sent from my CM6 Aria froyo using XDA App
eris_evil said:
Yes I did a wipe initialy when I loaded evil eris v4.0 and that booted up fine and then I decided I wanted a 2.2 rom so I got the celb rom for the Eris and the gapps and then I rebooted into recovery and did a wipe and uploaded the celb rom and it wouldn't load after. 30mins I said screw it and poped out the battery and booted into recovery and tryed to wipe and reload but it kept saying staus 7 and no space left on device so I don't know what else to do..
Sent from my CM6 Aria froyo using XDA App
Click to expand...
Click to collapse
Did you do a nandroid backup before you tried the 2.2 rom? If so, boot back to recovery, nand backup/restore and restore your backup.
Also, some roms need you to flash the rom, then the gapps, then boot. If you miss one and boot early, you'll get looped!
Sent from my Cyanogen Froyo using XDA App
Since you still have recovery, you're not bricked. It's just a matter of getting a rom to boot. Was your sd card partitioned for apps2sd while on the 2.1 rom? Also, did you try wiping your rotation sensors and battery stats? If you don't have a nandroid (mentioned above), wipe, wipe, wipe and flash a new 2.1 rom.
Sent from my Froyo Eris using XDA App
How does wiping battle stats a nd rotation sensors help?
I've been pulling my hair out trying to loads new rom and get stuck at the white screen. I've flashed many roms before. But lately get stuck at the boot stage.
joshw0000 said:
Since you still have recovery, you're not bricked. It's just a matter of getting a rom to boot. Was your sd card partitioned for apps2sd while on the 2.1 rom? Also, did you try wiping your rotation sensors and battery stats? If you don't have a nandroid (mentioned above), wipe, wipe, wipe and flash a new 2.1 rom.
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Sent from my Cyanogen Froyo using Tapatalk
Jp50 said:
How does wiping battle stats a nd rotation sensors help?
I've been pulling my hair out trying to loads new rom and get stuck at the white screen. I've flashed many roms before. But lately get stuck at the boot stage.
Sent from my Cyanogen Froyo using Tapatalk
Click to expand...
Click to collapse
Wiping those stats has no real use when changing roms if you're not already having problems. However, I've read other threads where people have been stuck in boot loops or not booting at all and that has helped them. Worse case scenario, if you wipe them and it doesn't fix your problem, it hasn't started any either. How many people actually use battery stats or change sensor settings?
Just trying to help.
Sent from my Froyo Eris using XDA App
eris_evil,
Do you know how to use the adb command line, and you have your PC set up (USB drivers and all) so that it is working?
If so, charge your phone fully (100%), and then:
- plug it in (USB) to the PC
- boot the phone into Amon_RA
- from the command line on the PC, run the following commands:
Code:
adb shell mount /system
adb shell umount /system
adb shell mount /data
adb shell umount /data
adb shell mount /cache
adb shell umount /cache
And then report back if you see these commands reporting errors. Do NOT paraphrase - cut and paste the exact text you see into a reply here. I am guessing you will see an error with either /system or /data.
bftb0
I dont have amon_ra I have I use clockwork mod recovery
Sent from my Liberty using XDA App
I'm going to try wipe and install another rom but if I wipe everything and install another rom will the boot image be installed with it cause when I'm in hboot it says that its the wrong boot imagine and zip. so maybe I got the wrong rom the second time around after the first rom i uploaded is the celb 2.2 froyo an eris rom?
Sent from my CM6 Aria froyo
eris_evil said:
I dont have amon_ra I have I use clockwork mod recovery
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
I have no experience with Clockwork. Sorry.
does anyone have the stock 2.1 update.zip laying around on there computer i may just try than and see if it loads
eris_evil said:
does anyone have the stock 2.1 update.zip laying around on there computer i may just try than and see if it loads
Click to expand...
Click to collapse
None of the HTC/VZW OTAs will work unless you have the stock recovery installed. Also, they will bomb out immediately if you have the wrong OS on the phone. Not a chance in h3ll that they will work on a (dev) ROM - the first thing they do is call getprop() to check the currently installed software version.
Nevertheless, the original download links (Google) for all of the Eris OTAs are listed in this XDA post
You can attempt flashing the Leak-V3 PB00IMG.ZIP ROM to your phone using the HBOOT + PB00IMG.ZIP method. Given the state that your phone is in, I'd guess there is about a 50/50 chance you will end up with a brick.
There are other approaches that are much more cautious - but are not guaranteed to work, and would require me to write a novel to describe them.
Basically, you attempt to do everything possible inside the recovery boot before you touch either "system" or "data" further - but you start by getting the 1.49.2000 S-OFF bootloader onto the phone. That requires jcase's "misc" image flashing, plus a HBOOT+(Root ROM)PB00IMG.ZIP install with a Toastcfh "battery pull trick".
That would give you the option to use fastboot mode to flash either Amon_RA or Clockwork to the recovery partition - that can only be done with the S-OFF bootloader
bftb0
You can only load Pb00img.zip from hboot. That's the only one that will work in hboot.
Put that file in your root folder on your sd card and shut your eris off. Hold the volume down button and turn your power on and you should be alright
Sent from my FroyoEris using XDA App
Thank you all very much I will take all of your advice and apply it to my knowledge I will let you know tomorrow if my phone gets fixed
Sent from my CM6 Aria froyo
Ok I thought the worst was over but now my phone is bricked for real it won't turn on or charge, how do you recover a bricked phone. If not do you think that since I bought my eris second hand will htc sill honor the manufacturers warranty if I send it to them plus I already called them and they said the warranty is still good because I haven't tryed to take the phone apart. I never told them I rooted my phone or tryed to put a custom rom on it but nor did they ask either. All I told them was one day I went to use it and it would not work. The only thing is if the phone won't turn on at all will they be able to tell I was messing with it. And if there is an other option to fix it without having to mail it out for three weeks.
Sent from my CM6 Aria froyo
okay, so i tried to install CM7 test build 8 onto my phone. the install got up till checking BML/MTD and then failed. i was already on test build 7.
anyhows, clockwork said the rom failed to install and then rebooted. now the phone is stuck in a loop of booting into clockwork and then aborting an install.
i would normally have just started up ODIN and flashed down to stock DJ05 or EB01 and then do the lovely root process; but alas i sent my PC into HP today for repair and stuck using a Macbook for a week or two. (no one else in my family uses PC anymore; iPad and Mac family now...sigh)
does anyone know of a way to fix this? i'd like to avoid going back to my old droid 1 (so laggy).
Dude.. this goes in either the thread for that rom or the Q&A section. You might get quicker responses when posting correctly.
Good luck.
Sry, thanks for the help though
reloaded89 said:
okay, so i tried to install CM7 test build 8 onto my phone. the install got up till checking BML/MTD and then failed. i was already on test build 7.
anyhows, clockwork said the rom failed to install and then rebooted. now the phone is stuck in a loop of booting into clockwork and then aborting an install.
i would normally have just started up ODIN and flashed down to stock DJ05 or EB01 and then do the lovely root process; but alas i sent my PC into HP today for repair and stuck using a Macbook for a week or two. (no one else in my family uses PC anymore; iPad and Mac family now...sigh)
does anyone know of a way to fix this? i'd like to avoid going back to my old droid 1 (so laggy).
Click to expand...
Click to collapse
i had a bootloop too with cm7 yesterday. Don't quote me on this but i think heimdall works on a mac, just like odin. here is a link that might help with heimdall
http://forum.xda-developers.com/showthread.php?t=957981
And yes wrong section to post, good luck
Im having the problem when I try to install it
Sent from my SCH-I500 using XDA App
I know it sounds odd but pull the battery and then do the three finger salute. I know we aren't supposed to but trying to wipe through there and then install has helped a couple of us with this problem on miui. I did it and when it finally installed right I rebooted into recovery the proper way and wiped. Worked like a charm.
Hope this helps, brother.
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/OTB @1.2ghz -100mv/NeonGT & Infinite Themes
I Agree with Tim. Three finger method and reflash CM7 Build number 7 (after wiping of course) Then try build 8 again. You will lose settings and data. Hopefully you backed up beforehand but if you're stuck in a bootloop it's a moot point. Hope this helps.
Sent from my SCH-I500 using XDA Premium App
thedoman said:
I Agree with Tim. Three finger method and reflash CM7 Build number 7 (after wiping of course) Then try build 8 again. You will lose settings and data. Hopefully you backed up beforehand but if you're stuck in a bootloop it's a moot point. Hope this helps.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
have done this twice. after install number 7 restart and reboot recovery and you will see your back to the orange cwm and good to go with number 8 install. wipe delvik
Quickest way back is to use the EB01 install package that is linked in the stickied thread about returning to to a TW ROM after running. Apparently the two ROMs Linked (Eclair and Froyo) have the right bootloader to work with the PIT file. Anyway that's what it says in the thread.
Flash EB01 (with atlas PIT). Flash a 3.x CWM and then try the CM7 procedure. No need for OTA updates or voodoo and/or lag fix, root, etc. Just plain ol stock EB01. This worked for me last night. I have not used the phone a lot since then but so far its been working OK.
He can't do that without odin brother..
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/OTB @1.2ghz -100mv/NeonGT & Infinite Themes
yeah...odin is out of the question for (hopefully) another two weeks. and i can't get heindall to work on my mac; keeps telling me that it isn't compatible with my laptop. *%&$ing MAC! STEVE JOBS, GO SUCK ON A BIG ONE
Lol tell us how you really feel.
Any friends that use pc? Work computer? Give what I suggested earlier a shot and let us know. If all goes well you could be fine in about 8 minutes lol
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/OTB @1.2ghz -100mv/NeonGT & Infinite Themes
try using virtualbox and install xp. it'd be your best bet. not sure if you'll run into driver issues, should work fine. if you need an XP install let me know, i have an iso on my server that needs 0 activation and should get you by.
you can try a linux live cd and then heimdall
To preface this, I have followed all instructions to a T in all threads related to this, so here goes.
I was running CM7 test 7 and all was well, then I updated to build 8 and still ok but no call audio so I flashed the .13 OTB kernel and the phone began to bootloop. I have since been unable to reinstall CM7 and have ODIN flashed the EB01 official and the Atlas .pit probably 10-12 times through the whole cycle to try and reinstall.
Now that I have given up on that I followed the steps to return to UKB 2.1 and after flashing everything booted fine but my touchscreen would not work...so, back to stock again and I have stayed there........but
Now every time I reboot I have to reinstall all my apps(they are still installed but force clse immediately), none of them save any settings or data when I exit and return to them and my launcher is throwing out "Unknown data error" in notifications every time I boot. It also resets all homescreen and system settings to default at each reboot and has to resync all contacts also.
I am hoping that someone can help we with this and that I have not flashed this thing to its breaking point and am totally screwed. Someone have mercy and know something...and yes, I have searched and have found a few threads on the subject but none with any answers.
thanks I hope
If you have most of your contents from your sd backed up on your pc and you have a spare sd card I would try putting your spare one in, put com rom on it and TiBu on it as well
Odin recovery, wipe data/cache/dalvik.. voltage settings too if your recovery has that option
flash ukb 2.0 reboot completely and do the 2.1 patch
I'm not a dev, nor do I know if this will fix anything but I went to cm7 a while back before deep sleep was fixed and when I went back to com rom to hold me over I noticed even after doing the atlas 2.2 and eb01..i still had a bunch of cm7 files on my sd card and it (ukb) was rather glitchey compared to before I tried cm7...i don't think that these can conflict with anything on the rom but if you have a spare sd what's it gonna hurt you said you've flashed/ repartitioned multiple times..what's once more!
If you can't get it fixed I would just go to the newest cm7 its just about perfect, the bugs in it are minor..imo...good luck!
Sent from my SCH-I500 using XDA App
I've got everything up and running with stock once more and everything seems to be good finally.
Honestly after all this I'm a bit hesitant to flash CM7 lol. I may a suit on it for a couple days and decide. Thanks
Sent from my SCH-I500 using XDA Premium App
In the future, I would try the ext4 format utility from navenedrob right after you've returned to stock & before you flash any custom rom. It formats all partitions & may fix something overlooked by odin.
Sent from my SCH-I500 using XDA App
okay guys so i made this thread since it was getting too confusing and hard to track CLEAR INSTRUCTION on how to root from Rooted rom to cm7 or omfg roms!!
Basically this is what i did and STILL have iSSUE:
1.ODIN and atlas v.2.2pit (DL09 stock rom)
2. updated all OTA
3. pulled out battery and ODINed blue CM7 (latest one from jt's site)
4. did 3 method cmr and clear all data/wipe/davik
5. installed latest cm7 7/17
6. waited and seem like everything is perfect then it stops at cm7 logo with galaxy s sign and kept waiting and nothing HAPPENS anyone help???!!!
this is really pissing me off because I've been trying this several times now!!
ALSO for omfg i dont even know the instruction to get there anyone help it would be great!!!
Did you remember to flash gapps?
Sent from my SCH-I500 using XDA Premium App
izzjkjoe said:
okay guys so i made this thread since it was getting too confusing and hard to track CLEAR INSTRUCTION on how to root from Rooted rom to cm7 or omfg roms!!
Basically this is what i did and STILL have iSSUE:
1.ODIN and atlas v.2.2pit (DL09 stock rom)
2. updated all OTA
3. pulled out battery and ODINed blue CM7 (latest one from jt's site)
4. did 3 method cmr and clear all data/wipe/davik
5. installed latest cm7 7/17
6. waited and seem like everything is perfect then it stops at cm7 logo with galaxy s sign and kept waiting and nothing HAPPENS anyone help???!!!
this is really pissing me off because I've been trying this several times now!!
ALSO for omfg i dont even know the instruction to get there anyone help it would be great!!!
Click to expand...
Click to collapse
- In step 1 use vzw eb01 instead of dl09
- No need for step 2 just flash eb01 and reboot fully
-In step 3 pull batt and odin cwr 3-30 fix all (instead of jts blue one) and immediately do step 4...
-do step 4 the same as you did..wipe data/cache/delvik
-install cm7 build date 7/4 and reboot
That will get you running on cm7...from there you can install mtd kernel of choice (if you want something different then the one thats comes with, it) gapps, and/or the newest cm7 build..do not wipe here to go to the newest build but make sure you only use the recovery that came with cm7 by accessing it via the power button menu, or terminal emulator...reboot recovery...no three finger booting recovery from here out.the cm7 recovery will also be blue..you only odin the 3_30 fix all to get the cm7 build on your phone do after that first time seeing red recovery after you're on cm7 it will be blue from there on.
-odin desired radio.
Sent from my SCH-I500 using XDA App
well apparently, there seems to be no links to the earlier versions of cm7 and the only thing is the latest cm7 with blue recovery from jt's site can..... i really want to try CM7 geez im missing out...
You can just install the latest CM7 following the same steps the previous poster gave you. No need to install 7/4. Install 7/17 then 7/18 update.
wjsmaggle said:
You can just install the latest CM7 following the same steps the previous poster gave you. No need to install 7/4. Install 7/17 then 7/18 update.
Click to expand...
Click to collapse
Thanks for the info but that is the issue i'm having I'm currently in stock froyo then i ODINED cmr 4 (blue from jt site) then i installed the latest 7/17 and everything seems to be working then i'm left hanging on cm7/galaxy s logo forEVER!! and nothign happens...
AND i did wipe date/davik/cache... please anyone???
izzjkjoe said:
Thanks for the info but that is the issue i'm having I'm currently in stock froyo then i ODINED cmr 4 (blue from jt site) then i installed the latest 7/17 and everything seems to be working then i'm left hanging on cm7/galaxy s logo forEVER!! and nothign happens...
AND i did wipe date/davik/cache... please anyone???
Click to expand...
Click to collapse
My previous post says to try to flash it with cwr 3-30 fix all did you odin that recovery and try to flash cm7 from there?
Sent from my SCH-I500 using XDA App
well there was no link on jt's site for cmr 3 or cm7 7/4 your talking about
izzjkjoe said:
well there was no link on jt's site for cmr 3 or cm7 7/4 your talking about
Click to expand...
Click to collapse
The Latest build should still work just try flashing it with the 3-30 recovery
here is a link
http://forum.xda-developers.com/showthread.php?t=942021
Scroll down to the .tar file and download it..odin it and three finger boot into recovery wipe everything and flash the newest cm7 build and reboot...once on cm7 don't three finger boot anymore.
Sent from my SCH-I500 using XDA App
When you odin, did you tick the re-partition box? Also you need to use one of the tar balls in the sticky about moving from cm7 to another rom. I know you're not going from cm7 but the tar balls still apply to this situation.
Sent from my SCH-I500 using XDA Premium App
I also had problems installing cm7 at first so what I did was installed latest miui.us build first which gave me blue cwm and converted all my files. Then flashed cm7 with no probs. This worked for me.
Sent from my I500 using XDA App
well tell me the instructions not just say "install miui" obviously i dont know how to do give me the steps!
Sorry, I had stock 2.2 eb01 (edo3/4 should work) to start. Then I used odin and flashed cwm-all (2.x.x or something) / three button boot to get to recovery/ wipe data/cache/flash super user zip/reboot/power off and back to odin/flash cwm-all again/three button boot/wipe data/cache/dalvik/flash latest miui . At this point it should reboot (cyanogen logo) then back to recovery and automatically install/reboot recovery/flash cm7 11.1. But like I said this worked for me, for some reason miui installed perfect like any other rom and not cm7. Sorry if this doesn't help.
Sent from my SCH-I500 using XDA App
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.