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
Related
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?
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.
...but after flashing hundreds of times I've never had this problem before.
Flashed one of intratech's frankenstein roms (GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5) and it just stayed on the booting page for seriously more than an hour.
Went back to download mode and flashed the kernel that goes with it (Kernel_I9100XWKJ3.tar.md5) and now I have no recovery mode and no download mode!
I do know how to get into both modes, it just isn't doing it. Instead of going into download or recovery, it just tries to boot as normal, so it's properly stuck.
Not sure Samsung would take kindly to me walking into their service centre with a custom rom etc, what do you reckon?
Try to buy a USB JIG off ebay, plug it in to see if it works
Sent from my GT-I9100 using xda premium
JUST done that actually lemin, thanks.
I guess if that doesn't work I'll have to take it to be fixed.
Wonder what could have gone wrong with the flashing...
Have you tried to remove the battery?
Sent from my GT-I9100 using xda premium
Seems all you needed in the first place is a factory reset from recovery, if the phone is trying to boot, it means the boot partition is intact and you are probably not executing the button combination properly.
Hold Volume up and home, then press power, keep holding the buttons until you are in recovery mode, then do a factory reset and reboot, enjoy your phone
Achilles, you might have thought so, and I wouldn't normally rule out the possibility of me being a dumbass, but really there is no recovery or download mode available. It just doesn't go into either. :-(
fergusstrachan said:
Achilles, you might have thought so, and I wouldn't normally rule out the possibility of me being a dumbass, but really there is no recovery or download mode available. It just doesn't go into either. :-(
Click to expand...
Click to collapse
You are not being a dumbass, just probably not timing the button presses correctly, if you don't hold those three buttons down until the recovery is actually on the screen, the phone will try to boot normally, talking from experience here
If you are doing this but the phone is still trying to boot normally, then a jig might be the only way to force download mode as you have said that it is trying to boot, so the partitions are intact, a full brick shouldn't boot at all....
Also, I flashed the same ROM, it is not really a custom ROM in the true sense, just a stock ROM with different CSC and MODEM, I really doubt "they" can call that a custom ROM and I doubt they would be able to tell anyway, "it's all stock parts" so long as you didn't flash any custom kernels or anything.
Good Luck.......
Just my humour achilles.
Trust me, as sure as I am about putting one foot in front of the other to walk, I know how to get this baby into download/recovery mode, and it aint playing.
Jig, then service centre it is. Until then, have to use the Galaxy Tab a la Dom Joly.
Hi, i got a problem with my 10:1 tab. Today i tried to install honeycomb rom using clockworkmod recovery and after the installation and rooting my tab there was a question should flash boot be fixed because the new one will replace other without going back so new flash and root from honeycomb could take it place and i said no to fixing it, second after my tab went off black and it not reacting to anything including trying to power on and get into recovery mode and i tried to push all the buttons and nothing works. Odin doesnt recognize the tab and if i plug it to charger or pc there is no response. The only thing i realized is i heard a plug in usb sound when i connect tab to pc and try to pull the power on button for like 5 seconds i hear plug in and second later plug out usb sound. What can i do to make it works again? I cannot give it to guaranty and all i can do is by myself
Send it to Samsung for a repair.
i cant, i have no guarantee all i can do is by myself, what can i do?
Did you try to hold power button a little longer ? Like 10 or 30sec. This works for some devices
Sent from my GT-P3110 using xda premium
Pull back cover off (use google to figure out how to do so), unplug battery for a few seconds. Plug battery back in. Press and hold power + vol down to try to get into ODIN.
There is no honeycomb rom for these tabs. What did you try to install? Link me.
Holding power button gives nothing, i tried ever combination for a couple minutes and not working. I tried to remove battery yesterday but it was connected via cables and there was no way to remove it without cutting out cables as far as i seen, if anyone can know how i can remove battery then let mw know because i can't find anything ever the internet. I downloaded HoneyVillain_1.2 from here http://forum.xda-developers.com/showthread.php?t=1138115. I tried to plug tab to charger today but after 10 hours it didn't worked at all, still got black screen with no reaction to buttons ;/
Hello
bad news - I killed my P5100 2 months ago and I can't repair it. I have same problem - I can hear plug on / plug off sound in Windows. But i have installed drivers and found that this is OMAP4430 device was connected/disconnected each time. And I can't do anything with my Tab.
I have took my Tab to official Samsung service and I've received answer that it is not repairable - only full replacement of internal board possible, and it costs 300$.
And I have tried to unofficial services and they tells me what my problem. Bootloader was corrupted and device can't start. So it is impossible to repair bootloader because it is protected in Galaxy Tab 2 and they proposed me to replace internal flash memory chip.
So I have dead Tab and wait for ability to programmatically repair my Tab
You can see my thread here http://forum.xda-developers.com/showthread.php?t=1908949, maybe it will be helpful for you
FrostX26 said:
Holding power button gives nothing, i tried ever combination for a couple minutes and not working. I tried to remove battery yesterday but it was connected via cables and there was no way to remove it without cutting out cables as far as i seen, if anyone can know how i can remove battery then let mw know because i can't find anything ever the internet. I downloaded HoneyVillain_1.2 from here http://forum.xda-developers.com/showthread.php?t=1138115. I tried to plug tab to charger today but after 10 hours it didn't worked at all, still got black screen with no reaction to buttons ;/
Click to expand...
Click to collapse
I honestly believe that the Rom you downloaded is for the acer ionica!
See xda has created separate forums for each phone because you can't use one phones rom for another! Yet you flashed that!
There s nothing you can do other than sending your phone for repair!
Sent from my GT-P3100 using Tapatalk 2
Ok so i installed wrong rom for my tab right? Is there something i can do to repair it by myself?
FrostX26 said:
Ok so i installed wrong rom for my tab right? Is there something i can do to repair it by myself?
Click to expand...
Click to collapse
No. Its a paper weight now and you could have prevented this by reading.
If you can't get it into Download Mode, then the only options are to send it to Samsung to fix it, or find some loose papers.
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
FrostX26 said:
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
Click to expand...
Click to collapse
http://www.jtagbox.com/jtag-news/ri...tab-2-101-unbrick-dead-boot-repair-supported/
I don't know how much support you'll get to follow this method but if nothing else will work it's worth a try.
As far as this tablet being unbrickable, that's only true if you don't intentionally flash something that was made for a completely different tablet...
Sent from my GT-P5110 using XDA Premium HD app
Well that's the point, I flashed with rom made for different tablet and it's dead now My question was if any brick could be repaired if i'll give it to someone with all the right tools to resurrect it, or there are certain bricks that can't be repaired no matter what tools and skills the person who attempt it have?
FrostX26 said:
Well that's the point, I flashed with rom made for different tablet and it's dead now My question was if any brick could be repaired if i'll give it to someone with all the right tools to resurrect it, or there are certain bricks that can't be repaired no matter what tools and skills the person who attempt it have?
Click to expand...
Click to collapse
Check my post again for the link as that's the only method that shows up on Google search for this tab.
does odin recognize your tablet?
Is it a tab 2. In your op it just said tab 10:1. Not tab 2. Just making sure as this is the tab 2
sent from MY BAD A$$ ET4G
I might be able to help u
Alright i had the problem recently and heres what i did to fix it If you can get into download mode ur all good from there. To get into download mode hold the power button and up on the volume rocker, if u get a message saying flashing roms is dangerous blah blah blah then press down on the volume rocker to enter download mode. Odin will recognize it if its in download mode, also what model is ur galaxy tab? Also if its a 10 inch model GT5113 i have the stock rom file for it so i could send it to u
Some helpful Info
Maybe you should have said yes? because after all you can't be too carefull , maybe there was something wrong with the rom. If the system asks you if you want to fix ALWAYS say YES. You should have said yes. Why did you say no ?! all right now to the fixing part. PLEASE NOTE I'M NOT AN EXPERT IN ROOTING BUT I'LL GIVE IT A GO. I think that if you can, then power it up and press the VOLUME UP key while holding the power button. From the menu choose recovery and factory reset your device. If it's possible reset rom to default. It should work if not then Post a reply saying not and I'll see what else can be found. Hold on tight for now!There is a Optional thing you can do if the above doesn't work: that is, if possible, you can un-root your tablet with an app from the market. If all of the above is impossible to do, and you cant even power your tab on, it's as useful as a brick, a black screen. Then I'm afraid it's a hard brick fopr you, boyo.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
FrostX26 said:
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
Click to expand...
Click to collapse
Sorry for my previous post, didn't read the whole forum! Stupid me! ok now there are only two types of brick. Soft brick and hard brick. Soft brick can be fixed, Hard brick - Not quite. And as you said, you flashed a rom for a different tab, maybe thats a compatibility issue. If you want a new os, honeycomb to be exact. You can always upgrade, just search 'honeycomb upgrade'.
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck
tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck
El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...
tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef
1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !
Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.
My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!