What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App
jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.
Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.
I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.
I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10
How do you know whether you have a hardware locked Vibrant or not?
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk
Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?
Related
So basically I rooted my vibrant, and realized it was hardware locked, as in recovery/download key combinations don't work.
I installed clockwork Mod recovery and backed up my system using the backup function. I then proceeded to flash the "Obsidian V2 - JK2 Official Froyo Based 2.2 - Team Whiskey" rom.
When that was done, I think I made a mistake by restoring the backup before restarting the phone before the first boot. Therefore, I am now stuck on the Vibrant/Samsung first boot screen.
I've researched a bit on how to get the phone into download/recovery mode on hardware locked models and none of the methods I found worked. A friend told me that apparently there was a method by using heat and a soldering iron....but if possible I want to avoid that unless its the last thing I can do to restore it.
Extra Info:
I had ADB turned off on phone before flashing ROM
It is samsung Vibrant Tmobile version, not Bell, and its hardware locked.
What I think the cause of the problem was that I restored a backup from 2.1 immediately flashing the v2.2 rom. Maybe I should have booted first into the new rom before trying to restore any backups...
When I plug my phone into the computer it starts charging (Battery icon with amount and animation of dots works)
I've tried using Droidexplorer as well but it doesn't detect my device.
My device makes the connection sound when connected to windows.
So hopefully, if you have any ideas for how this can be fixed with ODIN or how to get the phone back to the stock ROM, or even how I can force my phone into recovery or download mode without using a soldering iron then that would be extremely helpful. Thanks in advance
just happened to me too. Please help!
I figured it out.
Its because I flashed a backup which was a 2.1 image when I had a 2.2 kernel installed. And that = death.
The soldering method isn't that bad, so i fixed the problem.
That`s what happened to me too. But i just recovered my wife`s phone. While holding volume keys i pluged usb and voila, got into download mode. That means it`s not fully bricked. Then just did the odin recovery and the phone is back to life.
Thanks to all the devs in this forum.
Unfortunately, that method wont work for hardware locked phones, so the soldering jig is the only possible way to force the vibrant into download mode if its hardware locked.
You can still get to download mode using adb even if the phone won't fully boot.
Sent from my SGH-T959 using XDA App
Possible, but if ADB on the phone itself was turned off before the soft brick would it still be possible?
Zeltex said:
So basically I rooted my vibrant, and realized it was hardware locked, as in recovery/download key combinations don't work.
I installed clockwork Mod recovery and backed up my system using the backup function. I then proceeded to flash the "Obsidian V2 - JK2 Official Froyo Based 2.2 - Team Whiskey" rom.
When that was done, I think I made a mistake by restoring the backup before restarting the phone before the first boot. Therefore, I am now stuck on the Vibrant/Samsung first boot screen.
I've researched a bit on how to get the phone into download/recovery mode on hardware locked models and none of the methods I found worked. A friend told me that apparently there was a method by using heat and a soldering iron....but if possible I want to avoid that unless its the last thing I can do to restore it.
Extra Info:
I had ADB turned off on phone before flashing ROM
It is samsung Vibrant Tmobile version, not Bell, and its hardware locked.
What I think the cause of the problem was that I restored a backup from 2.1 immediately flashing the v2.2 rom. Maybe I should have booted first into the new rom before trying to restore any backups...
When I plug my phone into the computer it starts charging (Battery icon with amount and animation of dots works)
I've tried using Droidexplorer as well but it doesn't detect my device.
My device makes the connection sound when connected to windows.
So hopefully, if you have any ideas for how this can be fixed with ODIN or how to get the phone back to the stock ROM, or even how I can force my phone into recovery or download mode without using a soldering iron then that would be extremely helpful. Thanks in advance
Click to expand...
Click to collapse
Just a suggestion:
1:Open ODIN
2:Connect USB cable to computer (not phone)
3:NOW, connect USB to phone
4ress POWER, VOL. UP, & VOL. DOWN at same time and HOLD (yes i read that ur hardware locked but just try )
5:Wait for first Vibrant logo to appear, and as SOON as it dissapears...release ONLY the POWER button. Keep hold on both volume buttons.
Uh sorry if this didnt work but atleast it was worth a try.
*words in caps are keypoints, im not angry
roguly said:
Just a suggestion:
1:Open ODIN
2:Connect USB cable to computer (not phone)
3:NOW, connect USB to phone
4ress POWER, VOL. UP, & VOL. DOWN at same time and HOLD (yes i read that ur hardware locked but just try )
5:Wait for first Vibrant logo to appear, and as SOON as it dissapears...release ONLY the POWER button. Keep hold on both volume buttons.
Uh sorry if this didnt work but atleast it was worth a try.
*words in caps are keypoints, im not angry
Click to expand...
Click to collapse
Doesn't work....it only keeps bringing up the battery charging screen and won't even boot to vibrant screen.
Zeltex said:
Possible, but if ADB on the phone itself was turned off before the soft brick would it still be possible?
Click to expand...
Click to collapse
That I'm not sure on, but worth a shot.
Sent from my SGH-T959 using XDA App
Can you please link me to an article on the soldering method? I couldn't find anything on google.
Well as I said earlier, I just did the soldering method and forced my hw locked vibrant into download mode and restored with Odin. Unless you modify your hardware or flash something special to get rid of the hardware lock, the volume/power key combinations don't work.
Edit:
gonintendo said:
Can you please link me to an article on the soldering method? I couldn't find anything on google.
Click to expand...
Click to collapse
Here's the guide. Its pretty hard to mess up so don't worry.
http://forum.xda-developers.com/showthread.php?t=819551
I have a question about using this method:
once boot the phone by odin, is the phone going back to a
fresh state or with all the saved contacts/apps backed up
with Titanium Backup?
I am having trouble to boot the phone when I tired to restore to 2.1 update1.
Rooted, backed up with TB, then flashed to Obsidian V4, Froyo 2.2.
Now I want to restore to 2.1 so that I can get all my contacts back.
Thanks for help.
roguly said:
Just a suggestion:
1:Open ODIN
2:Connect USB cable to computer (not phone)
3:NOW, connect USB to phone
4ress POWER, VOL. UP, & VOL. DOWN at same time and HOLD (yes i read that ur hardware locked but just try )
5:Wait for first Vibrant logo to appear, and as SOON as it dissapears...release ONLY the POWER button. Keep hold on both volume buttons.
Uh sorry if this didnt work but atleast it was worth a try.
*words in caps are keypoints, im not angry
Click to expand...
Click to collapse
Haven't seen this mentioned yet, but something that has worked for me many times is this:
-Take battery out
-connect phone to the power chord (best to do it while connected to the computer)
-hold both the volume up and down buttons at the same time
- insert the battery into the phone while still holding buttons
You should see download mode pop up and you're ok to release the buttons after that. Now you're free to odin it up.
villaparv said:
I have a question about using this method:
once boot the phone by odin, is the phone going back to a
fresh state or with all the saved contacts/apps backed up
with Titanium Backup?
I am having trouble to boot the phone when I tired to restore to 2.1 update1.
Rooted, backed up with TB, then flashed to Obsidian V4, Froyo 2.2.
Now I want to restore to 2.1 so that I can get all my contacts back.
Thanks for help.
Click to expand...
Click to collapse
By restoring with Odin, all your stuff will be wiped out, but think on the positive side, at least you don't have to carry a broken phone around with you all the time now. Unless you put your backups on the external SD card, not internal 16gb memory, then maybe take out the SD card before restoring.....
And as a precaution to those who don't want to end up in the same situation as me, don't use nandroid to backup and restore a 2.1 backup when you flashed a 2.2 rom.
2.2 roms will flash a 2.2 froyo kernel to your device and then the 2.1 backup will flash a 2.1 image to it, therefore causing your phone to brick.
-----------------------------------------------------------------------------
And again, no method by pressing the physical hardware keys will work on Hardware locked model vibrants. Even taking the battery out or plugging in the USB won't work as these functions have been "disabled" by the lock. I'm pretty sure the soldering method is the only effective way to force your phone back to download mode and to restore to factory conditions. I've spent at least 39882884385820384872 different combinations with the battery pulling, USB plugging, holding key combinations and they don't work.
Zeltex said:
So basically I rooted my vibrant, and realized it was hardware locked, as in recovery/download key combinations don't work.
I installed clockwork Mod recovery and backed up my system using the backup function. I then proceeded to flash the "Obsidian V2 - JK2 Official Froyo Based 2.2 - Team Whiskey" rom.
When that was done, I think I made a mistake by restoring the backup before restarting the phone before the first boot. Therefore, I am now stuck on the Vibrant/Samsung first boot screen.
I've researched a bit on how to get the phone into download/recovery mode on hardware locked models and none of the methods I found worked. A friend told me that apparently there was a method by using heat and a soldering iron....but if possible I want to avoid that unless its the last thing I can do to restore it.
Extra Info:
I had ADB turned off on phone before flashing ROM
It is samsung Vibrant Tmobile version, not Bell, and its hardware locked.
What I think the cause of the problem was that I restored a backup from 2.1 immediately flashing the v2.2 rom. Maybe I should have booted first into the new rom before trying to restore any backups...
When I plug my phone into the computer it starts charging (Battery icon with amount and animation of dots works)
I've tried using Droidexplorer as well but it doesn't detect my device.
My device makes the connection sound when connected to windows.
So hopefully, if you have any ideas for how this can be fixed with ODIN or how to get the phone back to the stock ROM, or even how I can force my phone into recovery or download mode without using a soldering iron then that would be extremely helpful. Thanks in advance
Click to expand...
Click to collapse
had the exact same problem only diff is that i was kinda doing while snoozing off
nd when i was in recovery mode i deleted ALL USER DATE nd stuff.
right now i followed most of the comments nd now i'm on DOWNLOAD mode connected to the computer i'm still trying to find out how to use ODIN to fix my phone think u can help me a lil.
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
- update 31/12/2010 -
Cause
corrupted boot loader , bad sbl.bin flashing
Prevention:
do not flash roms/addons/fixes with sbl.bin
if you must flash sbl.bin, do it while you are sure that your USB configuration is perfect, and do it as less as possible.
Solution (for those who already bricked to black)
you're not gonna like it
find riffbox jtag....
marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Happened to me too. I was tinkering with the Armani source to hopefully find something of use for Axura, and I bricked it. Same things happened to me. I called att and got a new one.
marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Did you try removing battery and putting it back and then opening ODIN, holding the volume up/down and inserting the usb to bring it on the download mode. I guess I might have experience almost similar issue with one of the rom. I almost freaked out. Phone wont show if its charging. It wont mount on the pc. But tried all the possible method available several times including adb shell command. And finally I did hear the magical sound from window when the usb is connected and finally it did work.
Also try the adb method if it doesn't go into download mode using volume button combo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Happened to me the first time I ran the OTA update from ATT. Paused the update, and when I resumed it - the phone though I finished downloading the JH7 update and tried to apply it.
It failed to apply and when it went to restart, it never powered on. No download mode, recovery, USB power, Odin, nothing. It was completely dead.
I got it replaced at the AT&T store.
If sbl.bin was removed or corrupted you should call the warranty center. Tell them ota update bricked your phone. Lol good luck
sent from my cappy running di11igaf's rom v2.5 at 1280mhz!!
I think it is just bad luck. I was once being careless and had the battery fall out of my phone while flashing, it interrupted the flash and I was still able to get in download mode to Odin it. Needless to say, I'll never flash again without the back cover on
bulletproof1013 said:
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes i'ts probably a bad sbl.bin, but I didn't remove it I flashed a new one, most of the rom's do the same
yeah sounds like it...sry for your luck.but seems like its toast then. keep us posted
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
There is a a way. Whenever you need to flash to stock you must use following stock. http://forum.xda-developers.com/showthread.php?t=818439
This is same as normal stock posted by DG except that it includes sbl.bin that we (1008) need. I use it everytime and 3 button combos for Download, Recovery work great.
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
it seems like this is not my case
I'm still looking for other people who had my case, and recovered (even with the JTAG riff box) or at least find someone who know's what we shouldn't do, so we don't break our phones.
so whats batch 1008?
This happened to me last night. I was trying to flash the Darky port via CWM and during the flash it became unresponsive. I had to pull the battery. This caused 2 different things. Sometimes it would be a never ending loop of boot screens and then others it would just go into recovery where it wouldn't let me do anything.
From here luckily I was able to access download mode by using the "adb reboot download" command. So I then got into dl mode and tried to flash stock (not the 3 button fixed one) and it froze on FACTORYFS (or whatever it is). I had no choice but to pull the battery. Now it won't boot at all. So my assumption is it wiped the bootloader. I'm not 100% sure but I feel that the reason it stopped where it did was because I didn't run odin as admin on my Win7 pc. I read in another thread that someone had the same problem when they didn't do that either.
If you are in a pitch black room and you press power you can see your screen illuminate, it's just very dim.
I have batch 1008 if it makes any difference to anyone.
Either way I'm heading to the device support center in a half hour or so to try to get a replacement. I originally was going to make or order a jig but people are saying it only works if the bootloader is intact. I originally had hopes because one person claimed that they recovered a completely dead phone with it, but upon further reading all others could not. It seems like his phone may not have been completely bricked.
Update:
Just got back from the at&t device support center. They gave me a new phone without any hassle. They asked what was wrong with my phone and I told them that I was trying to update it and now it won't turn on. The guy tried a few combinations of button presses and tried hooking it up to a jig-like device. Nothing worked so he just gave me a refurbished phones. No questions asked. As I was walking out he said a few people have had the same issue so it's not a big deal.
Either way I thought this would help to realize that there is likely no way to get the phone to boot unless you have a jtag handy.
I don't feel safe to flash rom via CWM.
If you really want to do that, delete the bootloader inside the .zip
So i think i killed mine too
so i get black screen, two button combo gives me SEC S5PC110 Test B/d
I opened odin but nothing Is this toast?
I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"
step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery
step 2) open odin1 click and hooked up the usb to the phone and computer no battery
step 3) inserted the battery holding only volume up+down
step 4) "BOOM" download mode and a happy dance
I posted this in the"read before flashing" thread there are other people who have recovered from this and now I think that the extra trick to this is getting a 100% battery you need this to flash, and state the phone is in now wont charge a battery.
hope this sound encouraging
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
RKight said:
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
norcal einstein said:
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
Click to expand...
Click to collapse
Yeah it's either that or just a misconception spread by the community. Both my old captivate and replacement were 1008. I have been able to get into recovery via the power+volume combination. I was also able to get into dl mode using the vol+insert usb combination.
It's possible I just got lucky on both but who knows.
I, and many others have a 1008 that don't go into download or recovery via the button combos without fixing sbl.bin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Last year(late 2010, maybe mid November), I rooted my phone and flashed recovery with no problem s at all. Some time after that I added Apps2SD and that went smoothly with no problems for about a week. I purchased an 8 GB SD Card for more storage room and after I partitioned it and switched the cards my phone started acting up so i rebooted it. After that I was stuck in a boot loop, so i tried to flash it back to stock but it wouldn't take to it no matter how I tried, whether it be through recovery or SW Update. So then I tried Odin Multi loader(cant remember which version but at the time I made sure it was the one meant for the Intercept) after I flashed it with the Stock through Odin, the phone bricked. Now it will not turn on in any way(recovery or other) the only thing it does do is vibrate when I plug it in to a computer, and it will occasionally show battery life through the touch screen and keyboard buttons by lighting them, but as soon as the it is unplugged it is a brick. I see the little bit of functionality as a little bit of to be able to fix this phone whether through ADB or another function but I desperately need help with this. Can someone please help me fix this phone?
note: I currently have a Samsung Transform as my main phone so if the Intercept can't be helped then it's not that big of a problem.
I have the same problem! Please help!
When you root a phone you put the rom, and recovery onto the sd card. changing sd cards disrupts this process. Put the old sd card in and tell me what happens.
The phone doesnt come on at all
see if you can get it into download mode with the battery out.
Pull battery
connect to computer with usb
vol down + camera + end
If you get into download mode this way flash the stock.tar using SWUpdater.
Nope, it doesnt work, thx though
Ok I've got the same problem with my intercept as well, So i just like to add (maybe its just me) that when i plug my phone to the computer the phone shows that its still functions right (without the screen on), I'm able to make calls, and receive them as well (with the touch of the answer button) but just the screen doesn't turn on, AT ALL!, so KJON i don't know if your having the same problem as me but I'm just a noob and i wouldn't know what to do. But there's some ammo if you need it.
I HAVE THE SAME PROBLEM! i dont even know where /sdcard/sdx/zip/ is!
My phone is also a samsung transform and not and intercept and whenever i press vol down+ Power, only the function buttons at the bottoms light up but not the screen
i am a noob.
help?
noooooob here...i didnt wanna start another thread since i have this same problem, so i hope someone reads this..
couple days ago i bricked my sprint intercept i was using SWu and forgot to take the Binary files for the Moment out so now i cant get my phone to DL mode, ive been searching since saturday night and have tried every Button combo posted and nothing, my phone will not turn on and ofcourse it isnt recognized by my pc BUT, ive noticed that only when its plugged in to the computer after trying to power it up several times it´ll vibrate then the 4 touch buttons will react to either the call or end button, also it makes the low battery sound and if i press the camera button it makes the volume sound but i CANT get to download mode, can i bring my phone back or is it done with? help please! and thanks in advance...
well, i would say boot into rrecovery by making the phone off either power button, or remove and replace battery.
next, you will need to press and hold in order: power/end call, call, and volume down.. this should boot recovery mode.
lastly, use the red scroll device to go to reset facory defaults or factory recovery, use common sense while looking. select with clicking and use arrow back button to go back to recovery main, then reboot to system. easy as pie.
Have you tried ODIN or ADB?
I have flashed the Intercept numerous times, soft bricked more than once, I was always able to recover using either the stock bootloader, CWM recovery, or flashing the ROM/Kernel directly using ODIN or ADB.
If you are still having these issues drop me a line and I'll gather some links together that should get you back up and running.
If the phone will not boot at all, even with a charged battery, I would definately try contacting Virgin Mobile and escalating the issue. I've had plenty of luck replacing devices claiming that the device just dropped dead without notice. They are usually good about sending out a replacement phone, and on rare occasions even giving you an upgraded unit if they are out of stock.
Good luck!
Did you use Odin or the swupdater?
Bug difference. Sounds like there's a missing boot loader.
Sent from my SPH-L710 using xda app-developers app
Hi, did you guys fix your bricked phones? Today I have bricked my Samsung transform (bad flash went with SW upgrade.
Only vibrates sometimes and the buttons flash a little, but no boot at all. Is there any chance to fix it? even with Jtag?
regards
hello,
attempting to root my stock gingerbread i think i forgot to choose the pit file. well now i can barely get into the stock recovery program and when i choose factory reset it does it but when rebooting i still get this icon. so i cant get into download mode at all. ive left the battery out for a while as well. how can i get back into download mode? thanks.
Odin did not complete properly so you have no system to reset. Hook your phone up to the computer with the battery and sd card out. Press and hold the "1" key on the physical keyboard then add pressing and holding the power button. Odin away. Pop the battery in when it tries to reboot.
when starting off rooting ive had this problem many times. It usually has to do with screwing up odin. The first thing i want you to do then, is learn how to use heimdall, you have a much better chance of soft bricking your phone. I use it myself and never have had a problem.
To recover your phone there are a couple of solutions. There used to be a thread about this rest button near the camera lens. It is just below it to the left. This should get you into download mode. you will want to press it while your phone is off and battery is in. You will need a paper clip to do this.
Also you are going to want to leave your microsd card, so that it is not affecting the process in any way. Also double check that your phone drivers are correct.
Lastly sometime just waiting with the sdcard and battery out will help, as there is some sort of cache or somethign that must be cleared. I dont know if this true its just what I heard.
Also I dont know why I do this, but sometimes if you hold a key down before inserting the battery for about 30 sec, 1 key is usually the best cause you need it for download mode, and then inserting the battery and hit power, it might get you out of the soft brick.
I hope I help, its been a while since i've seen it, thank god.
irule9000
ok i reinstalled the phone drivers and was able to successfully odin the device to completion. it gets even better now. i only see lights on the bottom of the device now when trying to power on. wow. not my weekend. i have the battery pulled and im going to wait a while.
It will not reboot without the battery in.
Sent from my SPH-D700 using XDA App
i meant i had the battery in and it wouldnt properly turn on so i pulled it again. Sory about the confusion
nyr35blue said:
i meant i had the battery in and it wouldnt properly turn on so i pulled it again. Sory about the confusion
Click to expand...
Click to collapse
No prob. We all are just trying to help. Maybe it was a bad download on the Odin file. I would suggest repartition with the PIT file included.
Sent from my SPH-D700 using XDA App
phew. i was able to use an older version of odin and flash back to EC05. Thanks guys!
Hi people, something quite terrible happened to my phone when I woke up today. Before I went to sleep the phone worked and was charged by about 40% but some apps were force closing like crazy so I turned off the device before I went to sleep, cuz why not, eh? Then I woke up and turned on the phone and it showed the screen to choose if I want to go into downloading mode, I pressed cancel and the phone shutdown and now it wont turn on.
I tried soft resets, tried to charge it for 10 minutes, but the thing is the phone is like its hard bricked for no apparent reason... even the charge indicator when phone is off doesn't show anymore, no lights, no nothing. Please help me. If anyone has an idea what to do it would be greatly appreciated. It worked this morning, no one else touched the phone. :crying:
if it doesnt boot then its a battery problem, even in hard brick, it has some kind of flights flashing.
if Its hard brick then its paper weight, sorry.
Chord_Hugo87 said:
if it doesnt boot then its a battery problem, even in hard brick, it has some kind of flights flashing.
if Its hard brick then its paper weight, sorry.
Click to expand...
Click to collapse
If it's the battery what can I do here at home? At least try? I don't think it's a hardbrick cause I didn't do anything iregular to the phone, it was working before I shut it down and went to sleep. Idk how I hardbricked it by turning it off. :/
theSperks said:
If it's the battery what can I do here at home? At least try? I don't think it's a hardbrick cause I didn't do anything iregular to the phone, it was working before I shut it down and went to sleep. Idk how I hardbricked it by turning it off. :/
Click to expand...
Click to collapse
well the storage drive could fail, that could be another possibility which if I think about it now that seems to be the case. best bet send it to samsung.
if you plug your phone into your computer and it does not read or register, you really dont have any other choices. This goes for all phones, the forum can help you with soft brick, not something like this, this looks like a hardware failure.
Chord_Hugo87 said:
well the storage drive could fail, that could be another possibility which if I think about it now that seems to be the case. best bet send it to samsung.
if you plug your phone into your computer and it does not read or register, you really dont have any other choices. This goes for all phones, the forum can help you with soft brick, not something like this, this looks like a hardware failure.
Click to expand...
Click to collapse
The phone rebooted constantly and force close apps from the day I bought it. I thought it was software issue... I went to my carrier to complain but they said nothing is wrong with the phone (way back few months ago). So my last question is this, can a phone force close apps and restart constantly with a software issue? or does it happen only to devices with hardware issues?
theSperks said:
The phone rebooted constantly and force close apps from the day I bought it. I thought it was software issue... I went to my carrier to complain but they said nothing is wrong with the phone (way back few months ago). So my last question is this, can a phone force close apps and restart constantly with a software issue? or does it happen only to devices with hardware issues?
Click to expand...
Click to collapse
that sounds like a storage drive failure...no apps doesnt do that and phone doesnt restart for no reason.
Chord_Hugo87 said:
that sounds like a storage drive failure...no apps doesnt do that and phone doesnt restart for no reason.
Click to expand...
Click to collapse
Ok so good news! Today I plugged it in the charger again and it booted! As I see it when I turn it off it doesnt really shut down properly and it stays in some kind of a phase and doesnt let me reset or do anything really... but It drained the battery that it had left and it bugged out. I know this cause I shutted it down again via the android option and its "bricked" again. Now I will wait for it to lose charge again so I can boot it.
Can you please tell me how to properly flash via odin to the latest nougat firmware? The phone was from Vodafone in Germany, few months ago I flashed a Netherlands firmware, then some other one few weeks down the road. Can you please tell me how to flash it back to full stock and what firmware should I download? The model is SM-G935F and the S/N is RF8H61YE4CP. I prevously tried THIS firmware from sammobile. Is this the correct one for my phone? I tried using samsung smart switch but it says "Secure Check Fail : Bootloader" when it tries to emergency restore it in the download mode, and the smart switch software says just error. Also whenever I flashed with Odin, BL never wanted to flash cause of just one file in every BL md5 file and that is the param.bin one, everything else flashes like it should. Please write me a guide on how to flash it properly and "upgrade" everything to the latest version correctly for my phone. (many settings in Odin that I never touched)
theSperks said:
Ok so good news! Today I plugged it in the charger again and it booted! As I see it when I turn it off it doesnt really shut down properly and it stays in some kind of a phase and doesnt let me reset or do anything really... but It drained the battery that it had left and it bugged out. I know this cause I shutted it down again via the android option and its "bricked" again. Now I will wait for it to lose charge again so I can boot it.
Can you please tell me how to properly flash via odin to the latest nougat firmware? The phone was from Vodafone in Germany, few months ago I flashed a Netherlands firmware, then some other one few weeks down the road. Can you please tell me how to flash it back to full stock and what firmware should I download? The model is SM-G935F and the S/N is RF8H61YE4CP. I prevously tried THIS firmware from sammobile. Is this the correct one for my phone? I tried using samsung smart switch but it says "Secure Check Fail : Bootloader" when it tries to emergency restore it in the download mode, and the smart switch software says just error. Also whenever I flashed with Odin, BL never wanted to flash cause of just one file in every BL md5 file and that is the param.bin one, everything else flashes like it should. Please write me a guide on how to flash it properly and "upgrade" everything to the latest version correctly for my phone. (many settings in Odin that I never touched)
Click to expand...
Click to collapse
i had a simmilar problem i couple months ago when i flashed a custom kernel.
i was overclocking the cpu but caused the phone to freeze actually without being able to to anything
i thougt my battery was dead also
when i charged it nothing came up into the screen also.
you just have to hard reset it but just keep on pressing your volume down button together wih your home button and the power button
it may take lonnger then you can normally do it cuz your phone freezed
but eventually your phone will just reboot into download mode then eand you can hit the volume down button to reboot your phone then