Related
NOTE:
So far this has been the only sure fire method I've found to 100% get around any brick situation regardless of firmware, etc. This only works for the captivate, not any other galaxy s variant.
Situations: phone-!-Computer / no download mode
Black Screen / RST_STATUS 0x0
Procedure:
1. Remove the battery, external SD card and SIM card.
2. Wait 10 seconds.
3. Open odin3
4. Connect usb cable.
5. Hold volume up + volume down + Power.
6. Insert battery.
7. Release POWER BUTTON ONLY.
You should now be in immediate download mode.
Please forgive me if this is duplicate some where, but I tried every procedure I could find on google to no avail, then accidentally found this method just before I was going to box it back up and see if my buddy at AT&T would make me eat it or not.
My situation was: Launched Odin3 to flash H3 firmware, died twice in the middle, and on the third time locked up half ways just at the beginning of factoryfs.rfs -- Then the phone did nothing. Blackscreen is all. Interestingly enough, while in the state if you hold volume up + power, it will give a hw diagnostic screen. Beyond that I could get no where. Just a black screen, no acknowledgement when connected to PC, no charging indicator, nothing.
If this is a dupe Im sorry but this method I could not find and hope to make it readily available to people who may think their phones bricked.
Update 12/22/2010:
How to BRICK the phone / WARNING!!!
If for whatever reason you decide to use Odin to flash a stock GTI9000 ROM and manually add the kernels and modems using a "pure" 2.2.1 sammy rom. BEWARE.
Researching a lot, it seems the consensus is that the sbl in the 2.2.1 versions of the GTI9000 has *hard* download mode crippled.. Meaning if there is a software screw up YOU CANNOT USE A USB JIG OR ANY OTHER METHOD OF GETTING THE PHONE IN DOWNLOAD MODE!!! To fix it you'll need a new one or JTAG to replace the bootloader.
As far as I can tell, beyond getting completely rid of the AT&T logo, there is no need to flash boot/sbl to get the "purity" of the 2.2.1 sammy roms.
Extract all files from the tar EXCEPT boot/sbl and re-tar and flash just those to avoid overwriting the stock captivate boot loader.
Also, it does not appear the boot/sbl from the captivate 2.2 leak suffers this same problem.
For any one iffy on bricking their phones, stay away from roms that remove COMPLETELY the AT&T logo on boot. This generally means the boot loader has been messed with any you may be screwed if you soft brick the phone. Most CWM roms dont overwrite the boot/sbl, but some can and do. Watch yourself.. if it the AT&T logo goes away COMPLETELY, I recommend flashing JF6 with One click while the roms alive using adb reboot download and try another rom.
thanks!
worked...took a few tries but some trick with this captivate to get it into download mode.. i was totally bricked too, diag screen with PC/Phone icons and exclamation mark. for me 1.) plug usb, 2.) hold power and vol up/down and connect battery (it fell out) and i was in download mode
I guess a similar procedure was on the odin3 one click thread, but there is something different in your procedure, it's not my case but it would be nice if some people confirms this as this may be useful and if it really works it should be included in odin thread
What worked for me was: Pull the battery, sim and micro sd card. Open odin on the PC. Insert the battery. Hold vol up and down then with the buttons held connect the usb cable. Just remember to plug in the usb cable with the vol up and down held in and odin must be open on the computer.
I also ran into the vol up plus power red text screen. Interesting to note that one of the fields will change depending if the usb cable is connected or not.
mine is dead
mi samsung captivate was working great but, suddenly it go black and only the touch bottom have light, when i plug it in the a/c it show is charging. i'm mac user and a read that i ned to use odin3 but it not work on mac. how i can unbrick the phone???
is rooted with one click lag
the dbdata was modif to
thats all
HEEEEELLLLLPPPPPP
Odin will not open on the mac?
Cant you use a virtual machine and use Odin on a Mac that way?
Or else take the odin 3 single click for JF6 and use on a friends Windows Computer.
Please help - unable to flash back with Odin3
I have pretty much tried it all at this point and am trying to figure out what I'm doing wrong.
I followed the directions just in case get to the big yellow triangle with the droid shoveling and the screen stays at "downloading, do not turn off target..."
Of course I had Odin3 open already but its not seeing my phone, USB drives are installed am using Odin3 ver. 1.30.
Any help would be appreciated, TIA!
TechNut* said:
I have pretty much tried it all at this point and am trying to figure out what I'm doing wrong.
I followed the directions just in case get to the big yellow triangle with the droid shoveling and the screen stays at "downloading, do not turn off target..."
Of course I had Odin3 open already but its not seeing my phone, USB drives are installed am using Odin3 ver. 1.30.
Any help would be appreciated, TIA!
Click to expand...
Click to collapse
Best way to get download mode is use adb and type adb reboot download.
Or follow the volume up/down held with odin open on the computer, then you plug in the usb cable to the computer.
askpcguy said:
What worked for me was: Pull the battery, sim and micro sd card. Open odin on the PC. Insert the battery. Hold vol up and down then with the buttons held connect the usb cable. Just remember to plug in the usb cable with the vol up and down held in and odin must be open on the computer.
I also ran into the vol up plus power red text screen. Interesting to note that one of the fields will change depending if the usb cable is connected or not.
Click to expand...
Click to collapse
Thank you thank you thank you. i had a totally dead no boot or anything and this worked, i was going through the whole returning the phone senerio in my head
mattbeau said:
Thank you thank you thank you. i had a totally dead no boot or anything and this worked, i was going through the whole returning the phone senerio in my head
Click to expand...
Click to collapse
Just sharing the info! Makes you think twice about trying something else don't it?
does not seem to work because as soon as my battery touches the contacts it goes to the diag screen. do I have to release the power button in super human speed times there?
looked at all threads here, looked elsewhere -- there are some that are not fixable. Wanted to add that in case others come here and think that they might be the only ones that can't get it to work.
Ended up sending mine off to Samsung to reset today. :/
I love you! I called AT&T to send me documentation to sign and it was going to cost me 125 dollars to get it replaced even with warranty. And you fixed it !
i have tried just about every single method detailed in these forums, and nothing works.
Trying what OP suggested just sends me to the battery charging animation screen.
Anybody have any ideas ?
file analysis
I keep can get to the download screen and I hit start and it does the same thing everytime it just does File analysis i cant figure what i am doing wrong here somebody please help me
I think the issue was it had something to do with 64 bit windows 7 i just re did the stock rom one click solution and it worked fine
thekurrgan said:
NOTE:
5. Hold volume up + volume down + Power.
6. Insert battery.
7. Release POWER BUTTON ONLY.
You should now be in immediate download mode.
Click to expand...
Click to collapse
Thank you for sharing your experience.
I don't have a Captivate yet but am doing research on it and hopeful of getting one. I am confused about one thing.
Every where that I have read about how to enter Recovery mode or Download mode on the Captivate using the 3 button method, it says holding down both Volume UP + Volume Down (plus Power button) will enter Recovery mode. But you say it enters Download mode which is confusing to me. As I recall, to enter Download mode you must press the Vol Down only (plus Power button). Could it be because the phone won't go into Recovery mode, it goes into Download mode instead? Am I missing something?
Thank you!
Download mode is for updating the phone's firmware.
Remove battery, plug in the usb cable to the phone, open ODIN on the computer (need usb drivers installed before hand) on the phone hold volume up and down then plug the phone into the computer. Your phone will say DOWNLOADING. This method works even if you run into problems and the phone refuses to boot properly.
Recovery mode is for installing Update.zip. The method is tricky but involves holding volume up/down and power, the phone will show ATT then go black. It will repeat that but after the second time it goes black let go of power.
If that doesnt work, android debug tools ADB reboot recovery will work even better.
Or root the phone and use Clockwork Rom manager to boot into recovery, just press the menu item.
askpcguy said:
Download mode is for updating the phone's firmware.
Remove battery, plug in the usb cable to the phone, open ODIN on the computer (need usb drivers installed before hand) on the phone hold volume up and down then plug the phone into the computer. Your phone will say DOWNLOADING. This method works even if you run into problems and the phone refuses to boot properly.
Recovery mode is for installing Update.zip. The method is tricky but involves holding volume up/down and power, the phone will show ATT then go black. It will repeat that but after the second time it goes black let go of power.
If that doesn't work, android debug tools ADB reboot recovery will work even better.
Or root the phone and use Clockwork Rom manager to boot into recovery, just press the menu item.
Click to expand...
Click to collapse
Thank you askpcguy! I understand the difference between Download and Recovery modes.
So the procedural difference here is having the battery in + Power button, versus battery not in (use USB cable instead) and no Power button. Can the phone get power from the PC via the USB cable? This seems to differ from what the original poster said about download mode. Perhaps OP could edit his original post for clarification? Or am I still missing something? Thanks to all
The phone does get power from the USB cable.
The difference is one procedure uses the USB cable (download mode) and the other does not (Recovery mode).
The volume up+down method does not use the power button, the phone is powered on into download mode once you plug in the USB cable.
We say pull the battery to get the phone powered off. If a firmware flash stalled or doesn't complete, pull the battery and try again!
I now understand the precedural difference.
Thank you askpcguy!
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
in the main setting, application, developer settings.. is usb debugging enabled?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
When I first set up ADB and Fastboot on my pc, I was getting a response when writing 'adb devices' in the console. However, 'fastboot devices' returned absolutely nothing.
Solution (with phone connected to pc and usb debugging cheched):
1-shut down the phone
2-press and hold Volume Up key + Power
3-once in bootloader interface, in the pc command prompt, type 'fastboot devices'.
Voila!
By the way, don't mount the phone as usb storage device.
Thanks for the responses guys but yes, USB debugging is enabled and yes, I've used that way to get to fastboot mode as well as adb reboot bootloader
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
vstar said:
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
Click to expand...
Click to collapse
easy way to set up fastboot
Any solution
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
OK So I am in the exact same situation.
Nexus S, Broken power button, adb can see the device, fastboot cannot. fastboot cannot be navigated with the volume keys.
I also want to put an other rom onto it, but firstly I want to put TWRP recovery on it, as it supports touch, CW needs the power
button which like mentioned does not work.
I would rather not unsolder my power button to get into fastboot, any suggestions on how that might still be achieved?
thx
catalinu said:
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
Click to expand...
Click to collapse
Yes, it should have been better for me to have also a possibility to enter in fastboot with the power button blocked in ON position, but I didn't find. And now I know no way how to power it up...
fastboot drivers
http://www.samsung.com/us/support/owners/product/GT-I9020PWAATT#
has anybody considered using this executable from samsung ..
from what i understood when installing it ,it only unzips the contents at programfiles/Samsung/drivers
then you can check this thread to install them spesifically http://forum.xda-developers.com/showthread.php?t=1901617
..In short.
Go to
"Device Manager"
find
"Android 1.0" or something like that (i had my device in fastboot/bootloader mode, dont know if it was necessary)
install drivers from the drivers directory and install
P.S. Mine is an ordinary 9023nexus s (slcd) though
be a bit more careful with nexus s4g
Received an OTA notification and installed. At last check, was at the "updating apps" stage. Went to bed. This morning, nothing. Won't turn on at all. Was plugged in all night. No splash screen, no vibration, nothing. Totally dead. Power button + Down button doesn't work. Any hope of recovery?
Update
Also getting - unknown usb device (device descriptor request failed) / code 43 when trying to plug the phone into my computer.
Did you try holding volume down and connecting phone to computer? Try disconnecting the battery for a few minutes, reconnect the battery, and try to power up.
If for some reason it's an issue with the bootloader, there's a backup bootloader, hold vol up + power
Also something to try is LGNPST, that can reflash stock firmware
Power button+volume down doesn't work? The device might be fried. That might also be why your PC doesn't recognize your phone, although the very fact that your PC does recognize that there is something trying to connect to it, makes me doubt my hypothesis.
I'd try to adb reboot it, I think the phone doesn't have to be turned on for that to work. Are you familiar with adb commands? That way I was able to revive my old HTC that was stuck in bootloop and volume buttons didn't work so couldn't get into recovery. Just turned off the phone, plugged into the PC and adb reboot recovery or something, don't remember the exact command line, but you can find guides about it easily.
damn ! i have the same problem after the last OTA update
Maybe it's volume up while inserting the USB cable? Can't remember as I haven't used a nexus 5 for months.
Greetings of the day,
Hello everyone, I'm having a oneplus one 64GB phone that is not getting start, everytime i connect it with the charger it goes into a bootloop. Yes the phone was rooted and I was using a custom ROM with the default kernel. The issue started when I tried to reset the phone to battery settings. I think I somehow messed the kernel and now it is stuck in bootloop. The problem is that I can't connect it to my computer or put it in debug mode as it just restarts again. Any idea how to actually boot it so I can install the kernel and ROM again?
Lazy Titan said:
Greetings of the day,
Hello everyone, I'm having a oneplus one 64GB phone that is not getting start, everytime i connect it with the charger it goes into a bootloop. Yes the phone was rooted and I was using a custom ROM with the default kernel. The issue started when I tried to reset the phone to battery settings. I think I somehow messed the kernel and now it is stuck in bootloop. The problem is that I can't connect it to my computer or put it in debug mode as it just restarts again. Any idea how to actually boot it so I can install the kernel and ROM again?
Click to expand...
Click to collapse
Can it go into recovery mode(power+ vol-)?
Mr.Ak said:
Can it go into recovery mode(power+ vol-)?
Click to expand...
Click to collapse
No, My phone is not getting on but whenever i am connecting it with my charger the phones goes in the Bootloop, and when i am connecting it to My PC while pressing Volume Up + Power Button Pc shows that the Unrecognized devices has been connected.
And i think phone is Hard Bricked. I have tried ADB software and one plus 1 drivers manually but it didn't worked too. I have tried minimal ADB too but it also didn't work.
Kindly let me know about it.
Lazy Titan said:
No, My phone is not getting on but whenever i am connecting it with my charger the phones goes in the Bootloop, and when i am connecting it to My PC while pressing Volume Up + Power Button Pc shows that the Unrecognized devices has been connected.
And i think phone is Hard Bricked. I have tried ADB software and one plus 1 drivers manually but it didn't worked too. I have tried minimal ADB too but it also didn't work.
Kindly let me know about it.
Click to expand...
Click to collapse
Volume UP + Power should boot in fastboot mode. Volume Down + Power should boot into recovery. First, try to boot recovery.
giaur said:
Volume UP + Power should boot in fastboot mode. Volume Down + Power should boot into recovery. First, try to boot recovery.
Click to expand...
Click to collapse
I have tried both, but nothing happens with it, Volume UP + Power shows the unrecognizable device is connected and Volume Down + Power does nothing it continues with bootloop .
Have you got Developer Options enabled?
Goto About Phone & Tap Build Number until Developer Options is activated. Goto Developer Options> Advanced Restart & enable the switch.
Press power button->Restart->Recovery.
It will now boot into Recovery.
Also have you tried keeping hold of power button whilst it bootloops. Keep holding the power button until it powers off. Then press Volume Down & Power Button to power back up (you might see a slight flicker onscreen that means it should go into Recovery mode). Keep hold of these buttons until you gain Access to Recovery Mode.
This will allow you to Recover or flash a different ROM.
If you're having issues connecting to a computer (Windows) try downloading Windows Media Center for your version of Windows. This will install media drivers to recognize your phone.. If all went well you will get the pop up with A0001 (Codename of OnePlus One). From there you should be able to enter fastboot mode through ADB.
If this doesn't help you, I'm sure that someone else will untangle the puzzle to get your device in good working order buddy. Good Luck.
bmark240 said:
Have you got Developer Options enabled?
Goto About Phone & Tap Build Number until Developer Options is activated. Goto Developer Options> Advanced Restart & enable the switch.
Press power button->Restart->Recovery.
It will now boot into Recovery.
Also have you tried keeping hold of power button whilst it bootloops. Keep holding the power button until it powers off. Then press Volume Down & Power Button to power back up (you might see a slight flicker onscreen that means it should go into Recovery mode). Keep hold of these buttons until you gain Access to Recovery Mode.
This will allow you to Recover or flash a different ROM.
If you're having issues connecting to a computer (Windows) try downloading Windows Media Center for your version of Windows. This will install media drivers to recognize your phone.. If all went well you will get the pop up with A0001 (Codename of OnePlus One). From there you should be able to enter fastboot mode through ADB.
If this doesn't help you, I'm sure that someone else will untangle the puzzle to get your device in good working order buddy. Good Luck.
Click to expand...
Click to collapse
he said his device is in bootloop. how come he will turn on the developer option then?
akhiarr said:
he said his device is in bootloop. how come he will turn on the developer option then?
Click to expand...
Click to collapse
This has got to be some sort of World Record for resurrecting an old post from over five years ago. Congratulations on that achievement!
Did you just join to post that?
Lol.
Hello i have my ME301T probably bricked. Last time I used omni-4.4.4-20150521-me301t-FINAL ROM, which was working fine for some time. After longer time, when I didn't used my tablet, I'm not able to start it, neither to get into the fastboot or recovery.
What is working?
- APX mode
- charging
I tried also disconnect the battery - it didn't helped. I measured voltage and its fully charged (4,17 V). When I connect the charger, just red battery icon is showed on the display for few seconds and thats all. The same after long press of power button or in combination of power + vol. down.
So the only mode i can get is the APX. I was able to install APX driver but I'm not sure what next? I probably need some blob file, which I cannot find.
Any idea what I can try now? Or is my device really completly bricked without any chance?
Thanks
Haldy said:
Hello i have my ME301T probably bricked. Last time I used omni-4.4.4-20150521-me301t-FINAL ROM, which was working fine for some time. After longer time, when I didn't used my tablet, I'm not able to start it, neither to get into the fastboot or recovery.
What is working?
- APX mode
- charging
I tried also disconnect the battery - it didn't helped. I measured voltage and its fully charged (4,17 V). When I connect the charger, just red battery icon is showed on the display for few seconds and thats all. The same after long press of power button or in combination of power + vol. down.
So the only mode i can get is the APX. I was able to install APX driver but I'm not sure what next? I probably need some blob file, which I cannot find.
Any idea what I can try now? Or is my device really completly bricked without any chance?
Thanks
Click to expand...
Click to collapse
If you cannot boot into either fastboot or recovery, the tablet is bricked for good. I'm sorry!