[Q] I need help with my fascinate - Fascinate Q&A, Help & Troubleshooting

I have a fascinate and have successfully rooted it, flashed the cricket info (i got talk and text) and had 3g at one point. All of the sudden 3G went out. I put CYANOGEN on there, latest 7.1 i believe for the fascinate.
Upon trying to revert back to the original ROM so I can get in there with PST and CDMA WS, I encountered a very strange set of problems and now I am just stumped. I tried to ask a couple of other people and no one seems to know what is happening.
Here is what happens, I try to put the original ROM on there, by using ODIN and doing the atlasv2.2 pit file, and the original ROM, froyo, and the other one eclair i think.
When I use odin it gets to the system part, then right after it goes to the part that would take the longest, and I forgot what its called, dataFS? it has FS at the end, and then the phone (while odin is still going) will go to either a blue screen or a green screen with no words. If you look closely, it appears there is a clock at the top right just like if the phone was on.
I have not overclocked this device at all so thats one thing that can be ruled out.
I've tried odin using both battery in and battery out method as different guides have stated different things. When the battery is out, I get a blue screen. When its in, i get a green screen.
The screen appears right after the normal odin screen, with the status bar, but it will dissapear when it comes to the dataFS part (right after system) then it will take about 20 - 45 minutes and I will get an error screen on odin.
Funny thing is i've used odin and that method and it worked the last time. It works fine if I need to flash a clockwork recovery. However, upon booting into recovery, half the time I will get an error that has to do with BUILD.prop and SCH-I500. This is when I try to flash any rom except MIUI. For some reason, MIUI kicks this phone around and its the only rom that works. CM7 wont work, stock won't and every other rom wont.
So, to sum it up, my main problem is ODIN and its funky behavior, and not being able to go back to stock so I can see if my 3g settings are correct. If you have any information, even if its just something to help get my wheels turning, then please post it up, any and all help is greatly appreciated folks, thanks.

I dont know if this would work but if u think the problem is Odin then I would uninstall odin and reinstall the newest version available. Also, make sure the phone driver software get done the same.
Then after that I would try odin again. Phone off, battery out. Open odin. Plug in usb. Make sure phone set usb to debug. Hold vol down button. Odin should see your phone.
Im sure u know all the steps up to this point but try again.
Good luck
Or u can try running odin as Admin on the comp.

Also if the problem persits I saw a user had a similar problem and of turned out to be his usb cable so try a different one if you can't fix it.
Sent from my ADR6350 using Tapatalk

See, thats what I thought too, but I will give it a shot and see. I doubt its the drivers, odin or the program, file or anything else because it does work with clockwork, and i've downloaded it several thousand times, plus it works great when I do anything but flash the original rom, odin will go fine. Drivers seem fine, it communicates and all that perfectly so I also highly doubt that.
I will get another cable and just try it on a whole different PC to see what happens. I was really hoping someone had this happen and had a fix but I might have to do some heavy delving. THANKS GUYS! I will try this and report back.

It was the cables, used a brand new USB cable and it worked, strangest thing that a cable can work but not work and its just a bunch of wires, but almost all my audio cables have to be bent or else you will loose a channel. I guess its just poor quality materials. So thank you, it works now and it was just the USB cables.

Related

after data wipe, phone boots to black screen, rooted but no CWM recovery - confused

I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks

[Q] Hard Bricked, unrespsonsive, Jig doesnt work, about to get physical

So, heres my problem. I have 2 samsung fascinates. I screwed one up a while back and was able to pull it back together and get it into ICS on CM9 with all the proper files using Odin.
I recently got a second samsung fascinate and was attempting to flash the same files, through Odin, but was having trouble.
I was able to get CWR (I believe it was voodoo) onto the phone, but once in recovery mode and having cleared all cache's, wiped files, and factory reset, I still could not successfully instal the files from the SD card (the same ones that worked on the 1st fascinate)
SO
I downloaded another version (or so I thought), Pushed it through Odin, Odin said it passed and auto restarts the phone. The phone never comes back on.
In hindsight think that CWR somehow ended up being deleted from the phone (if thats possible without doing it on purpose) before what was pushed by Odin was actually pushed. The file might have been wrong, im not sure, I will post up the exact file name when I get home.
At this point, the phone is completely unresponsive,. No holding the volume, plugging it in, putting the battery in. Jig doesnt work, Heimdall Doesnt work, Fastboot doesnt work. No download mode, period. No lights, no vibration. Tried multiple batteries, tried assuming the screen was bad, tried multiple cables, tried plugging into wall and computer. Nothing.
Mac will not notice the device at all once its plugged in, however, PC notices and starts to wig out. I have to hold the power button down, while its plugged into the computer to allow for it to search for drivers
The driver is SEC S5PC110 TEST B/D notification.....I feel like this is for a phone other than the fascinate.
Either way, I try to download fascinate drives, or the driver its calling for, both being unresponsive.
Am I completely screwed? Or is the questions more that I found myself at the point the I have either deleted what was deemed "Un-deleteable" or do I need to take the board out and get a soldering iron?
Also, I know a developer, I have taken it to him and he looked at it and scratched his head......hopefully someone has some sort of solution. Thanks
What file did you try to flash?
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Philveatch said:
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Click to expand...
Click to collapse
thats what happens when you flash files for another
device to this one. there is a guide in the general section that has everything you needed. hopefully next time you do a bit more research before you get flash happy. at this point unbrickable mod is your only way out and that requires some microscopic soldering skills.
It looks like you flashed a bootloader for the Galaxy S2.
Interesting. It was in a fascinate forum talking about how to add ics to a fascinate phone.....hmm.

