So today I finally took the leap and flashed my phone (I've had it since it launched). I flashed it with Axura 2.2 and everything went great. I was playing around with it for a few hours, then I got greedy and decided to add the Voodoo lag fix, and this is where things got messed up. Basically, it didn't take, i got a female robot voice telling me I didn't have enough space available. So after that the phone was still working as normal, but I lost all my info saved in the internal memory and the phone started acting weird and wasn't booting up properly. So I did some reading and came to the conclusion that i should go back to stock and start all over again.
That's where I'm stuck right now. I'm trying to use Odin to restore to stock, I downloaded all the necessary files, and entered them into the proper fields in Odin. But, when I connect the phone (In downloading mode) it doesn't say [com7] in Odin like it's supposed to, it says [com3] instead.
And that's where I'm stuck at. Any idea where I screwed up and how to unscrew it up? Thanks....
Redo it com can be anything a long as it connects and stays connected you did it right from what I understand
Nerov3 voodoo
Hotstuff5964 said:
So today I finally took the leap and flashed my phone (I've had it since it launched). I flashed it with Axura 2.2 and everything went great. I was playing around with it for a few hours, then I got greedy and decided to add the Voodoo lag fix, and this is where things got messed up. Basically, it didn't take, i got a female robot voice telling me I didn't have enough space available. So after that the phone was still working as normal, but I lost all my info saved in the internal memory and the phone started acting weird and wasn't booting up properly. So I did some reading and came to the conclusion that i should go back to stock and start all over again.
That's where I'm stuck right now. I'm trying to use Odin to restore to stock, I downloaded all the necessary files, and entered them into the proper fields in Odin. But, when I connect the phone (In downloading mode) it doesn't say [com7] in Odin like it's supposed to, it says [com3] instead.
And that's where I'm stuck at. Any idea where I screwed up and how to unscrew it up? Thanks....
Click to expand...
Click to collapse
Any com is fine mine mostly shows 3 but once in a, while 5
No worries its the same
Sent from my SGH-T959 using XDA App
voodoo has been giving my phone issues as well. argh!
Anyway, like xrider said, I believe any COM is fine.
Odin won't do anything for me with [com3]
I actually got it go to [com4] earlier, Odin did it's job and completed. Once I rebooted the phone, it still wasn't right. It opened up to that screen where you use the volume buttons to move, then press power to enter, like if it was still rooted. I clicked on reboot and it started back up like normal. So I was getting ready to flash axura again, I downlaoded OCLF, titanium, and rom manager again. But when I clicked on the OCLF app, EVERYTHNG was unavailable. So I figured I would try and restore to stock again. And, now I'm stuck there again. I'm getting the [com3] thing again, the phone is in downloading mode of course, but now, i have some red letters on top of the screen that say, "keypressed, 164"
:\
I'll give you my two cents since I had to learn about ODIN the hard way earlier this week. It doesn't matter what com port it shows (mine showed com1 I think, but never 3 or 7). I know you said you were going back to stock, but does that mean your are going back to JFD, or something else? Do you have the 512 pit and the right tar file? Are you repartitioning or not? I certainly don't have all the answers, but it's still a little too fresh in my head to forget. Also once you get back to root, I would highly recommend Nero v3 (I don't run Voodoo. Haven't really understood the advantages/disadvantages, plus it seems like it could be over my head), it's a really great ROM and some of the new mods are starting to come out.....
I was gonna post up some pics of what I'm looking at, but I cant because I don't have enough posts yet! Guess I better whor3 it up!
gtiryan said:
I'll give you my two cents since I had to learn about ODIN the hard way earlier this week. It doesn't matter what com port it shows (mine showed com1 I think, but never 3 or 7). I know you said you were going back to stock, but does that mean your are going back to JFD, or something else? Do you have the 512 pit and the right tar file? Are you repartitioning or not? I certainly don't have all the answers, but it's still a little too fresh in my head to forget. Also once you get back to root, I would highly recommend Nero v3 (I don't run Voodoo. Haven't really understood the advantages/disadvantages, plus it seems like it could be over my head), it's a really great ROM and some of the new mods are starting to come out.....
Click to expand...
Click to collapse
I don't even know what JFD is When i said stock I meant to well.... stock, like out of the box. I think I have all the right files, I got them off a post here on XDA. As far as repartitioning, I've read to do it, and not to do it, so I've tried it both ways. I might give that Nero v3 a chance. I was really impressed with Axura 2.2. But like I said, I got greedy and added Voodoo-doo
Well I figured out part of my problem, I was using an outdated version of Odin. I was using 1.0, I upgraded to 1.7 and it worked and reset my phone. The only problem I'm still having is, the phone feels like it's still rooted. Do I have to manually unroot it, to get it back to normal? Also, when I open the OCLF app, NOTHING is available to chose from, everything is in red. And lastly, when I hook it up to my pc, it doesn't show up in my computer.
Hotstuff5964 said:
Well I figured out part of my problem, I was using an outdated version of Odin. I was using 1.0, I upgraded to 1.7 and it worked and reset my phone. The only problem I'm still having is, the phone feels like it's still rooted. Do I have to manually unroot it, to get it back to normal? Also, when I open the OCLF app, NOTHING is available to chose from, everything is in red. And lastly, when I hook it up to my pc, it doesn't show up in my computer.
Click to expand...
Click to collapse
How does the phone feel like its still rooted? If its still rooted you should see the superuser app in the drawer or you can d/l the terminal emulator app from the market and type su. SU will tell you if you have root or not. Aslo try a diffrent usb port on your pc, that happens to me once and a while.
badaphooko01 said:
How does the phone feel like its still rooted? If its still rooted you should see the superuser app in the drawer or you can d/l the terminal emulator app from the market and type su. SU will tell you if you have root or not. Aslo try a diffrent usb port on your pc, that happens to me once and a while.
Click to expand...
Click to collapse
Ok, I was making a mistake, it wasn't rooted after the reboot. It's just something doesn't feel right.
I restored with Odin again, so that's all good. I want to try out Nero v3 this time, like was suggested earlier, the problem I'm having now is, I'm having a hard time downloading from the market. I'm trying to download ROM Manager from the market, but it just says "starting download" and nothing ever happens.
Back in business! Flashed it to Nero v3, this is thing is FAST baby!
Yeah buddy!
Related
I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
buggzero said:
I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
Click to expand...
Click to collapse
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
buggzero said:
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
Click to expand...
Click to collapse
Your welcome and yes, you're completely back to stock and everything is gone. So you should be set. No, both methods work well and do the same. I know adb but still prefer the first method, works all the time is something goes wrong with voodoo or any lagfix.
I wouldn't say it's preferred to prevent those issues because you may still have them either way but its nice to have. You can make a backup with it so if anything goes wrong you have something to fall back on. Just makes things simpler.
Sent from my SGH-T959 using XDA App
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
buggzero said:
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's simple to disable voodoo. When you have voodoo installed you should have a voodoo folder in your internal SD card, if you don't them make one. Put a file called disable-lagfix in there with no extensions. A blank file with that name. Reboot and you'll hear the.process going through of removing voodoo. Then you can flash what ever you like without any problems. If you want voodoo back delete the disable-lagfix file or rename it to enable-lagfix. Simple.
Sent from my SGH-T959 using XDA App
thx for ur sharing...
i hv the same problem, it's fixed now...
Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
I flashed a few different ROMs, but suddenly the SIM card isn't capturing any signal. I tried the SIM card on an old phone and it works fine. Is there something I can do without buying a new SIM reader for it?
Hm, what different ROMs have you flashed? Have you tried going back to stock via ODIN?
I have a suspicion that you flashed a ROM build that has an issue with losing baseband/imei. Please list the ROM and build date that caused the issue.
Sent from my SGH-T959 using xda premium
If it is not an IMEI issue, try flashing a modem in recovery.
Here's the story. Some of the ROMs I flashed were ICS Passion, ICZen, and Doc’s Master ICS V12.1 (KB5) and I didn't like it so I flashed back to ICZen or Passion. One of them messed up the signal, but I don't remember which one. Anyway, I tried RemICS-JB after that, but it still did not have any signal, so I figured I flashed back to stock. However, after starting Odin it didn't progress for awhile so I exited the program. Then I resetted the phone and suddenly it was in a mode that that looked like this "Mobile .../ ! \...Computer" I found out that it was either soft-bricked or hard-bricked. Seeing as how I couldn't go into download mode with 3 buttons nor adb method, I decided that to have to make a jig. Then suddenly after trying this method for a bit,
http://forum.xda-developers.com/showthread.php?t=775911&highlight=usb+jig
I was able to start Odin and still have repartition ticked since I read that it would cause problems, but it didn't this time. The strange thing was that I was never in the original download mode(android with shovel). My screen still looked like this "Mobile .../ ! \...Computer" until I saw a blue dot at the bottom which happened to be the progress bar when I just clicked the START button on Odin after adding the PIT and PDA. On the other hand, I right-clicked and ran as administrator in Windows 7, so maybe that had something to do with it. Anyway, I'm glad it was able to flash it back to stock and the signal is back. I just have to root it again and flash ICZen or something. Let's hope it doesn't happen again haha.
FC3SRedSuns said:
Here's the story. Some of the ROMs I flashed were ICS Passion, ICZen, and Doc’s Master ICS V12.1 (KB5) and I didn't like it so I flashed back to ICZen or Passion. One of them messed up the signal, but I don't remember which one. Anyway, I tried RemICS-JB after that, but it still did not have any signal, so I figured I flashed back to stock. However, after starting Odin it didn't progress for awhile so I exited the program. Then I resetted the phone and suddenly it was in a mode that that looked like this "Mobile .../ ! \...Computer" I found out that it was either soft-bricked or hard-bricked. Seeing as how I couldn't go into download mode with 3 buttons nor adb method, I decided that to have to make a jig. Then suddenly after trying this method for a bit,
http://forum.xda-developers.com/showthread.php?t=775911&highlight=usb+jig
I was able to start Odin and still have repartition ticked since I read that it would cause problems, but it didn't this time. The strange thing was that I was never in the original download mode(android with shovel). My screen still looked like this "Mobile .../ ! \...Computer" until I saw a blue dot at the bottom which happened to be the progress bar when I just clicked the START button on Odin after adding the PIT and PDA. On the other hand, I right-clicked and ran as administrator in Windows 7, so maybe that had something to do with it. Anyway, I'm glad it was able to flash it back to stock and the signal is back. I just have to root it again and flash ICZen or something. Let's hope it doesn't happen again haha.
Click to expand...
Click to collapse
Always run Odin with administrator privileges. I'm not sure if that's what cause your troubles but it's always good practice.
Remics JB will cause loss of baseband. This has happened from time to time with some ROMs. If it happens again, just Odin back to stock to fix. You had a soft brick, good job on recovering it!
Sent from my SGH-T959 using xda premium