Related
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
stoanhart said:
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
Click to expand...
Click to collapse
Was her phone stock before you started tinkering with it?
In any case I'd suggest re-download nerov3 (to avoid corrupted download issue), ODIN back to JFD (remove the ghosts from the past ROM's) and reflash.
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
stoanhart said:
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
Click to expand...
Click to collapse
Good luck!
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
stoanhart said:
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
Click to expand...
Click to collapse
Did you re-download nero? It might be a corrupted download, I haven't seen anyone with the same symptoms.
Does it happen if Voodoo is disabled?
EDIT: Saw that you didn't even have a chance to enable it, hmm, try a different ROM? Axura or Eugene's work.
No, I didn't try re-downloading it. Perhaps I'll give that a try, although it is the same file I flashed onto my phone.
After a bit of time playing with Nero, though, I'm considering going back. The parts that work are slick and wonderful, but it very much feels like beta software. In particular, scrolling lists or web pages is choppy. I've heard this criticism of Android before, but I've never experienced it with the original Vibrant software. It was always so smooth. It makes me think that maybe Samsung was using GPU acceleration in some places. Also, I seem to have some problems with the touchscreen becoming unresponsive, especially in the browser if it's blocked waiting for data (another bug...).
Is it possible to run the JL5 modem on the stock image? That would be great.
I updated to EB13 from DI18 originally using ODIN and the eb13.tar. Things were fine, no real bugs except the known video camera bug and screen lag. I was able to fix the screen lag once I rooted and ran the sensorcalibutil_yamaha scrpit. My TWS was only 2% and had no 3G data problems whatsoever.
Recently I decided to try out the deodexed rom from the dev section, but when I started it up I kept getting the "buz...buzz-buzz-buzz" over and over. I though I must have done something wrong, so I formatted my sd card, wiped my phone, cache and dalvik cache. I then used ODIN to re-install the eb13.tar and I re-rooted using oneclick root.
This time around, I now have 55% TWS in the same location as before and 3G data drops like crazy. Also for some reason the market app won't update itself to the new version and is stuck on the original, old style. Also interestingly, on this flash I had zero lag problems and my compass and gps work flawlessly.
I'm not sure what is going on or why this would happen, anybody else experience something like this??? I am worried because I have a phone interview in the morning and can't afford signal drops when I have full coverage. I am going to re-do the whole process and hope that fixes it
I odin'd two times trying to fix this again, no dice. I never should have messed with things because all was good until I started messing about.
Found a solution for now though, I Odin'd back to DI18 and am calling it a night. I can't afford a spotty data connection for my interview in the morning. I'll report back once I start tinkering again
Odin to DI18 and don't do anything. Just turn off your phone.
Copy the EB13 update.zip to the memory card and delete your "Android" folder as well as any app specific folders for cache or whatever.
Put in your memory card and boot into recovery. Flash the update.zip and reboot.
Once the phone is on you can use the OneClickRoot 2.5.5 to get root and recovery.
I still get the TWS problem but airplane mode fixes that.
arashed31 said:
Odin to DI18 and don't do anything. Just turn off your phone.
Copy the EB13 update.zip to the memory card and delete your "Android" folder as well as any app specific folders for cache or whatever.
Put in your memory card and boot into recovery. Flash the update.zip and reboot.
Once the phone is on you can use the OneClickRoot 2.5.5 to get root and recovery.
I still get the TWS problem but airplane mode fixes that.
Click to expand...
Click to collapse
thanks, tried this but it didn't correct any of the problems. My market refuses to update to the new version for some reason. When I Odin'd back to DI18, the market ap updated itself on the second launch, no problem.
As far as TWS goes, the issue is still persisting. I did notice that if you are using the data connection for something like shoutcast radio (internet radio) there is no drop at all, and the signal is almost boosted. But if you aren't actively using the connection it drops, connects, drops, connects, over and over. It is absolutely killing my battery life.
Edit: Fixed the market update problem by clearing market cache and data. Now if we can find a fix for the camera lag and TWS problem, I will be a happy camper
First off let me say hello to everyone! I have never posted here but do A LOT of lurking . Big ups to all the devs here. You have helped make my Fascinate 100 times better than it was out of the box. I post over at fascinate forums and posted this issue I have been having. If anyone can help out with this I would appreciate the hell out of it.
Running
Community Rom v 1.2 w/ stock kernel(WHICH IS AWESOME BY THE WAY! Best Rom I have ever used hands down!).
EnV Theme(which is equally awesome!)
Can not get my computer to recognize my phone via USB(phone issue)
So here is what happens.
My USB mount was working fine until last night. Now every time I connect my phone to my computer I get a message in the bottom right corner telling me windows does not recognize the USB device.
When I click the message I get this
USB Device Not Recognized
USB Root Hub
Unused
Unknown Device
When i click the unknown device I get this
Windows has stopped this device because it has reported problems. (Code 43)
This is not a computer issue...it is a phone issue. I have tried plugging my phone into 3 different computers, installed the drivers, and get the same issue every time. If it is an internal error there is nothing I can do because I can't Odin back to stock and take my phone in to Verizon.
Things I have tried
Uninstalling and reinstalling the drivers multiple times, different drivers(generic and the ones from the samsung page), fixing the drivers, different USB ports, different USB cables, different rom, different kernel, re downloading drivers(both).
I cannot figure this out. If anyone can help me it would be much appreciated.
:edit: My phone WILL charge when plugged into the USB.
p.s. Once my Pizza gets here I am going to attempt putting the phone into Download mode. I completely forgot to check if Odin would recognize it in DLM. If it does I am reverting back I am going to revert back to stock and have a rooting/flashing party by myself tonight(I have beers).
I'm sure your already aware to make sure your in usb debugging mode. mentioned it just incase.
Yes my phone is in debug and set to mass storage. I want to try a hard reset but don't want to be such with a stock fascinate if it doesn't work.
Alpha Tappa Lambda
I had similar problem, and my Odin wouldn't work either.
Turned out to be some dirt in the usb port, cleaned it out with a scrap of paper with isopropyl alcohol. After a couple of cleanings, the PC recognized the device for the first time in 2 weeks. I am not the only one who has had physical problems with the usb port, search on it. The Fascinate seems to be fragile in this respect.
Of course, if your Odin detected the phone then its something else...
Good luck.
I had this exact problem and it was the USB cable for me
I didnt think of it initially cuz it would charge my phone fine
I went through every step over and over and even reformatted my entire PC
Then i grabbed by coworker's ATT captivate charger and everything worked fine...
so my suggestion is to find someone with a samsung OEM charger and see if that's your problem
I also think it has something to do with the USB port. I had the exact same issue and it ended up being dirt in the port on the phone
masterjeff said:
I also think it has something to do with the USB port. I had the exact same issue and it ended up being dirt in the port on the phone
Click to expand...
Click to collapse
I had the same thing, would charge but computer wouldnt see it. Cleaned port with a little rubbing alcohol and it worked like a charm.
My new phone will be here tomorrow. I ended up flashing ED01 with CWR and now have a fully stock fascinate ready to be sent back.
I haven't read this thread for awhile but I wish I would have tried the cleaning method before having to get a replacement phone in. Oh well...should be a fun re rooting a brand spankin new stock phone tomorrow
Well now I know what it was. I just got my new phone in. All was well.
Rooted to EF, Odin'd the EC01 radio, and flashed OTB 1.3 and was just setting everything up. I rebooted after flashing everything.
Then came the fast media scan hack. Guess what...my phone will no longer connect via USB after flashing that.
Does anyone know how to remove this? I can no longer Odin anything and I am pissed off right now.
p.s. not pissed off at anyone in particular...it's my problem for flashing not the devs...but seriously this sucks.
Re flashed the Rom, went into terminal emulator and restored the default media scanner, rebooted phone, rebooted computer, USB works fine.
Right after I flashed the fast media scanner I had the same problems I was having before...now everything is working just fine. Not trying to bust on adrenalyn or anything. Just reporting my experience with the fast media scan hack.
Cannot Get Computer To Recognize Phone
I tried installing the Anonymous ROM and got bricked. A friend of my was able to get it back to factory settings. Now, no computer will recognize my phone.
I have tried several computers, 3 windows 7 computers and 1 iMac. None of them recognize the phone.
I have tried two different cables and every USB port on all of the computers. Nothing seems to be working.
All I wanted to do was get the Sprint crapware off my phone and now I can't even get back to where I was.
Also, when I try to do the ROM manager I am getting a file signature error.
You can try Software Data Cable app, This app allows you to connect to your computer via the same wifi connection. You might give it a shot.
Sent from my SCH-I500 using XDA Premium App
I had this problem once. I think i went into my usb settings and click ask on connect or something like that. Worked for me at the time.
Sent from my SCH-I500 using XDA App
My phone is doing that now how do you undo the speed hack?
Sent from my SCH-I500 using XDA Premium App
I was in the same boat. Was rocking UKB ComRom 2.0 when all of a sudden I could no longer connect my phone via USB to my PC. I was running Windows Vista and had never had a problem before. I tried multiple PC's and multiple cords. I was worried that I would have to get a replacement.
I cleaned the USB port on the phone with no luck. Installed and deleted and reinstalled the drivers 3 times with no luck. Made sure USB settings on the phone were correct. Toggled the USB settings a few times just in case- no luck. Did a Dalvik and Cache wipe with no luck. The only thing that worked for me was the do a factory reset/Wipe and then redo my phone from there. It left UKB ComRom 2.0 on the phone and I just had to add back in my data. Just an FYI.
ive had this issue since ukb 2.0 i moved to cm7 mtd did a full data wipe and still have this issue >,> wonder if i have to manually change it or somthing
Just had this happen again today on my phone. Fixed it back on the 29th after doing a factory reset and then reinstalled my apps/ etc......This time all I had to do was a Davlik, Cache wipe and it seemed to fix the problem. Never had this happen before ComRom 2.0, but not it is happening more frequently it seems. Any ideas?
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
So i would say I have a pretty bad problem. Randomly my phone shut off, and when i tried turning it back on, the logo would show up but the screen would later be turned off and only the buttons would light up(home, back, settings, search) THIS IS THE SGH-T959 Model.
I DID NOT root my phone or anything, and the state in which it is in right now i THINK is called a "brick"? My phone randomly keeps vibrating and the buttons stay lit up, but the screen is just completely black. When turned off the battery just keeps refreshing and show a little bit of green, but it doesn't charge past that.
I followed some instructions and I think it's in recovery mode right now, what i see on my screen is Android system recover <3e>. I have the options to choose "reboot system, reinstall packages, delete all user date, delete cache data, and format internal-sd card" I tried rebooting but didn't work, neither did reinstall packages and the error tat came up was E: failed to open mnt/internal_sd/update.zip(No such file or directory). I think that is fine though because i WAS NOT trying to root my phone or anything, this problem just randomly occured. I searched and found things about people getting this problem after rooting, but i didn't try rooting it.
I don't know what to do next, I can't backup any of my content or data since my phone screen won't turn on.
I tried all the common things like taking out the battery, etc, didn't help.
I also read about reverting it back to stock, but my phone is technically already in stock, since all i did were occasional kies updates, nothing that relates to rooting it or flashing it
PLEASE HELP!!!
Does your computer recognize the vibrant when you plug it in?
nope, and when i turn on kies it tells me to connect my mobile phone
And you have data to get it off before we can consider wiping it?
Don't use kies. It will brick your phone. Happens over and over. Use Odin to go back to stock and start over whatever it was you were trying to do.
what do you mean if i have data? If you are asking if i have my data backed up then no I don't.
and I don't even remember the last time I used kies, probably because there are never any updates. And isn't it like the official way of updating your firmware?
In recovery do delete user data and wipe cache if that does not work just reinstall stock rom using odin but go to download mode first. That is pretty much everything that can be done at this point.
If after Odin you still have wired problems in most cases it means water damage and you mother board needs to be cleaned or replaced.
Sent from my T959 using XDA App
Gun thanks so much, I fixed it after deleting user data and wiping cache. Unfortunately the apps were deleted so it's basically a brand new phone.
THANKS A LOT once again
Was it that simple? Good for you.
Sent from my T959 using XDA App
Woodrube said:
Don't use kies. It will brick your phone. Happens over and over. Use Odin to go back to stock and start over whatever it was you were trying to do.
Click to expand...
Click to collapse
Any idea where to find the JFD or JI6 stock Odin images?
All of the links turning up on XDA seem to be dead.
Just picked up this device used for the express purpose of hacking around in it, so would love to have a stock image on hand to restore when needed.