Problem on my Vibrant

Hi guys im not quite new when it comes to android.
last night i was trying to upgrade and flash a CWM on my friends vibrant whe it stopped. i turned off the phone when tries to turn it back on.... the phone quite turns hot and not like my phone when im flashing it.
i got all the files download and read all of the instructions before starting ofcourse.
first the phone doesnt turn on, then i manage to enter the DOWNLOAD MODE again but somehow the Laptop doesnt detect and gives a yellow punctuation mark on the device. i tried to install and flash the rom but it doesnt continue. i tried putting or plugging it to a diff port but still no luck.
can someone help me and answer this question? is this thing hard bricked = im screwed
any help would be gladly appreciated. thanks again guys in advance
Try a different USB cable as well as a different USB port.
http://forum.xda-developers.com/showthread.php?p=30831184
Read that post, then, read the thread from page 1, just so I don't feel like I've had the same conversation twice in 1 day.
Shouldn't take long its only a few posts. See if this applies to your situation.
thanks boss but i tried the cable with my galaxy mini and it worked when i tried to flash and went back to stock rom. changed the port as well but still no luck....
the phone as well doesnt turn on like the way of a soft brick. a picture of a phone wanted to be connected to a pc, black screen it is though but the phone goes to DOWNLOAD MODE
Try reinstalling drivers from AIO toolbox. Open Odin as administrator. What does Odin say exactly? Is there a yellow box, if so what does it say in it?
i tried reinstalling the drivers i have downloaded but still no luck, odin detects the phone and when it doesnt i re-install the driver so the computer would detect the COM port of the phone. the odin doesnt push through and no BLUE bar on the phone it self. such as the indicator for the flashing. i tried as well running odin as the administrator but still no luck. so do you think that this could be a hard brick, i dont think so cause i can still enter the DOWNLOAD mode of it. the phone turns hot when im on the download mode. could this be a hardware problem.
No its probably not a brick. I think its a communication issue. I would still think its possible to fix it. As far as it getting hot, not sure but the fact that it gets to download mode is a beacon of hope.
I've got to go to bed, will be back tomorrow to check on this.
yeah i hope thesame way too man. thanks for the reply.... time for you to take some rest. thanks again. i'll post the reply if ever the phone gets fixed
thanks for everything man, the phone now is resurrected after JTAGGING. but i know that those technicians who charged me 1000php just did the flashing on ODIN. i know the thing i've done wrong why it didnt work the first time. now it is running up again. the firmware that was flashed was for TELUS. it now shows T959D. i'll follow the guide fully on flashing and upgrading this thing
I had the same problem as you this morning. I tried driver, after driver, after driver and nothing worked. Eventually I gave in and used my sister's laptop and that did the trick. Mabuti ayos na ang cp mo. Ingat.

Status 0 in cmw

