i've read almost every single post related on this subject, tried almost everything but no go.
recently, i installed SS-6 to my girlfriend's Vibrant but she didn't like it, so i attempted to revert to my nandroid from the original stock rom.. nandroid gave an MD5 error and did not installed.
at that point, i had already wiped data/cache, prior to nandroid.
i rebooted the phone, and now im stuck on the Vibrant splash.
i have tried to go to recovery mode via hard buttons but no go. i actually tested with another Vibrant and on that one, im able to get into recovery so it is not that i'm missing pressing a button or what not. been trying anxiously to see if im able to go either to download mode or get into cwm and flash cyanogenmod!
tried to use ODIN/ADB in order to boot into cwm to flash another rom, but it doesn't see the phone. ive already installed samsung drivers.
if i connect the charger, the battery indicator doesnt come up. it stays on that lined-circle screen forever, even after taking the USB cable out.
please help!
EDIT: added [Q] and added some more grammar errors.
any help is highly appreciated.
I had this same problem... The only thing that would fix it was this thing I had to buy called a Jig. It was less than $8 (with free shipping) on eBay.
http://www.ebay.com/itm/Fix-Download-Mode-USB-Jig-Samsung-Captivate-Galaxy-S-/140520601309
It delivered in 2 days and my phone is working perfectly now
just ordered one!
thanks!
one more thing, are you able to just install a different ROM through ODIN or ADB without having to do the full wipe? im wanting to save the contents of the internal SD.
thanks again
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.
I installed Chainfire3D (after hearing good things about it) and then realized the problems it causes, so i deleted the app and then its CF3D drivers from system/lib which didnt work properly anyways. Upon restart device doesnt boot anymore :crying: (welI maybe its on cause the battery generates heat, but its black screen) I also couldnt get titanium backup to work in the past just in case something like this happens cause it was constantly stuck on yahoo finance when backing up.
My main issue is I had alot of things (worth a couple days) installed on my phone, and dont want to lose all of it. Bad thing i didnt realize there is Nanadroid backup (cause its my first android phone) which works unlike titanium quickly and efficiently, but backing things up now after black screen is pointless no? i can acess CWM recovery, but dont want to factory reset yet.
So any way to inject those stupid CF3D drivers via ADB? Or maybe backup everything but that certain system/lib folder?
Edit: i ran into this:
On CF-Root just boot into recovery, ADB shell to it, and type "rootsh" (instead of "su") to have root shell access... if anything goes wrong, just "mount /system" and "/system/lib/cf3d_uninstall.sh" to remove the CF3D driver and restore the old one. Not very likely it will happen, but a good fallback option in case of issues (no need to reflash firmware or restore backup)
Click to expand...
Click to collapse
, unfortunately cf3d_uninstall.sh was one of the files i deleted, but maybe if someone who has Chainfire3D installed on S3 LTE can share that file, i can then inject it and restore the old drivers?
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
white 16GB Tmoble GS3
Actually my current issue is similar, it boots up says galaxy S3 then black screen. I can connect to odin, i can boot into clockwork, and i can flash roms, ODIN says everything is successful after i flash but when it boots it still goes to a black screen. this happened after i flashed a rom(that worked) and flashing a kernel that also previously worked....after that its been stuck....i can flash whatever with success but i cannot seem to get it past that Galaxy S3 screen....
I flashed the new FreeGS3 rom, and the TGST STOCK ICS Alpha37 kernel i cleared caches and wiped davliks not too sure where to go from here.....Do i need factory tmoble GS3 PIT file?
Redsalamander said:
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
Click to expand...
Click to collapse
Not to offend anyone the Dev app said he wasn't going to support it for the galaxy s3
Sent from my SCH-I535 using xda premium
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Redsalamander said:
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Click to expand...
Click to collapse
Well thing is on my end...i didn't flash whatever the OP had flashed. What i DID do though is flash a rom and a kernel on the same cwm event. when it rebooted...it just does this....
i have a backup file....its on my laptop though....with only using odin or cwm how can i push that file onto my phone? My CWM doesnt have USB mount else id just do that.....?
I have the GT-S7560M through Solo (Bell) and I rooted it shortly after purchase last year. I've been happy with the phone and for the last few weeks an upgrade notice has been appearing but would fail when applied. Some searching suggested the root was interfering. At first I started to look into un-rooting the phone, but then thought that a factory reset would be the simplest, least-risky solution. I had done a factory reset on my last Galaxy phone without a problem so it seemed like a safe choice. I backed up the contact info, etc with Kies (I don't use many apps so I didn't go all out ie Titanium Backup) and removed my SD card.
Now the phone boots to screen asking me to pick a language and press Start. Then it moves on to a black screen with the info bar at the top (clock, cell strength, data xfer) and nothing else. It is auto-rotating. The phone does react to touches with the buttons lighting up, but I can't get anywhere. Kies can see the phone, the phone number, the firmware version and all that. It reports Internal Memory as 84.83MB used of 1.58GB. I can navigate through the phone using Windows Explorer. I did a Restore with Kies but it doesn't seem to have had any relevant effect.
I am able to boot into CWM Recovery. I don't remember doing a back-up with it, and when I ask it to restore from either the SD card or the interal SD it says it can't mount.
At this point I would start thinking about taking the phone back to the store, but a flash counter appears during start-up and I'd rather they didn't see that for obvious reasons.
When I google I just get people who have bricked their phones. I just want my phone to work again. I'm not worried about modifying it further to achieve that.
Yoqui said:
I have the GT-S7560M through Solo (Bell) and I rooted it shortly after purchase last year. I've been happy with the phone and for the last few weeks an upgrade notice has been appearing but would fail when applied. Some searching suggested the root was interfering. At first I started to look into un-rooting the phone, but then thought that a factory reset would be the simplest, least-risky solution. I had done a factory reset on my last Galaxy phone without a problem so it seemed like a safe choice. I backed up the contact info, etc with Kies (I don't use many apps so I didn't go all out ie Titanium Backup) and removed my SD card.
Now the phone boots to screen asking me to pick a language and press Start. Then it moves on to a black screen with the info bar at the top (clock, cell strength, data xfer) and nothing else. It is auto-rotating. The phone does react to touches with the buttons lighting up, but I can't get anywhere. Kies can see the phone, the phone number, the firmware version and all that. It reports Internal Memory as 84.83MB used of 1.58GB. I can navigate through the phone using Windows Explorer. I did a Restore with Kies but it doesn't seem to have had any relevant effect.
I am able to boot into CWM Recovery. I don't remember doing a back-up with it, and when I ask it to restore from either the SD card or the interal SD it says it can't mount.
At this point I would start thinking about taking the phone back to the store, but a flash counter appears during start-up and I'd rather they didn't see that for obvious reasons.
When I google I just get people who have bricked their phones. I just want my phone to work again. I'm not worried about modifying it further to achieve that.
Click to expand...
Click to collapse
You have posted in wrong section
BTW your solution is just flash stock Rom via ODIN , your problem will get solved.
BTW your solution is just flash stock Rom via ODIN , your problem will get solved.
Click to expand...
Click to collapse
I've just finished doing that, and it appears to have worked.
For anyone else with a similar problem who finds this thread:
- Go to the FAQ here: http://forum.xda-developers.com/showthread.php?p=45767157#post45767157
- Download Daver18qc's root kit at the link provided (you'll have to scroll down to the second post). You want this to get Odin; don't worry about the zip's other contents.
- Go here: http://www.sammobile.com/ and register. It's free and all it wants is an e-mail and your country.
- Go here: http://www.sammobile.com/firmwares/ and type s7560m in the search box. The list will automatically update. I'm a Solo customer and chose 'Canada (Bell Mobile)'. When I first tried this in Firefox I would get a screen telling me I wasn't logged in. I tried it in IE (which I never use and so is 'clean') and the download went through.
- Go back to the FAQ http://forum.xda-developers.com/showthread.php?p=45767157#post45767157 and scroll down to 'Short Tutorials' and 'How to Flash with Odin:'.
- One thing it leaves out is that when you boot into Download Mode, you will first get a warning screen that asks you to either press Volume Up to continue or Volume Down to abort and reboot. Not a big deal but it caught me off guard. Odin will not detect the phone until you get past this screen.
- Continue with the Tutorial. After it is done you will have to setup the phone again. But at least it's working now.
Recently, I flashed a TWRP and rooted my Tablet (Galaxy Tab A SM-T350). Yesterday, I made the mistake of installing crdroid (https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517) and wiping the recommended partitions (In that post). After confirming that the custom ROM worked, I went back into TWRP to install the Google Apps and SuperSU. That's when I screwed up.
After installing those .zips I went back into crdroid, and the "Weather Pro" or something like that, which appeared to be the launcher, kept crashing.
Regretting my choices and wanting to go back to stock, I flashed this ROM with ODIN: https://androidfilehost.com/?w=files&flid=154234
That didn't seem to work, as when it booted into the setup, it would crash and reboot. I thought I had flashed the wrong version of Android on it, and downloaded this ROM: https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T350/XAC/download/T350XXU1CQJ5/194035/
That also didn't seem to work, as the device would do the same thing. Boot to setup and crash. I tried to boot into ASR and wipe it from there, which is what landed me where I am now:
The device booted, went into setup and immediately shut down. The device does not boot at all, and when plugged in, simply shows the circle with the bolt inside, never showing the green circle and the battery percentage.
Quick FYI: I backed up everything with ADB to my PC way before this happened. Don't know if that will help.
What I mean: https://1drv.ms/v/s!AnXXk5PX0LXn3gd4nJiaPXYOKhFv
Anyone know where to begin in terms of resurrecting my tablet?
Thanks in advance
UPDATE: I don't know what happened, but the device is not charging. Still refuses to boot without crashing but I feel like this could help
Update 2: Ok so it turns out I was stupid and the battery was just dead (I thought it was charged after a night-long charging, but I guess not)