[Q] Soft bricked vibrant-going in circles for a week - Vibrant Q&A, Help & Troubleshooting

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.

Related

[Q] shed a little (up to date) light on my nightmare of a new phone.

O.K. So my baby (HTC Dinc) was lost in a bunch of snow. I was running android 2.2 with scence UI 2.0 and never had any trouble finding new and exciting roms that were just a lot of fun to play with. So after doing little homwork and having the Verizon guy talk up this Samsung I made my next $200 plunge into my new favorite hobby. However I was not aware that this phones hacking community was so... confusing. So heres where im sitting I ran FascinateRoot_v02 which is a 1 click root and boom i get Superuser. Completely psyched to get a rom on that isn't plagued by Verizon advertisements and Bing Bull$#!t, alas i am stuck. rom manager went in and installed ClockworkMod 3.0.0.8 as its recovery. I download the SuperDark1.1-D101 and go to install it through ROM manager and nothing happens. then i realized that i must not have the right recovery. I am lost and hating the frustrations that are fallowing the events that led to me getting this phone. I know the hardware is good and all but Big Red and Bing (WTF is this doing on a google OS Phone) have turned the wonderful SuperAMOLED screen into an eyesore.
Here's what I need.
1.) someone to post what the OTA update did to my phone. (USB not recognized by PC)
2.) Someone to explain in very small words how to ROM this phone with the latest info.
3.) Someone to explain What VOODOO and NoN-VOODOO Kernels are and the benefits of both
4.)How to install the kernels
5.) Anything that i can do to help with 2.2 because running with limited/no flash makes me feel like im playing with an iphone original with a shiny new screen.
I'm very sorry for making a new thread that i am sure has questions that have been asked before on it, but for two days i have been lost on this. Please help a guy out!!!
Droidneedzsence said:
O.K. So my baby (HTC Dinc) was lost in a bunch of snow. I was running android 2.2 with scence UI 2.0 and never had any trouble finding new and exciting roms that were just a lot of fun to play with. So after doing little homwork and having the Verizon guy talk up this Samsung I made my next $200 plunge into my new favorite hobby. However I was not aware that this phones hacking community was so... confusing. So heres where im sitting I ran FascinateRoot_v02 which is a 1 click root and boom i get Superuser. Completely psyched to get a rom on that isn't plagued by Verizon advertisements and Bing Bull$#!t, alas i am stuck. rom manager went in and installed ClockworkMod 3.0.0.8 as its recovery. I download the SuperDark1.1-D101 and go to install it through ROM manager and nothing happens. then i realized that i must not have the right recovery. I am lost and hating the frustrations that are fallowing the events that led to me getting this phone. I know the hardware is good and all but Big Red and Bing (WTF is this doing on a google OS Phone) have turned the wonderful SuperAMOLED screen into an eyesore.
Here's what I need.
1.) someone to post what the OTA update did to my phone. (USB not recognized by PC)
2.) Someone to explain in very small words how to ROM this phone with the latest info.
3.) Someone to explain What VOODOO and NoN-VOODOO Kernels are and the benefits of both
4.)How to install the kernels
5.) Anything that i can do to help with 2.2 because running with limited/no flash makes me feel like im playing with an iphone original with a shiny new screen.
I'm very sorry for making a new thread that i am sure has questions that have been asked before on it, but for two days i have been lost on this. Please help a guy out!!!
Click to expand...
Click to collapse
Your mistake was a simple one, you simply used the wrong Clockwork Recovery, the ORANGE. Most of our ROMS are not compatible with that. You need the RED Clockwork Recovery 2.x.x, if you do some searching it is all over here. Your OTA update I have no clue about because you didn't even mention it in the original post except to ask what it did. If USB isn't recognizing, reinstall the Samsung drivers, and try toggling USB debugging. You are now NON-Voodoo, your file system is stock RFS, which is slow. What Voodoo does is change your filing system to EXT4, which is must faster. This does not mean your phone will be blazing through everything. It simply means that your phone will be much faster at writing data, I have not seen one person disappointed per se in it yet, I personally use it. Overall, it will increase the performance of your phone. Kernels, you flash using the RED Clockwork Recovery, which you will find downloads of and instructions for all over this forum, it is very easy. Once you get the correct Clockwork Recovery this will be easy man, so go get that, and flash a ROM like you normally would. Have any more questions, you can reply, or IM me. EDIT: Also, get a program called Odin, which is all over this forum as well. As you read more and more, and do more things, you will see why it is very useful.
Thanks! 1 problem... I cant set it back using rom manager. How else can you fix/downgrade to 2.x.x. Also the OTA update has my phone hidden on my pc through USB conectivity and I have never used Odin. I really do appreciate the help! I hate trying to learn new setups in 2 days
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
Droidneedzsence said:
Thanks! 1 problem... I cant set it back using rom manager. How else can you fix/downgrade to 2.x.x. Also the OTA update has my phone hidden on my pc through USB conectivity and I have never used Odin. I really do appreciate the help! I hate trying to learn new setups in 2 days
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Okay, here is Odin, attached at the bottom of my post. I am also including Clockwork Recovery, the one you need, as well as the update.zip. First you need to place Update.zip on your SDCARD. Since your pc won't recognize your phone, you can use the Dropbox program to do this. Update.zip HAS to be on the root of your SDCARD. Now, Odin is the program you want to use to Flash the cwm.tar, okay? And ONLY that .tar. Open Odin and mess with NONE of the settings, NONE. Click the PDA Button, choose cwm.tar and then click on START. Note: In the upper left hand corner, if Odin detects your phone, it will be yellow. And make sure USB debugging is enabled. So, flash cwm.tar to your phone, boot into recovery by holding BOTH of the volume keys while powering up, then in Clockwork Recovery select "Install Update.zip", it will install and you will have the RED Clockwork Recovery. THEN you go flash your ROMS and such, as for your USB problems, could be very simple, just do some Googling. Oh, and in terms of ROMS? I HIGHLY recommend Adrynalyne's SuperClean.
One thing to note since you have been having problems, and because I didn't see it mentioned above.
For odin to work (for odin to see your phone) you need to have it (your phone) in download mode.
This is made possible by pulling the battery, plugging in the phone to your PC via the STOCK usb cable (I have read non OEM cables can cause problems), and holding down the "down" button on the volume rocker while holding the power button. You should boot into download mode. Yellow Triangle as some call it...because of the giant yellow triangle on-screen....
I had a hell of a time figuring this out through the guides but once you figure it out you will have no problems.
gkirby11 said:
One thing to note since you have been having problems, and because I didn't see it mentioned above.
For odin to work (for odin to see your phone) you need to have it (your phone) in download mode.
This is made possible by pulling the battery, plugging in the phone to your PC via the STOCK usb cable (I have read non OEM cables can cause problems), and holding down the "down" button on the volume rocker while holding the power button. You should boot into download mode. Yellow Triangle as some call it...because of the giant yellow triangle on-screen....
I had a hell of a time figuring this out through the guides but once you figure it out you will have no problems.
Click to expand...
Click to collapse
I KNEW I forgot something, thank you for adding that. I have so much going on but did not want to leave the guy hanging I rushed through the explanation.
There were some issues with the "stock" versions of CWM, and our devs have touched it up to work with our phones better. The latest "Orange" version you installed from Rom Manager uses a new method for installing updates/ROMs (Edify script). Almost all of the things available on these forums are still set up for the old method of installing updates/ROMs (Amend script). As a general rule of thumb, we don't update CWM through Rom Manager, and just use versions posted here. There were some compatibility improvements, but they also added Voodoo support and options.
Also, because of not using Rom Manager to update CWM, the "Install from SD Card" option in Rom Manager doesn't work. There's some kind of "*update.zip" in the clockwork folder on your SD card. If you copy the update.zip from the root of your SD card into the correct folder and rename it, the "Install from SD Card" might work. Sorry, I don't use Rom Manager anymore, so I don't have the exact names or folders.
The way a lot of people handle ROM installs is to reboot into recovery (hold volume up and volume down and power while starting up, and release only the power button when "Samsung" appears). Once you install the cwm.tar that Dread This Day posted, this method will take you straight into Clockwork Recovery. You can download ROMs from Rom Manager or directly from these forums.
Just a word of caution on Voodoo. There are some serious problems you can get yourself into if you don't know what you're doing with it. I strongly suggest you thoroughly research exactly what it does, the impacts of installing/using it, and how to properly remove it before you decide to use it.
Thanks for the info and the walkthrough. Gotta love expediant info. Ill be playing with it after I get off work. I have been using the micro usb from my Dinc so ill swap it out and see if it works.
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
all i get from that is samsung recovery utils. lookin over the net and tried the whole emulator trick. this phone is aggravating I know its probably just me. So im going to run some tests to find out if i can get into the download mode via an cmd prompt or some such program.
In other news I FOUND MY Dinc! after a weekend of being in the snow a co-worker spoted a lighter and went to get it, at which point he found the phone under it. great news is that my case and screen protector saved it. no water damage, not even a red seal!
Edit:
The program is called terminal emulator not cmd prompt. sorry for the platform crossover.
In emulator
type in #su
agree to superuser
type in #reboot download
and done. i knew that computer class would pay off. lol next step is getting phone recognized by odin. more fun awaits...
abondon ship. htc thunderbolt is out in the next 3 weeks and im gonna be all over it. as my name infers deoid needs sense and samsung... well it has none and oit of the 5 phones ive rooted and romed this is by far the most anoying. ota updates that make a phone unrecognizable via pc and the need to run multiple programs just to get a phone to except root. no froyo in sight and... bing... they ruined a great phone by pretty much leaving it up to our devs to make it worth something. i shall miss my superamoled but not enough to birn an upgrade. thanks for the help, you guys are great, hope to see ya in the htc scene soon.
Sent from my SCH-I500 using the XDA mobile application powered by Tapatalk
In my opinion ROM Manager blows goats your better off downloading from xda and flashing in the orange clockwork
Sent from my SCH-I500 using XDA App
WhiteRocks said:
In my opinion ROM Manager blows goats your better off downloading from xda and flashing in the orange clockwork
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Most of the ROMs for the Fascinate won't work with orange clockworks. You will need the red version.
Sent from my SCH-I500 using XDA App
Sense really blows dude, I would cut my hand off before going back to buggy htc, 2.2 fascinate is way better, but to each his own...
Sent from my SCH-I500 using XDA App