When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
We need more info like what did it specifically say. Be as specific as possible
Sent from my Nexus 4 using xda app-developers app
RedJack117 said:
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
Click to expand...
Click to collapse
that's "usually" an error you get when the zip is corrupted.
but occasionally you'll get it if your running an i9000 roms (I've had it interchangeably with status 7 before)
I would try re-downloading and flashing the zip again.
if that doesn't work try downloading and flashing fluid kernel
then go to "advanced" and select "reboot recovery".
then try flashing the rom again.
Status 0 error on anything I try to flash using CWM
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
After you PM'd me, I started looking around about the Status 0 error being thrown. All signs point to the Updater Script that in the ROMs that you are flashing. My hunch is that once you flashed the CyanAOSP, that changed your build.prop from T959 to i9000 and that is why you are getting the error. I'm pretty sure there is a way to fix it (see below)
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
The zips that you mentioned are probably the standard Root.zip and the CWM zip from s15274n's thread stickied at the top of the Q&A section. Keep those handy.
Click to expand...
Click to collapse
Some answers in-line above.
**********************************
Let's get a few things straight before we start. I am still looking for the Heimdall JFD package, but I think that I know where it is. Pretty sure I put it on one of the external HDDs that I have. I'll try to upload it tonight or tomorrow night, as I am away all weekend with the family. I really don't think that you'll need it, but best to have it and not need it, than need it and not have it.
Theoretically, once you Odin'd back to JFD, I would think that it would've reset your device ID back to T959, but I guess that it didn't. This is what I would do. Odin to stock JFD and then boot it up and let it settle. Root it using the Root.zip that you have already used before. At some point you'll need to pick a ROM to settle on, even if only to get past this hump. (I use Sada's CM11 for my sons' Vibrants. Not that there is anything wrong with any of the others, but I just basically set it and forget it for my boys. I think though that he may have stopped development for it though, so I guess I'll be looking through the dev section myself here in the near future.) Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). My issue was a Status 7 because of the device ID being changed and the Recovery/Kernel combo weren't letting me flash. I basically opened up the ROM.zip and deleted those line and re-zipped it up and then flashed it (did it all on the phone and no PC, but I'm crazy like that).
Let's let a few of the current device Devs weigh in and see what they think. Already mentioned nirogu325 above, but let's try @epicboy and @dzee206 and @sada23. If they are inclined to come and help, it would be much appreciated.
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
Click to expand...
Click to collapse
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
The phone only had one major issue before I started messing with it - back & home buttons not working. I honestly can't remember how and what I did to put CyanAOSP on it but I ended up with 2 issues after putting it on. Only the Menu button works (eventhough all 4 lights up) and the USB seems to be grounded. I managed to work with it the past year up until I Odin-ed it back to JFD. When the phone is off and battery still has charge, the loading button would come up followed by the empty batt image at the background. This will loop until the batt dies. The only way to turn it on is by connecting the USB to a power source. Accessing download is easier because all I needed to do is remove batt then press and hold the vol up & down before putting the batt back in. Getting into recovery is a bit trickier. You'll need to wait until you actually see the phone charging before doing the 3-button combo.
Last Saturday, my daughter had a school event and I brought this along because it took better pictures than my S3 knock-off. During the parade, after shooting a video, it would automatically take me to the preview. Since, both back and home buttons were not working, I was stuck. Only option was to reboot it. What makes it interesting is that there is no reboot option on the JFD. It was a good thing that I had my power bank with me. I really did not want to constantly reboot it so I thought of installing one of those virtual button apps. I managed to install ToucherPRO before their presentation which made it much easier. To my surprise, it somehow revived the back button on the device itself - I noticed it when I got home that night to transfer the photos and vids.
I mentioned this so that you guys will have an idea on what I need to go through to get it fixed - somewhat, at least to a more tolerable state. (you won't believe it but the tips of my fingers hurt due to the number of times I have to go into recovery or download)
@Woody
Woody said:
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
Click to expand...
Click to collapse
Yup. I actually find it both weird and interesting - which games work and how they work.
Woody said:
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
Click to expand...
Click to collapse
Remember I mentioned my hesitation using Heimdall and Bay_wolf's AIO toolkit regarding hijacking drivers and stuff, Kies on this PC is now useless. It won't even recognize the phone after I tried the toolkit - which is good, I guess.
Woody said:
... Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). ...
Click to expand...
Click to collapse
I read about this when I started going back through the threads. As you mentioned, this is an old phone. Old phone = old threads. What I do is I read everything on page 1 then skip over to the last page, going back. Seems to be more effective specially for DL links.
I was actually reserving this one as part of my 'last option' fix. From experience, editing scripts is far more dangerous than flashing a 'working' one. I managed to root my other DD this way, but went downhill from there - ended up bricking it 3 times.
Anyway, I think I got it - or at least, the correct way of doing it. It took me 3 days....
After day 1, I ended up with 8 update.zips (7 CWM and one ROOT) and at least 2 copies of ROMS, GAPPS, MODEMS, and KERNELS on my SD card - only the update.zips worked, the rest either gave me status 0 or leave me with the 'Vibrant Samsung' bootloop. I had some progress on DAY 2. I read something like what epicboy said:
epicboy said:
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
Click to expand...
Click to collapse
I tried several JB ROMS listed on the Bible but, the problem was, I can't get into recovery - it was all 'blurry'. When I tried a different JB ROM, it also worked but was still 'blurry' during start up and on recovery. That's when I remembered Woody's post regarding rainbows and bootloaders.
DAY 3: For some reason, everything was flawless. I was able to install JB then KK. EFFORTLESSLY, if I may add.
@epicboy
I'm planning to spend a couple of days more on this Vibrant before I mess with my other phone - a knock-off SGS3. I was drawn to L-Droid because the screenshots and contents of page 1 of their thread was specifically for the T959 and not the I9000. I know it's not really a big deal because the ROM will work and changing the build.prop for 'cosmetic purposes is easy. What really concerns me is the camera. Sadly, the T959 only has only one camera and if the camera app that you're using (stock or otherwise) has a feature to switch from back-to-front and you accidentally press that, it messes it up to the point that you can't use it anymore. I have downloaded the ROM and will try it out in a couple of days. Will send you a PM or reply on the thread regarding my feedback. I've flashed it several times but really haven't been able to do it flawlessly like in DAY 3 - which I find really weird.
Tnx peeps!

Help! Phone is stuck like Ive never seen! Mobile Odin!

Hey guys, I'm really hoping someone can tell me of a solution Ive not though of.... So Ive got the note 3 from sprint. currently had 4.4.4. I shoulda just left wellenough alone, I realize, But I tried to flash just a modem via mobileOdin and upon reboot, it will say "recoverybooting" and then I get the blue android. Thats all. This was just over 6 hours ago I did this and Im dead in the water, Ive SEARCHED the internet high and low and there are other facing similar problems, but it seems like every mishap Ive read about EVENTUALLY gets fixed. This just will not do anthing with any button combo as far as recovery and/or download mode. I cant access download mode either. recovery never actually boots, just a forever frozen blue android.. Now, with the phone attached via usb to my PC, it DOES see it as COM7, BUT REGARDLESS what ive tried it just remains at the "recovery booting" spot then blue android until I pull the battery again. Please HELP.! IF ANYONE HAS ANY SUGGESTIONS I would be just delighted if you may have some other approaches to this matter. THANKS! Please let me know iTs DESPERATE!
Zscott87 said:
Hey guys, I'm really hoping someone can tell me of a solution Ive not though of.... So Ive got the note 3 from sprint. currently had 4.4.4. I shoulda just left wellenough alone, I realize, But I tried to flash just a modem via mobileOdin and upon reboot, it will say "recoverybooting" and then I get the blue android. Thats all. This was just over 6 hours ago I did this and Im dead in the water, Ive SEARCHED the internet high and low and there are other facing similar problems, but it seems like every mishap Ive read about EVENTUALLY gets fixed. This just will not do anthing with any button combo as far as recovery and/or download mode. I cant access download mode either. recovery never actually boots, just a forever frozen blue android.. Now, with the phone attached via usb to my PC, it DOES see it as COM7, BUT REGARDLESS what ive tried it just remains at the "recovery booting" spot then blue android until I pull the battery again. Please HELP.! IF ANYONE HAS ANY SUGGESTIONS I would be just delighted if you may have some other approaches to this matter. THANKS! Please let me know iTs DESPERATE![/QUOTE
Have you tried removing the battery for a couple of minutes ? If you have read a couple of my threads on NH7 4.4.4, once your there downgrading anything is risky. Here is a link to read http://forum.xda-developers.com/note-3-sprint/help/4-4-4-download-mode-t2877528 . Here is a link for a recovery from a hard brick, by creating a boot image and then copy and paste it on a sdcard http://www.rom-central.com/showthread.php?87-GUIDE-HOWTO-Recover-from-a-HARD-BRICK-N900V-NC2-NC4 there are several sites on this type of fix, I just can't remember where they are. However, I do have something that may help, on one of those sites there was a link for someone who has already created a SM-N900P Unbrick img for Sprint and I downloaded it just in case. Here is the link http://www.mediafire.com/download/l6q1152x5c9d4h6/N900PUnbrick my copy. From what I understand you need to format/erase your sd card then copy and paste the unbrick img to the sd card from a PC. Pull the battery and install the sdcard back in the device, then try and boot the phone into download mode. Here is another link http://forum.xda-developers.com/showthread.php?t=2439367 I have not had to do this so you will have to do a little reading to be sure.
Click to expand...
Click to collapse
The fact that it still shows up as COM is a good sign.
Get a hold of ODIN 3.07+ I had issues with ODIN 3.06.
Here are a few things to try:
1.Take the battery out and hold all the buttons that you normally would to boot into recovery. While holding all the buttons, plug in the usb cable. If it boots into download mode, awesome, just put the battery in before you flash.
2. .Take the battery out and hold all the buttons that you normally would to boot into recovery. While holding all the buttons, plug in the battery. Hopefully it will boot into download mode.
3. try different cables, remember regular micro usb cables work with the note 3.
Make sure you put the modem file in the phone slot, and the rom/system tar in the pda slot.
Best of luck
Thanks for the suggestions guys! Iguess time is just what it needed. I actually fell asleep after trying for so long, and when I woke up I decided to try once more and VOILA... It let me into download mode! Went back to stock and have since been rebuilding . ha! Thanks again

Categories

Resources