Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
Hello All!
My first post here, even though I have long been a lurker. I hope I'm posting in the right place. If not, apologies, and Mods - please redirect me, and I shall re-post in the correct place.
Phone: SAMSUNG GALAXY S3 GT-I9300 International version
Last known installed/running OS: Official SAMSUNG JB ROM (Unsure WHICH version) after having run on CM 4.4 for a couple of weeks.
PROBLEM:
a few months after going back to stock, Phone suddenly developed issues of random reboots. These would happen at any point in time, with no predictability whatsoever. One fine day, it rebooted, and wouldn't get past the Samsung splash screen. Pulling the battery and trying to restart phone resulted in the same stuck at Samsung logo issue.
Left the phone alone for a couple of months after this as I had a spare, but finally decided to try and revive the S3.
Phone does not charge when connected to charger. At least, it shows no visible signs of it. It DOES, however, try booting itself when plugged in, but gets stuck on the first screen of ODIN Download mode, instead of the Samsung logo splash screen as it used to earlier. Also note that this screen it gets stuck on is a pixellated screen, not the clear normally seen screen when entering ODIN mode.
The Vol UP, Home and power button combo brings me to this very same screen, there is no recovery menu to be seen, as would be normally. The Vol DOWN, Home and power button combo brings me to the regular clear ODIN mode as usual.
The headings at this screen read:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I have read through most posts regarding similar issues on XDA as well as other forums, and tried flashing stock firmwares (single AND multiple part ones) through ODIN, with no success. The error i always get is as in the attached screen captures.
I've tried ALL versions of ODIN, and many PIT files. All were failures.
So, is this a dead for all purposes phone, or do I still have hope since ODIN mode is still available?
I don't think USB debugging was checked before bricking, because ADB toolkits just keep waiting for phone to be detected.
All drivers are up to date and installed correctly. Kies is not installed.
Any help is welcome.
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
I have a Device here which seems to have the same or at least a similar problem, however, i got it for free from someone else to experiment with, so there is no urgent need to repeir it.
I tried flashing a pit and erasing nand, but when i start to do it, odin just gets stuck at "erasing", if i try to flash a full firmware it just hangs at "getting pit for mapping" so i assume the nand is gone for good... however, i have one more dead s3 arround that seems to have a burned cpu, probably i manage to solder over the nand or the cpu
rp158 said:
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
Click to expand...
Click to collapse
ODIN stays at "Setup Connection" without any progress. I've left it overnight a few times, just to ensure I was giving it enough time.
When the cable is pulled, it reads "there is no pit partition"
@Mohanms04: I suppose, it's hardbricked
rp158 said:
@Mohanms04: I suppose, it's hardbricked
Click to expand...
Click to collapse
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Mohanms04 said:
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Click to expand...
Click to collapse
Try this recovery firmware, if not the jtag is required.
http://forum.xda-developers.com/showpost.php?p=30087735
I switched to samsung from apple and i stupidly tried to flash some firmware without really knowing what i was getting into. I ended up getting my phone stuck on the ATT logo and only being able to get there and download mode, cant even turn it off.
I've googled, tried everything i can find, and used all sorts of combinations to no avail. I've gotten to the point that when the phone boots up, it shows the android man and says "no command". WHen i try and go into recovery mode from there it tells me that i dont have a recovery mode.
From what i've read the best step is to flash stock rom but i cant seem to get anything to work, and although i've been messing with this for a grand total of(probably over) 24 hours, im still as lost as i was in the beginning.
I've got Prince Comsey, Odin3 V3.12.3, Odin3 V3.12.7
With firmwares that APs are
AP_G955USQS3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT_meta.tar.md5
AP_G955USQS5CRI4_CL13889051_QB19733321_REV01_user_low_ship_MULTI_CERT_meta.tar
AP_G955U1UEU5CRJ2_CL13889051_QB20199591_REV01_user_low_ship_MULTI_CERT_meta.tar
AP_G955USQU1AQC9_CL10895874_QB12856072_REV00_user_low_ship_MULTI_CERT_meta.tar
I've done the trick of, when starting the flash, rebooting the phone back into download and starting again. Which actually let odin flash some software(which is how i am now at the android "update" screen) but that was all it did.
Some software give me "Fail (Auth)"
Some say "complete write fail"
But none have worked.
EDIT: to add; I've eddited the configuration settings for all odins to be able to use the "UMS" option for the "USERDATA" file, which seemed to help odin but nonetheless still didnt fully help me.
Someone please help me get my phone working again. WHat else can i do?
Please also, if you have a solution or question, explain what you mean or need in detail because as i said i am very new to android