Related
I installed "Eugene_2E_JK2_Froyo.tar.md5" on two of our Vibrants using odin. I have four strange anamolies that happened to both Vibrants as a result of this...
1) There is NO lock screen anymore.
2) The touch "home" and "search" keys are non-responsive.
3) Videos cannot be played.
4) The most disturbing is we cannot receive calls...but we can make them.
I currently have 2.2 froyo.uvjk2 installed on both vibrants.
As a result of these weird accurances, I tried installing several roms...such as Axura 204 and Onyx R42 Stock. I keep getting a signature error when the Vibrant boots in recovery mode. Do roms not work on 2.2?
I am using the current "One Click Lag Fix" and "Rom Manager".
What should I do to fix these Vibrants and why are the roms not working?
Any help would be greatly appreciated.
ams77 said:
I installed "Eugene_2E_JK2_Froyo.tar.md5" on two of our Vibrants using odin. I have four strange anamolies that happened to both Vibrants as a result of this...
1) There is NO lock screen anymore.
2) The touch "home" and "search" keys are non-responsive.
3) Videos cannot be played.
4) The most disturbing is we cannot receive calls...but we can make them.
I currently have 2.2 froyo.uvjk2 installed on both vibrants.
As a result of these weird accurances, I tried installing several roms...such as Axura 204 and Onyx R42 Stock. I keep getting a signature error when the Vibrant boots in recovery mode. Do roms not work on 2.2?
I am using the current "One Click Lag Fix" and "Rom Manager".
What should I do to fix these Vibrants and why are the roms not working?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
make sure and disable the lag fix, and try the reboot to recovery option in rom manager. (so that your in clockwork recovery and not samsungs)
then try flashing the new rom from there.
also you probably know this, but just to be sure: make sure your flashing rom zips and not odin style roms.
otherwise odin should work especially if you've done it before, but be sure to flash a 2.1 kernel if your going to a 2.1 rom
theres some guides for that, if you decide to go that direction I can give you a link.
firefly6240 said:
make sure and disable the lag fix, and try the reboot to recovery option in rom manager. (so that your in clockwork recovery and not samsungs)
then try flashing the new rom from there.
also you probably know this, but just to be sure: make sure your flashing rom zips and not odin style roms.
otherwise odin should work especially if you've done it before, but be sure to flash a 2.1 kernel if your going to a 2.1 rom
theres some guides for that, if you decide to go that direction I can give you a link.
Click to expand...
Click to collapse
Can you tell me what this means...how do I disable the lag fix? I am extremely new to android (one week), so can you tell me more about how to flash a kernel and what that means? Is Axura 204 and Onyx R42 Stock 2.1 roms? Do I have to downgrade back to 2.1 in order to run those roms? If so, I'll take you up on that offer for the link for directions.
Thanks for all the help...
ams77 said:
Can you tell me what this means...how do I disable the lag fix? I am extremely new to android (one week), so can you tell me more about how to flash a kernel and what that means? Is Axura 204 and Onyx R42 Stock 2.1 roms? Do I have to downgrade back to 2.1 in order to run those roms? If so, I'll take you up on that offer for the link for directions.
Thanks for all the help...
Click to expand...
Click to collapse
try looking here: http://forum.xda-developers.com/showthread.php?t=849028
that should have most of your questions answered, anything you need more specifics on just pm me again and I'll explain further.
wow. dude. this is weird.
this same problem happened on my gf's nexus one out of the blue last month. there was no way to fix it (searched the entire internets!) other than doing a factory reset.
so i did that and it worked for 2 weeks. then bam, same ****ing problem again.
reset again, it did it again that same week.
called HTC and got a new SLCD nexus one mailed out to us free of charge.
EXACT same problems though, those two buttons haptic feedback but do nothing, no lock screen, and phone calls go straight to voicemail.
Samsung wants me to send them my Vibrant to "reflash" it. Can I do it myself?
Hey all. I've been having a couple of problems with my Vibrant -
1. About once a day, when trying to play an MP3, the phone says that the audio files can't be played because they don't exist. Reseting the phone allows the audio files to be played again.
2. The wifi radio frequently will not turn on properly. When trying to turn it on in the wifi settings menu, the wifi will say "turning on...", and about 30 seconds later it will say "error". After a few tries, it will eventually work.
I called Samsung, and they want me to send it to them to "reflash" it. I'm wondering if this is something I can do myself. I've been reading about all of the flashing of roms you guys do here, but I've never done it. Would using Odin or whatever to reflash to stock be the same thing Samsung is going to do?
Thanks for bearing with a n00b!
Yes to all your questions.
You can do it yourself. It will be the EXACT same procedure Samsung will do (except here you have the option of using ROMs that are MUCH cooler).
}{Alienz}{ said:
Yes to all your questions.
You can do it yourself. It will be the EXACT same procedure Samsung will do (except here you have the option of using ROMs that are MUCH cooler).
Click to expand...
Click to collapse
Awesome! Thank you! Two quick questions-
1. What's the risk level to this? Would I be running the risk of creating a shiny paper weight if I start flashing?
2. What's your favorite ROM? Any recommendations?
Thanks again!
If you can read and follow simple directions then, it is a no-brainer. 1st read the noob bible it has all the instructions to flash anything you want. Go to Unlockr.com or Youtube type in: --Odin back to stock --- rooting a vibrant--- flashing a custom rom.
Simply put Odin is a program that allows you to restore the original 2.1 JFD rom (stock) from there you would Root the phone> then download Rom manager>download Titanium backup> then backup your phone using it> then download a custom rom and put on you internal sd card > then using Rom manager you would flash it
and you have flashed a custom rom. All this takes les than an hour (more like 30-40 min)
Hope that helps you understand more......cheers
I'm not sure if I should put this in another thread, but as I was following the steps, I hit a wall - Titanium backup is force closing when I'm trying to open it. It will show a message saying that it got root access, then immediately crash. Any troubleshooting hints?
Thanks!
lewishollow said:
I'm not sure if I should put this in another thread, but as I was following the steps, I hit a wall - Titanium backup is force closing when I'm trying to open it. It will show a message saying that it got root access, then immediately crash. Any troubleshooting hints?
Thanks!
Click to expand...
Click to collapse
NM - it's the new 3.7.6 version they released - it has known FC issues. I got the apk for 3.7.5 and it works like a dream. Thanks!
Just a thought could it be that you do not have busybox installed? Or perhaps the most recent busy box.
Thanks to your help and encouragement, I took the plunge and flashed a custom ROM! It may not sound like much to you guys, but it was big for me!
I chose trigger for my first try, and it's incredible so far! It's SO much better than what Samsung is putting out!
Thanks for you help everyone!
Trust us, the fun is just starting for you!! Once you flash, you can't stop!
Battery Life
lewishollow said:
Thanks to your help and encouragement, I took the plunge and flashed a custom ROM! It may not sound like much to you guys, but it was big for me!
I chose trigger for my first try, and it's incredible so far! It's SO much better than what Samsung is putting out!
Thanks for you help everyone!
Click to expand...
Click to collapse
And I think you chose the right ROM! Trigger is the shizznessttt!!! If you don't mind me suggesting though, make sure you charge your phone at 100% before flashing anything. It actually made a difference in my battery life, no bs. I guess there is a difference why the devs write and suggest you are fully charged and not just so it dont die midway through flashing procedures lol. Good luck fam.
lewishollow said:
Awesome! Thank you! Two quick questions-
1. What's the risk level to this? Would I be running the risk of creating a shiny paper weight if I start flashing?
2. What's your favorite ROM? Any recommendations?
Thanks again!
Click to expand...
Click to collapse
there is allways the chance you could brick your phone. I suggest reading the noob handbook at the top of the vibrant Q&A page, take your time and follow all directions and you should not have any problems.
I have a major question. As of a week ago my phone suddenly began taking 20-30 minutes to boot. I'm not quite sure what caused it but one morning my phone booted to a black screen that only showed my toolbar at the top. After it randomly vibrating over a course of 20-30 minutes it finnaly showed my screen lock and wallpaper. Now it does this every time I boot!
I need to know if there is a way to fix it, for it's not only a nuisance but a safety issue. What if my phone were off and I needed to make an emergency call?
Phone Facts:
*Samsung Vibrant
*Firmware 2.2
*Not rooted, but at one time was
*Clockworkmod installed
The default answer is to use ODIN to get back to JFD... if you have issues THEN, well, let us know.
I have a guide in my signature with the files needed as well, going back to stock.
First, is this a known issue that can be solved with ODIN? Also, if I were to ODIN do I need to delete information on the phone or do I just get the stock files, download ODIN, and flash my phone?
This is not a known issue... which you know, because you searched before posting.
You should move any sensitive/important info to your pc and backup... you should not lose that data, but if you do, now you can't blame me.
Just use odin and the files from the guide.
So the data on my phone currently shouldn't interfere with the flash. Because I remeber hearing somewhere that old data from the android market and GPS can mess with the phone after it is flashed causing the GPS and market possibly to not work properly afterward. Is this correct?
Huh? Just ODIN the dang thing back to JFD already! When you do that, all data is erased except what is on your EXTERNAL SD (although this COULD get wiped, but is SHOULDN'T). Back up data on both your internal and external SD's to your computer that you don't want to lose, then follow s15274n's signature links to his tutorial on how to ODIN back to JFD and FOLLOW IT precisely and you will be fine.
EDIT: And when that works, and you're all back to normal again, don't forget to swing back here and THANK every post you can find by s15274n by clicking the thanks button.
I'll be sure to do that, THANK YOU both of you! Especially you s15274n for your wonderful tutorial. It worked like a charm, now all I have left is to replenish my apps and update my phone to 2.2. THANK YOU!!!!!!! No GPS issues, NO Android Market issues, NO issues at all! T-H-A-N-K Y-O-U!
^ Might I encourage you, BEFORE going to stock 2.2...
Maybe root with the update.zip in the guide and flash a 2.2 based ROM (THAT IS STABLE). Your phone will be better than stock 2.2 and you will have a lot more options.
Your call. Just know your phone would be better on Trigger, Zen or Project V than stock.
EDIT, of course I have a guide on that too
EDIT2, saw your post in the guide... also replied there.
Thanks but I think I'll stick with stock 2.2. However, I'm thinking of installing SetCPU but of course () I have a question before I attempt it. If I were to uninstall setCPU will the speed of my phone go back to original stock settings or will it stay with the custom settings I had set?
It would stay with the stock settings.
Sent from my SGH-T959 using XDA App
If you are rooting and flashing a kernel to overclock, why are you not using a rom?
Voodoo is better than overclocking/poorer battery in my opinion.
Agreed ^
Sent from my SGH-T959 using XDA App
odin to JFD and thy some other ROM
I have this SAME problem.. 20-30 mins to reboot.. and randomly vibrates while booting up. I just opened a thread about how I can unroot 2.2... you know, please help! I didn't do this until I rooted my 2.2 vibrant. Now i have no idea how to unroot.
Did you read the thread? Odin to jfd.
To answer your boot question LaxHoss it is most likely caused by a glitch in the samsung in vibrant. I came upon a list of glitches on the device a few days ago and discovered this issue. If you are using either the "password" or "pin" password locks on your phone and your phone takes a long time to boot then the screen lock is the cause of the boot issue... To correct simply go to:
Settings > Location and security > Set screen lock > (Then choose "pattern" or "none").
This is how I solved the boot issue for me.
However, for your root issue I would suggest to odin to stock and next time you root use "Z4root" or "Superoneclickroot". Just follow s15274n's guide to odin back to stock, it's real easy.
If going back to JFD, strongly encourage using the update.zip in the guide to root... your pc will think superoneclick is a virus. rageagainstthecage has exploits your pc will hate.
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
powerstroke said:
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
Click to expand...
Click to collapse
Well the first thing you should do is read, read, and read again on the CM7 test build thread along with the waiting room in the general thread. For every handful of success stories there are even more horrible failures.
Another question you should ask yourself is why are you considering switching? Because you know, understand, and like CM7 features? Or because you have seen endless posts on here about how it is now working?
Believe me I love CM7. I ran it for my daily driver for a few months back when 60% of it didn't function. Now that it is in TEST build 10 (still not full release like Ultimate Kang bang 2.1 that you are running) people are flashing it like it is a full RC. They are also having terribly problems and soft bricked phones more than an Touchwiz based ROM at the moment.
If you really like CM7 features, understand the process for flashing an MTD/BML ROM, and feel prepared for the worst then go for it. If it is successful for you it will change your whole perception of the Fascinate. Add on the new Glitch V11.1 kernel and you will never run anything else!!
...If you are just flashing it because it is the flavor of the week... I'd wait till it is in nightlies before flashing. Just reduces the chances of an oh-s#%t-moment happening.
powerstroke said:
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
Click to expand...
Click to collapse
I was exactly where you are 24 hours ago myself. I took the plunge and I'm glad I did. CM7 is the best thing that has ever been on my phone. I had zero installation problems. I haven't even tried the new 1.7ghz kernel yet. Got nems 1.6 though doing nicely. While I echo the precautions of the prior post I whole heartedly endorse the switch
Sent from my SCH-I500 using XDA Premium App
gkirby11 said:
Well the first thing you should do is read, read, and read again on the CM7 test build thread along with the waiting room in the general thread. For every handful of success stories there are even more horrible failures.
Another question you should ask yourself is why are you considering switching? Because you know, understand, and like CM7 features? Or because you have seen endless posts on here about how it is now working?
Believe me I love CM7. I ran it for my daily driver for a few months back when 60% of it didn't function. Now that it is in TEST build 10 (still not full release like Ultimate Kang bang 2.1 that you are running) people are flashing it like it is a full RC. They are also having terribly problems and soft bricked phones more than an Touchwiz based ROM at the moment.
If you really like CM7 features, understand the process for flashing an MTD/BML ROM, and feel prepared for the worst then go for it. If it is successful for you it will change your whole perception of the Fascinate. Add on the new Glitch V11.1 kernel and you will never run anything else!!
...If you are just flashing it because it is the flavor of the week... I'd wait till it is in nightlies before flashing. Just reduces the chances of an oh-s#%t-moment happening.
Click to expand...
Click to collapse
Great answer!
powerstroke, like he said; read, read, and read some more. that's what i did. and i ended up going for it, and so far i am not looking back. Just prepare yourself with backup plans in case something goes wrong.
From my point of view, I'm enjoying CM7 as least as much more than CommRom as I enjoyed CommRom more than Stock. I'd say that it's CM7 from here on out for me, except that's what I said about CommRom not too long ago. Who knows what the Devs will come up with next?
I liked CM7 but the low in call volume and the sucky AOSP camera made me go back to CommRom 2.1 with EC09 radio.
i agree, just read up like crazy so you don't mess anything up but take the plunge if your prepared. i went from just stock, debloated ed01 to the latest cm7 and i've had no problems. look up omfgb though because i'm waiting for that one to be more functional and i'm probably gonna switch to it
Give miui a shot to. It's pretty.
Fascinatemtd MIUI 1.7.15 - Glitch v11.1
Ok awesome guys appreciate all the info. I think I'm going to give it a whirl. Main question I have now is, what is the easiest and safest way to switch over to that rom from where I am now? Just do the factory reset, wipe cache, and wipe dalvik cache? Then flash the CM7 rom through recovery? or something else? Just want to make sure I do it right lol
^^^
That's why everyone said read.....
Ha...No **** lol. I understood that part but for people that might have already switched between those roms might have other suggestions. No need to be a smartass
Well since your being a smartass, lol, want to find me a forum that specifically shows how to switch from a froyo rom to cm7????
powerstroke said:
Well since your being a smartass, lol, want to find me a forum that specifically shows how to switch from a froyo rom to cm7????
Click to expand...
Click to collapse
Easy, try the thread for the CM7 ROM in the development section. jt covers it in the op, and there are several more specific walkthroughs in the the thread.
provided by Land Shark:
(coming from stock DL09)
1. Power down phone, pull battery
2. ODIN EC09 modem, pull usb cord, close ODIN
3. Reopen ODIN, connect USB, flash fixed CWM 4 from OP of CWM7 thread (here: http://forum.xda-developers.com/showpost.php?p=14554015&postcount=1)
3. Close ODIN, pull usb cord, put battery back in phone, hold volume up, volume down, and power buttons but release all three as soon as you see samsung logo flash for the second time
4. Flash CM7 07/13 build and GAPPs (Google Apps) from OP
5. Reboot phone, wait for ROM to fully boot and load, finish setting up phone with contacts, apps, etc., profit.
ok..followed your instructions. now im in a loop when its trying to flash. "waiting for sd card to mount" over and over. counting down in seconds? what should i do?
If you are serious about diving into cm7 read all u can I red for 3 days. Nearly 2500 posts and its knowledge I'll need should anything not go smooth you may have one glitch that u try and fix mess that up and its steam rolls into a long process but if u follow word for word and know exact orders of Odin and flashes and how to get to the proper cwm its beautiful just make sure ur beyond prepared before the first click that's about the best advice I can give 2cents are now in the pot
JOrtenzi said:
provided by Land Shark:
(coming from stock DL09)
1. Power down phone, pull battery
2. ODIN EC09 modem, pull usb cord, close ODIN
3. Reopen ODIN, connect USB, flash fixed CWM 4 from OP of CWM7 thread (here: http://forum.xda-developers.com/showpost.php?p=14554015&postcount=1)
3. Close ODIN, pull usb cord, put battery back in phone, hold volume up, volume down, and power buttons but release all three as soon as you see samsung logo flash for the second time
4. Flash CM7 07/13 build and GAPPs (Google Apps) from OP
5. Reboot phone, wait for ROM to fully boot and load, finish setting up phone with contacts, apps, etc., profit.
Click to expand...
Click to collapse
well this is what i did and still have problem!!!!!!!!! T.T
1) odin ebo1 with atlas pit 2.2
2) cwr blue on CM7(jt site)
3) installed cm7 latest one 7/17
4) now stuck on cm7 logo and just stuck there... nothing happens ........... any HELP????????!!!!!!
izzjkjoe said:
well this is what i did and still have problem!!!!!!!!! T.T
1) odin ebo1 with atlas pit 2.2
2) cwr blue on CM7(jt site)
3) installed cm7 latest one 7/17
4) now stuck on cm7 logo and just stuck there... nothing happens ........... any HELP????????!!!!!!
Click to expand...
Click to collapse
This works for me, but in step 2. I odin cwr 3-30 fix all. immediately Boot into it and wipe everything, then flash the 7/4 build, from there use cm7 recovery from power button to flash newest build w/o wiping...worked multiple times for me.
Sent from my SCH-I500 using XDA App
I was on com rom with ed04 radio, i just did the 3 wipes and install miui zip, takes less than 5mins.
Sent from my I500 using XDA Premium App
Hey All,
I've been looking for an answer for over a day now, but can't seem to find anything about my specific problem. Here's what happened:
I had flashed to ICS 4.0.3 on my Samsung Vibrant about a month ago and everything was working great until yesterday when I woke up to find the "Encryption Unsuccessful" screen on my phone. I did a little research to find out that there is a fix to this and to NOT reset the phone. So, I took the steps to ODIN the phone back to Stock Eclair in hopes that starting from the beginning again would be easiest way to fix the problem. The ODIN process finished completely fine (PASSED), but now when it reboots, I only get to the first "Vibrant" screen, then it shows the battery and spinning circle icon. Apparently it won't fully reboot. I've tried to ODIN it back to stock several times, and I keep getting the same results. I can get it into download mode and plugged into my computer, but that's about it.
From the posts I've read, it sounds like my phone might still be okay to recover since it does power up, but I can't seem to find a solution to get it fully back up and running.
Any help/recommendations would be greatly appreciated!
Thanks in advance!
Maybe your JFD file is corruption. Check with your MD5 sum if there any error or mismatch.. Just give you an idea.BTW what Odin are u using. I recommend Odin 1.7 I stay away the older Odin or the newer Odin
You are screwed.
Sorry to tell you this but i had the exact same problem and found no solution whatsoever to fix the phone. I finally gave up and bought a Galaxy Nexus. You can try flashing Eugene's Unbrickable Froyo Rom which is flashable through odin as a .tar package along with the pit file. You might be able to fix it but i highly doubt it. I flashed Eugene's rom and got the same results as you described. By any chance did you click "Reset Phone" when the "Encryption Unsuccessful" showed up? If so well yeah your phone is pretty much paperweight as of now...until someone finds a solution. Like you i am also able to access download mode. So i guess there may be a way to fix your phone. Not saying it's impossible...hopefully someone finds a solution soon.
Here is the link to Euguene's rom: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Good luck.
OP, what ROM were you running (specifically. Not just ICS 4.0.3-what is the name of the ROM)? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Check here out for a possible solution/workaround.
Replacement Vibrant Coming
Thanks for your recommendations/help guys.
I decided to go to T-Mobile and complain and they are sending me a replacement phone. Apparently it's still under warranty, so it won't cost me anything, and if my data is lost, then so be it...at least all my contacts will still be in tact through my Google account.
Merio - I did NOT hit the Reset Button when I saw the Encryption Unsuccessful screen. Before doing anything I did a little research and I found a forum here on xda that said to not hit that button, and tried to explain a way to fix it using the Heimdall One-Click. Basically it sounded like I'd be flashing back to a Gingerbread ROM. So, instead I just went ahead and tried to flash back to stock Eclair. The results of that were obviously not good.
Woodrube - I was running the Passion 13 ROM (ICS 4.0.3). Was really enjoying it until I got the Encryption "Screen of Death"
I don't know what Kernel it was, actually, I don't really know what a Kernel is...
Thanks again guys. Hopefully I'll be up and running on my replacement phone soon!