[Q] Everything FCing - Fascinate Q&A, Help & Troubleshooting

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.

Related

Latest Trigger - Did you update via Rom Manager?

Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?

[Q] Rooting Samsung Fascinate (2.2.1)

Can anyone loan me a hand? I just got my new Samsung Fascinate today and I really like it. Can anyone here help me root it? It's on
version 2.2.1.
Build Number: SCH-I500.ED04
Kernel V: 22.6.32.9
Model: SCH-I500
Hardware V:I500.04
If you can, please help me out. I'm familiar with jailbreaking iPhones and iPods but have never dealed with an Android.
http://forum.xda-developers.com/showthread.php?t=1046855&highlight=root+ed01
What he said... But if you want other roms, don't bother with unrooting.
Just update your recovery to the latest CWM and flash a new rom using CWM.
But I would make sure to read up before taking any steps further to make sure you know what steps to take.
Sorry, but I don't even know what a rom is. I'm familair with iPhone Jaibteaking and thats it. This is my first Android phone. All I Wanna do is be able to install the themes and tweaks and get free tethering. I'm sorry i don't know much.
Sent from my SCH-I500 using XDA App
I had root on my Fascinate and then I updated OTA to Froyo 2.2.1 and lost root.
How do I root my Fascinate now?
FW=2.2.1
Kernel=2.6.32.9
Build=SCH-I500.ED04
Baseband=S:i500.04V.ED04
Thanks to you and all the help on XDA.
Same that was already posted above.... READ
http://forum.xda-developers.com/showthread.php?t=1046855&highlight=root+ed01
When I tried to download the "update.zip" file I get a 404 error.
Thanks
RacerXFD said:
What he said... But if you want other roms, don't bother with unrooting.
Just update your recovery to the latest CWM and flash a new rom using CWM.
But I would make sure to read up before taking any steps further to make sure you know what steps to take.
Click to expand...
Click to collapse
I would go this route, load up ComRom 2.1 and get rid of the ED04 radio it has some issues. It's not as hard as it sounds to do this. Just read up and enjoy a better running phone.
nunyazz said:
Same that was already posted above.... READ
http://forum.xda-developers.com/showthread.php?t=1046855&highlight=root+ed01
Click to expand...
Click to collapse
I went to the page you suggested and when I tried to download the "update.zip" I get a 404 error.
What is next?
Thanks
sfobrien said:
I would go this route, load up ComRom 2.1 and get rid of the ED04 radio it has some issues. It's not as hard as it sounds to do this. Just read up and enjoy a better running phone.
Click to expand...
Click to collapse
If this is the route you want to take (I highly recommend it as well), I would check out this thread or even this thread (although it is on Android Central, so you will need to make an account to see all the links if you don't already have one). They are pretty similar (the latter is a bit overboard on detail, but that can be a good thing if you are new to the process) and should at least get you started on learning what it is you need to learn to ultimately wind up at ComRom 2.1. I hope this helps!
Hello. I finally found out what a ROM was and how to use ODIN. I had my Uncle to ROOT my Fascinate when he was down this weekend. Last night, my phone got bricked or stuck in blue recovery and I had to flash it. Or restore it using ODIN. Anyhow, can you tell me the steps to get it rooted again with Odin & Evil Fascination? ClackWorkRecovery caused thus because I couldn't get it to work to install Com rom.
Sent from my SCH-I500 using XDA App
For a better understanding, I want to do the following:
Steps to Rooting my SCH-I500 with Evil Fascinate
Getting clockworkmod working correctly
& Installing Com rom.
Sent from my SCH-I500 using XDA App
GagesiPad said:
For a better understanding, I want to do the following:
Steps to Rooting my SCH-I500 with Evil Fascinate
Getting clockworkmod working correctly
& Installing Com rom.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Evil Fascination and Community Rom are two different roms and both will root your phone when flashed... this is how mine's set up for ComRom and it works flawlessly:
1) download odin, samsung mobile phone drivers, debloated/debinged/deodexed EB01 all in one package, CWR3-Voodoo, and ComRom 2.0 package of your choice and the 2.1 patch... place ComRom and its patch onto your sd card
2) use odin to install EB01
3) boot up phone once to let it format itself
4) power off phone and use odin to then install CWR3-Voodoo
5) boot straight into CWR, wipe data/cache/dalvik 3 times each and assuming you don't want to backup/restore data (I usually just use Titanium Backup app from the market) proceed to install .zip of ComRom 2.0
6) select reboot phone and let it boot up, it may take a while the first time
7) congrats, you're rooted and running ComRom 2.0
8) to install the patch simply hold the power button down until the menu pops up, select recovery
9) this will boot you into CWR again, no data/cache wipe necessary simply install .zip ComRom 2.1 patch then reboot phone again
10) congrats now you're rooted, voodoo'd, and running the latest ComRom
hope this helps, that's about as simple and short as I can make it
tapatalked from my KangBanged Fascinate
Ok. Thanks for letting me know that. I had no idea there was a difference. I'm new to this stuff so. Yah. Anyways, I used that guys post to root my phone (the first reply with the link) and it worked for me. Can you give the the download links to all of the stuff up there that you mentioned? Or is there another thread that you go that from with a better understanding? With the links and all? I'm not sure what Voodoo is. I just want the Com Ron up and going. ;-) thanks =D
Sent from my SCH-I500 using XDA App
GagesiPad said:
Ok. Thanks for letting me know that. I had no idea there was a difference. I'm new to this stuff so. Yah. Anyways, I used that guys post to root my phone (the first reply with the link) and it worked for me. Can you give the the download links to all of the stuff up there that you mentioned? Or is there another thread that you go that from with a better understanding? With the links and all? I'm not sure what Voodoo is. I just want the Com Ron up and going. ;-) thanks =D
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
this should give you a current recovery (CWM), I use the first one:
http://forum.xda-developers.com/showthread.php?t=1046905
most everything else can be found in landsharks thread here: odin, the samsung drivers, debloated/deodexed EB01 and ED01, and how to install all of that (props to landshark68 for putting it all together)
http://forum.xda-developers.com/showthread.php?t=1048380
ComRom can be found here along with instructions on how to flash, changelogs to see whats been updated, known bugs... I would suggest reading the first few posts by nitsuj17 just to get familiar with it:
http://forum.xda-developers.com/showthread.php?t=1108991
superchunkwii put up a pretty nice detailed thread on how to get to ComRom if you're at stock (or need to go to stock, then go to ComRom):
http://forum.xda-developers.com/showthread.php?t=1053567
last but not least voodoo, these are the closest threads I could find that describe it (second one is a little better):
http://forum.xda-developers.com/showthread.php?t=1043673&highlight=voodoo
http://forum.xda-developers.com/showthread.php?t=1039897&highlight=voodoo
i know it might seem like information overload and a lot of reading, thats why i tried to simplify it in my instructions in my previous posts... if you download what you need from those threads then follow the steps I listed you shouldn't have any problems. If you do, don't worry we're here to help
Ok. From my understanding, CWR3-Voodoo is like the one click lag fix right? I'm actually using that on my phone now. When I'm on my computer later, ill go through all that and learn more about it and download everything and try it. =]
Sent from my SCH-I500 using XDA App
GagesiPad said:
Ok. From my understanding, CWR3-Voodoo is like the one click lag fix right? I'm actually using that on my phone now. When I'm on my computer later, ill go through all that and learn more about it and download everything and try it. =]
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yes it has an option for enabling/disabling lagfix but its optional.. even if you decide to flash a rom with no voodoo kernel you can still use that CWM with no worries
tapatalked from my GINGERBANGED Fascinate
Thanks. Since I'm allready rooted, can I skip to steps 20-24 and do that?
GagesiPad said:
Thanks. Since I'm allready rooted, can I skip to steps 20-24 and do that?
Click to expand...
Click to collapse
yeah if you're rooted and running the baseband you want (ED01 or whatever) the boot into CWR and flash the rom you want... you're going to need to do a data/cache/dalvik wipe before flashing the initial ComRom 2.0 package so make any backups you want.. once its done installing reboot phone to make sure everything works right, then boot back into recovery and flash the patch (no wiping or anything needed) any questions or problems be sure to post them
tapatalked from my GINGERBANGED Fascinate
Thanks! I back up my stuff though Titanium back up. One thing though, how do I tell if I have CWR installed? Thanks for your help!