[Q]Fascinate Paperweight?!?

Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
dssheeley1 said:
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
Click to expand...
Click to collapse
In the op of ics and also droidstyles guide you have to flash build 1 before you can flash build 5
Sent from my SCH-I500 using XDA App
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
I bootlooped when i went from stock EH03 to Build 5 so i did 3 first then 5.
But this doesn't help our poster here.
OP:
you get into DL mode but odin wont see your phone?
What i suggest is to try: Move the usb cable to a different port. see if your pc can see it then. Second thing try a totally different computer. Chances are your PC is trying to use borked up drivers.
Once you get odin going flash a stock image [i recommend eh03] then cwm then build 3 and now the new build 6. good luck!
if you need any links or a more detailed guide I STRONGLY suggest Droidstyles guild, it is by far the best and most up to date for the fassy!
OhioYJ said:
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
Click to expand...
Click to collapse
Consider yourself lucky....going from stock to build 6 causes me problems and many others. Going from stock, to build 1, then build 6 works flawless.
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
dssheeley1 said:
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
Click to expand...
Click to collapse
You realised you just bring a a old thread back yourself and no longer support of this model wtf you realise people.still use this phone everyday Right?
Sent from my SCH-I500 using Tapatalk 2

[Q] Am I bricked?

I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.

Need help doing a stock upgrade to 2.2 without Mini Kies

A friend just gave me a SGH-T959 Galaxy S Vibrant. It still has the stock 2.1 on it. I'd like to upgrade it to CM7 or maybe CM9, but all the instructions I've found say you should at least be on 2.2. I've been trying for several days to upgrade to 2.2 using Mini Kies. It downloads the rom (not sure where it stores it on my machine), reboots the phone in download mode and just sits. I left it for hours several times and nothing. If I reboot it it is fine when I reboot. It is just never copying anything to the device.
Is there a way to do the update without Mini Kies. I should also mention that my machine is a MacBook Pro running lion. I've tried this on a Windows XP VM in VMWare Fusion and I get the same exact results, it goes to download mode and then nothing.
xltrigger said:
A friend just gave me a SGH-T959 Galaxy S Vibrant. It still has the stock 2.1 on it. I'd like to upgrade it to CM7 or maybe CM9, but all the instructions I've found say you should at least be on 2.2. I've been trying for several days to upgrade to 2.2 using Mini Kies. It downloads the rom (not sure where it stores it on my machine), reboots the phone in download mode and just sits. I left it for hours several times and nothing. If I reboot it it is fine when I reboot. It is just never copying anything to the device.
Is there a way to do the update without Mini Kies. I should also mention that my machine is a MacBook Pro running lion. I've tried this on a Windows XP VM in VMWare Fusion and I get the same exact results, it goes to download mode and then nothing.
Click to expand...
Click to collapse
Whoops, mix up, JFD is 2.1 Eclair. You can still flash CM7 without 2.2, just follow this guide:
http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
After flashing the kernel via heimdall, if it never boots, just wait a few minutes and pull the battery, then boot into recovery by VOL-UP + VOL-DOWN + Power, then continue.
Just flashed the zImage. I'm waiting for boot. The talking updates on time remaining are kewl. Thanks for you help. Hopefully all works well.
Is CM9 stable enough to run ok, or should I stick to CM7.2?
xltrigger said:
Is CM9 stable enough to run ok, or should I stick to CM7.2?
Click to expand...
Click to collapse
CM9's okay. I run it. But both CM7 and CM9 may still have intermittent issues with 911 calling. There are two people who can't call period (they _may_ have a corrupted /efs which would prevent them from calling even on stock now, but not sure). Some who failed and then worked, etc, etc.
Looks like I may have screwed myself. It won't boot after the zImage. I can boot CWM, but I can't do a USB mount in CWM. I can enter the menu, but it never shows up. If I had copied CM and GAPPS before the zImage I'd likely been ok. I tried putting the zip files on external MicroSD, but CWM offers me no way that I can see to apply a zip from that. It only sees the internal.
If you have any suggestions on where to go from here please let me know.
Update:
Even though I couldn't get into the device when booting normally, I was able to get connect using adb.
I did "adb push cm-9-20120707-NIGHTLY-vibrantmtd.zip /sdcard/" and was able to copy the update to my phone.
I did the same for gapps. So far so good. I'll update this post again when all is finished.
Update 2:
I've got CM9 installed and booted. Downloading my apps now. Thank you so much for your help /me is really happy now
If its your 1st time on ICS with the T959 I suggest reading this:
http://forum.xda-developers.com/showthread.php?t=1464423

Q: blank screen after T-Mo splash animation, possible to fix without wiping?

Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737

Categories

Resources