[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.

Downgrade to froyo

Hi, I'm currently on simply honey3.91 gingerbread...I flashed this rom specifically just to be able to use netflix but now it appears that the newest version works on froyo now.. how do I downgrade back to froyo? Froyo had working gps for me which I could never get to work consistently on gb...to have GPS and netflix working on my phone would be great!
Sent from my GT-I9000 using XDA App
Odin back to eclair, root, install rom manager, format sd-card (remove the external sd-card to avoid loosing important data) and flash froyo.
naars90 said:
Hi, I'm currently on simply honey3.91 gingerbread...I flashed this rom specifically just to be able to use netflix but now it appears that the newest version works on froyo now.. how do I downgrade back to froyo? Froyo had working gps for me which I could never get to work consistently on gb...to have GPS and netflix working on my phone would be great!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No need to format SD card
Sent from my GT-I9000 using XDA App
I have gingerbread bootloaders...would that be a problem?
It's not going to be a problem. You may only be annoying by the I1900 when you boot your phone. Regarding formatting your sd-card, to cleanup the left over software components like voodoo folder and data. Re-installing the os on your phone is juts like re-installing os on your pc. Cleanup the left over junk may help saving space and other unforeseen complicated issues.
naars90 said:
I have gingerbread bootloaders...would that be a problem?
Click to expand...
Click to collapse
VibrantThemer said:
It's not going to be a problem. You may only be annoying by the I1900 when you boot your phone. Regarding formatting your sd-card, to cleanup the left over software components like voodoo folder and data. Re-installing the os on your phone is juts like re-installing os on your pc. Cleanup the left over junk may help saving space and other unforeseen complicated issues.
Click to expand...
Click to collapse
on the flipside if you want to be extra careful just flash froyo bootloaders of course dont be sacred if at reboot you get rainbows thats normal after that reboot phone into download mode then odin back to stock reroot flash clockwork and flash a froyo rom
godsfirsthomie said:
on the flipside if you want to be extra careful just flash froyo bootloaders of course dont be sacred if at reboot you get rainbows thats normal after that reboot phone into download mode then odin back to stock reroot flash clockwork and flash a froyo rom
Click to expand...
Click to collapse
Have you tried that? Don't want to take a chance and I hate the rainbow lolz.
Thanks anyway
VibrantThemer said:
Have you tried that? Don't want to take a chance and I hate the rainbow lolz.
Thanks anyway
Click to expand...
Click to collapse
the rainbows are there only while your still on simply honey as soon as you odin back to stock they will be gone and you have your normal galaxy s start up logos
VibrantThemer said:
Have you tried that? Don't want to take a chance and I hate the rainbow lolz.
Thanks anyway
Click to expand...
Click to collapse
I have flashed bootloaders both ways. Nothing to worry about as long as you follow the steps. Works like a charm.
offdutyninja808 said:
I have flashed bootloaders both ways. Nothing to worry about as long as you follow the steps. Works like a charm.
Click to expand...
Click to collapse
I'm thinking of doing this as I cannot seem to get a full workday with relatively light use out of GB right now.
Anyway... where can I find the bootloaders for Froyo and is there a guide to make sure I do this in the right order. I haven't had any issues with all the various flashes and odins that I have done so far, but with CM7 on board I know that it's quite a bit different now.
I tried using the XDA search for bootloaders and basically got this an other similar threads.
I read this thread http://forum.xda-developers.com/showthread.php?t=1117990 which looks like I already had stock bootloader, but I wasn't sure if that is correct.
Yeah, that's the right place. Just click on the "Froyo Bootloader Revert to Vibrant" link to download the original bootloaders. It should be a .tar file. Flash through Odin with the same steps, but just use the Froyo BL .tar instead of the GB one and BOOM!
In like tube socks!
Oh yeah... don't forget that the button combo for the GB bootloaders is different. It's just volume up + power.

Phone keeps getting stuck at HTC screen.

I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?

Categories

Resources