I've tried to put a new ROM using Clockwork Recovery 6.0.1.2, during process it stuck for 4 hours and was turned off by power button.
After that tab don't react on power button, on pwr+vol up, pwr+vol down, pwr+ both vol buttons, nothing.
It even doesn't show battery icon when charging - screen is always black.
Any advices?
Thanks in advance.
I think the method described here will do the trick: http://forum.xda-developers.com/showthread.php?t=1478361
kallt_kaffe is having the same problem and he describes the procedure as: "basically tape down the power button to force a reboot cycle."
Aecidz said:
I've tried to put a new ROM using Clockwork Recovery 6.0.1.2, during process it stuck for 4 hours and was turned off by power button.
After that tab don't react on power button, on pwr+vol up, pwr+vol down, pwr+ both vol buttons, nothing.
It even doesn't show battery icon when charging - screen is always black.
Any advices?
Thanks in advance.
Click to expand...
Click to collapse
1. Put on your computer headphones and turn the volume up.
2. Plug your tablet into your computer via USB.
3. Hold the power button & Vol - keys together (Volume - is the side that is closest to the power button)
4. Listen for the "USB device connected" or "USB device disconnected" sound on your PC
5. If you can hear that, something has gone bad within the bootloader and the display does not initialize properly. Edit: The ICS installation does indeed attempt to patch the bootloader
6. If there is no sound, then the tablet is stuck in limbo, so go ahead and do the battery drain procedure as described in the above post.
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
-open ODIN 1.85 and see if it shows a connected device. If your PC made a connected sound, then there will most likely be a yellow COM port in ODIN.
- Hold [Power] & [Volume Down] together for 15 seconds or longer whilst monitoring your Device Manager windows to see if you can get the tablet out of APX mode and have it appear as another type of Device. Then press Volume+ several times with 1.5 sec. intervals. With luck, this should get you into Download mode, and ODIN will shine yellow for you.
- While doing all of the above keep your headphones on and listen for connected or disconnected sounds from your PC.
- Make sure you have this firmware for the P7300 which contains a bootloader, which is essential: http://www.hotfile.com/dl/162686792/c693269/P7300ZSKK2_P7300ZZHKK2_TGY.zip.html
- Flash with "Bootloader update" checked in ODIN and see if device is resuscitated. If the tablet boots, it will be in Hong-Kongish, but just select a language you recognize from the dropdown, it has them all.
- It may be a good idea to also throw in a .pit file and check Repartiton
N.B. The firmware link that I have provided is for the Tab 8.9 3G P7300 only! Do not flash it on another version of the 8.9!
You will need to search for a firmware that contains a bootloader.bin.md5 file for your tablet model.
Again, all of this will only be possible if the device registers with your PC on connecting the USB cable.
de3pkeeper said:
1. Put on your computer headphones and turn the volume up.
2. Plug your tablet into your computer via USB.
3. Hold the power button & Vol - keys together (Volume - is the side that is closest to the power button)
4. Listen for the "USB device connected" or "USB device disconnected" sound on your PC
5. If you can hear that, something has gone bad within the bootloader and the display does not initialize properly.
6. If there is no sound, then the tablet is stuck in limbo, so go ahead and do the battery drain procedure as described in the above post.
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
Click to expand...
Click to collapse
Ok, I've disassembled the device, and removed a battery connector for a time.
Didn't help though.
When I'm connecting tab to PC and holding pwr+vol_down, I hear that connect-disconnect sound and there is a device called
NVIDIA USB Boot-recovery driver for Mobile devices blinking in Device Manager with those sounds.
Odin shows no yellow com, all are empty, so download mode is not available.
you are stuck in APX mode , First go to this link and follow the instructions : http://forum.xda-developers.com/showthread.php?t=1130574]
if you get this in nvflash :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
this means your device is locked and the battery draining is that last thing that might work for you .
i still didn't try it, but i only disconnected the battery and connect it again but my device still dead for a month now .
DSHV said:
you are stuck in APX mode , First go to this link and follow the instructions : http://forum.xda-developers.com/showthread.php?t=1130574]
if you get this in nvflash :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
this means your device is locked and the battery draining is that last thing that might work for you .
i still didn't try it, but i only disconnected the battery and connect it again but my device still dead for a month now .
Click to expand...
Click to collapse
I'm getting exactly what you posted:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
and right after that tab disconnects from pc and disappear from devices list.
is it possible, that some Samsung Service Center will help me? I think that what I did voids the warranty, but anyway, I'm in Ukraine and getting official support here is almost mission impossible.
Aecidz said:
I'm getting exactly what you posted:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
and right after that tab disconnects from pc and disappear from devices list.
is it possible, that some Samsung Service Center will help me? I think that what I did voids the warranty, but anyway, I'm in Ukraine and getting official support here is almost mission impossible.
Click to expand...
Click to collapse
unfortunately the sbk (secure boot key) for locked Samsung devices is unknown and i was hoping that someone will be able to provide it since it's now increasing problem for 8.9 and 10.1 tabs especially after ics update . actually this is well known mode(apx) with all Nvidia Tegra devices such as acer a100 tablet and asus transformer ee pad but developers there were able to find the sbk for these devices .
if you are covered by warranty and the battery drain method didn't solve the problem you should go to Samsung and good luck . i am not covered by warranty and the only solution i found after connecting Samsung here in Egypt is replacing the mainboard costing almost as a new device (even Samsung couldn't fix it) .
DSHV said:
the only solution i found after connecting Samsung here in Egypt is replacing the mainboard costing almost as a new device (even Samsung couldn't fix it) .
Click to expand...
Click to collapse
Not very reassuring... Hope they will fix mine. I don't see any way to do it by myself.
Aecidz said:
Not very reassuring... Hope they will fix mine. I don't see any way to do it by myself.
Click to expand...
Click to collapse
Sounds like they want to get your cash.
If things went to sh*t software-wise, they can be fixed the same way.
They could just UART into the board and restore the bootloader. I don't have to expertise to do it, but they should have it.
1. Put on your computer headphones and turn the volume up.
2. Plug your tablet into your computer via USB.
3. Hold the power button & Vol - keys together (Volume - is the side that is closest to the power button)
4. Listen for the "USB device connected" or "USB device disconnected" sound on your PC
5. If you can hear that, something has gone bad within the bootloader and the display does not initialize properly.
6. If there is no sound, then the tablet is stuck in limbo, so go ahead and do the battery drain procedure as described in the above post.
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
Click to expand...
Click to collapse
1-7 okay. And device is "NVIDIA USB Boot-recovery driver for Mobile devices", not APX (because i installed special driver).
But nothing happend when i try to enter Download mode.
USB Disconnect > Connect > Pressing power and vol button for ~7 seconds (why 15+?.. So 15 i tried too) > Sound > Pressing V+ 10 times... Nothing glows in Odin.
eskimono said:
1-7 okay. And device is "NVIDIA USB Boot-recovery driver for Mobile devices", not APX (because i installed special driver).
But nothing happend then i try to enter Download mode.
USB Disconnect > Connect > Pressing power and vol button for ~7 seconds (why 15+?.. So 15 i tried too) > Sound > Pressing V+ 10 times... Nothing glows in Odin.
Click to expand...
Click to collapse
I had a broken bootloader and my display was dead the same way all of youse with bricked tabs describe.
It appears that in your case the bootloader is so badly messed up, that a fail-safe kicks in and sends the tab into APX mode directly.
Consider disassembling your device to disconnect the battery, press Power a few times with ti disconnected and keep it disconnected for a minute or so to force discharge of all capacitors, then reconnecting and attempting a reboot.
Disassembly is really easy - get a plastic knife and stick it under the display near the charging port and work your way around the whole unit. The entire display comes out of the back cover. Flip the display around and there you will notice where the battery connects to the main board, unplug the connector.
Have you tried?
And wut i must do after that?
---------- Post added at 11:46 AM ---------- Previous post was at 11:11 AM ----------
Disassemble, disconnect battery, press power, short + and - (on device, not on battery lol)... After that connect battery and connect via usb ... the same. cant enter download menu.(
Will try this > http://forum.xda-developers.com/showthread.php?t=1478361
If wont work - service center
Aecidz said:
I've tried to put a new ROM using Clockwork Recovery 6.0.1.2, during process it stuck for 4 hours and was turned off by power button.
After that tab don't react on power button, on pwr+vol up, pwr+vol down, pwr+ both vol buttons, nothing.
It even doesn't show battery icon when charging - screen is always black.
Any advices?
Thanks in advance.
Click to expand...
Click to collapse
Hi, may I know what new ROM did you flash? And your previous ROM before flashing. So that we can all avoid that ROM until somebody can fix this mess cause by brickbug. Thanks.
Nah. Samsung service sucks.
They said that motherboard should be replaced.
I don't understand how software problem couldn't be fixed w/o hardware replacement.
Screw that, I'll go get Nexus 7.
nexus_g said:
Hi, may I know what new ROM did you flash? And your previous ROM before flashing. So that we can all avoid that ROM until somebody can fix this mess cause by brickbug. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1789464 <- that one. Version with N7UI (Build 11 Beta 9: (link) (Stable Build)(N7UI))
Not sure if it's ROM problem though.
Maybe it's just my karma.
Aecidz said:
http://forum.xda-developers.com/showthread.php?t=1789464 <- that one. Version with N7UI (Build 11 Beta 9: (link) (Stable Build)(N7UI))
Not sure if it's ROM problem though.
Maybe it's just my karma.
Click to expand...
Click to collapse
Actually it turns out to be the problem with CWM 6.0.1.2. You should use 6.0.0.8 or less.
manpete said:
Actually it turns out to be the problem with CWM 6.0.1.2. You should use 6.0.0.8 or less.
Click to expand...
Click to collapse
too late anyways.
but thanks for the info.
de3pkeeper said:
I had a broken bootloader and my display was dead the same way all of youse with bricked tabs describe.
It appears that in your case the bootloader is so badly messed up, that a fail-safe kicks in and sends the tab into APX mode directly.
Consider disassembling your device to disconnect the battery, press Power a few times with ti disconnected and keep it disconnected for a minute or so to force discharge of all capacitors, then reconnecting and attempting a reboot.
Disassembly is really easy - get a plastic knife and stick it under the display near the charging port and work your way around the whole unit. The entire display comes out of the back cover. Flip the display around and there you will notice where the battery connects to the main board, unplug the connector.
Click to expand...
Click to collapse
My tab was bricked and I followed your post but there is ghost, my tab is still on after 4 hours without the big battery, the secondary battery is so strong (I dont know where its placed)... I dont know how to drain it fastest.
the big battery connector are 5 wires, 2 red, 1 blue and 2 black, are they????
de3pkeeper said:
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
-open ODIN 1.85 and see if it shows a connected device. If your PC made a connected sound, then there will most likely be a yellow COM port in ODIN.
- Hold [Power] & [Volume Down] together for 15 seconds or longer whilst monitoring your Device Manager windows to see if you can get the tablet out of APX mode and have it appear as another type of Device. Then press Volume+ several times with 1.5 sec. intervals. With luck, this should get you into Download mode, and ODIN will shine yellow for you.
- While doing all of the above keep your headphones on and listen for connected or disconnected sounds from your PC.
- Make sure you have this firmware for the P7300 which contains a bootloader, which is essential: http://www.hotfile.com/dl/162686792/c693269/P7300ZSKK2_P7300ZZHKK2_TGY.zip.html
- Flash with "Bootloader update" checked in ODIN and see if device is resuscitated. If the tablet boots, it will be in Hong-Kongish, but just select a language you recognize from the dropdown, it has them all.
- It may be a good idea to also throw in a .pit file and check Repartiton
Click to expand...
Click to collapse
My tab has a blank screen and went through the steps you mentioned. ODIN has a yellow com port and when I try to flash the firmware+bootloader ODIN stops in "SetupConnection".. I tried to change port, cable, odon version to no avail. Any ideas? Thanks!
Related
Hi all,
I was flashing between Jf6 and JH7 today, wanted to see if flashing JH7 via different methods would give me a 3 button fix. (If it did fix it then flashing via Kies mini didn't do the job)
Ironically it backfired when Odin froze and I flipped out the battery
(Hey, I've been at the dl screen before when it was doing nothing and it survived!)
I plug the USB in, I get the exclamation screen
Do it with volume keys pressed, still get it
Hold down the volume + power and the screen goes blinking between exclamation and blank. I've tried releasing power keys at each point in those screens
I even took a video incase I'm not doing it right. Odin is running in the background. No USB plug-in 'pings' from Windows, as you can hear.
Anything I can do?
btw my bat build date is 8/13.. that bad week
I'm in Australia (bought phone off ebay) so sending it back to the States will be a bit of trouble.. I'm hoping I can work something out with the ebay seller otherwise I'll buy another cappy and hope someone finds the jtag points I guess.
same here. no button combo method that previous worked is working now. :/
OP, did you see this thread: http://forum.xda-developers.com/showthread.php?t=775911
not working for me, but maybe it'll help you ... ?
Tremere said:
Hi all,
I was flashing between Jf6 and JH7 today, wanted to see if flashing JH7 via different methods would give me a 3 button fix. (If it did fix it then flashing via Kies mini didn't do the job)
Ironically it backfired when Odin froze and I flipped out the battery
(Hey, I've been at the dl screen before when it was doing nothing and it survived!)
I plug the USB in, I get the exclamation screen
Do it with volume keys pressed, still get it
Hold down the volume + power and the screen goes blinking between exclamation and blank. I've tried releasing power keys at each point in those screens
I even took a video incase I'm not doing it right. Odin is running in the background. No USB plug-in 'pings' from Windows, as you can hear.
Anything I can do?
btw my bat build date is 8/13.. that bad week
I'm in Australia (bought phone off ebay) so sending it back to the States will be a bit of trouble.. I'm hoping I can work something out with the ebay seller otherwise I'll buy another cappy and hope someone finds the jtag points I guess.
Click to expand...
Click to collapse
You may also want to try removing and then reinstalling the Samsung USB drivers on your PC.
I've verified there is simply no USB device being registered no matter what OS, the phone is just sucking power.
@The_Bishop: Did see that, exactly the same as yours, plug usb in, get that screen
Anyone want to be awesome and send my Capppy back to Samsung on my behalf?
best method that never dies when i was in your situation......
unplug usb, turn phone off, then put battery in, turn odin on, now hold volume buttons ONLY then insert usb in phone, you will see download mode with odin identifying the port;
hope it worked ?!?!?!?
Believe me I have tried everything. There is simply was and still is no way to enter recovery or download mode on this phone. Its hardware locked!
a little off topic, but how do i find my phones "bat build date" ?
I had the exact same problem. If you do a battery pull.. hold down both volume buttons and plug the usb cable into the phone while it's hooked to PC then it bumps you into Download mode. I did the exact same thing you did and am running froyo at the moment.
Oh.. no power button.. just both volume buttons.
YoungGun821 said:
a little off topic, but how do i find my phones "bat build date" ?
Click to expand...
Click to collapse
Is on the underside of the battery, one facing into the slot.
i.e 2010.08.13
terrigan said:
I had the exact same problem. If you do a battery pull.. hold down both volume buttons and plug the usb cable into the phone while it's hooked to PC then it bumps you into Download mode. I did the exact same thing you did and am running froyo at the moment.
Oh.. no power button.. just both volume buttons.
Click to expand...
Click to collapse
Done that. Exactly what happens in video. Both volume buttons down, plug in usb.. no response, just brick screen.
I had the same problem.. the phone didn't register USB.. have you rebooted the computer? I believe i did that at one point.
terrigan said:
I had the same problem.. the phone didn't register USB.. have you rebooted the computer? I believe i did that at one point.
Click to expand...
Click to collapse
I did try once or twice. From another thread it was also said to disable driver verification on windows startup for x64 machines. which I also did.
Basically I want to hear from someone who:
a) has a captivate that could never enter dl/rescue via buttons, only adb
b) captivate didn't trigger a plug in 'ping' from Windows until they ??
FYI this is a Macbook Pro, and I booted into Win7 x64 Pro for flashing.
Hi I have the same problem..
What I did was this rooted with one click.. loaded Cognition 2.1.6 all was good..I saw the froyo so I thought lets try it. so opened up ODIN put it in recovery mode. with ADB could never get it in the button way.. it started to load and it froze. I didn't disable voodoo and IS THAT WHY I AM STUCK? I have tried every combo changed drivers computer will not see the phone.. is it a AT&T Phone
IS there anyway to fix it?? or can someone make a program to fix this? I would make a big donation if they did!!!
Thanks Forum!!
Yeah I had it in adb mode to enter download mode, maybe that is why it won't start back up.
I've now given the phone to a local mobile repair business, if riffbox or someone comes out with a Captivate rescue soon its probably as a end result of me
I sent mine back to Samsung as well. BTW, I have a battery from 2010.08.12 so I might be in the same boat. Wish I'd have used one of my OEMs to see if that made any difference, but I did not. :/
I have the same issue.
Rooted my phone through adb, which was fine. Couldn't get into recovery/download modes with hardware before then.
Now my phone is bricked, and not detected or even charging via USB.
wtf
If the repair shop cant fix it try this:
1.) Remove Battery, SIM Card and External SD
OR
2.) Press and HOLD VOL UP AND DOWN with USB inserted and THEN slap in the battery.
This worked for me, for some reason inserting the battery last did the trick.
Let me know if anyone finds a solution to this I have tried it all and my computer will not detect my phone. Has Samsung blocked this in there firmware?
Did you try what I posted above?
yep nothing if I could get it to detect in command prompt I could force it but it won't... the button thing didn't even work when the phone worked!
So ....
OK, I've been reading here for 6 days all manner of Captivate unbricking. Here is my story...
I picked up a Captivate on the Rogers network. I connected it to my email server (Exchange 2010) with no problems, poked around, noticed the lag, noticed the SMS time issue, then promptly rooted, installed clockwork, and then threw cognition 2.2 beta 9.1.3. Quite frankly I was shocked at how much faster it was.
Anyways, after a day of poking around, I could not get my email to my exchange server running (tried the email.pak floating about), so I actually decided I was going to go back to the backup I made of my phone using clockwork before I installed cognition. When I restored my backup, I thought I had bricked my phone.
I let it rest for a day, then came back here, and found one of the 3-4 different variations of the 4 button download mode combo that permitted me to do the 1 click restore. This restored me to the AT&T version of 2.1. It worked, but was less than desirable.
I decided that at that point I really wanted to go back to stock, so I downloaded the stock backup on the Rogers Captivate wiki page, and did the restore using clockwork. The phone has not been the same since.
When i turn it on, I get an at&t splash screen, then in about 20 seconds I get the at&t "jingle", but the splash screen stays on. I can't seem to find any key combination that will permit me to get back into download mode so I can restore using the One Click that worked for me the first time. I have tried:
1. 3 button salute with USB in first, battery out initially.
2. 3 button salute with USB plugged in *as* I was inserting the battery.
3. Power and volume down (both with and without USB, and with battery being plugged in after USB and "during" insertion of battery)
4.Power and volume up with same combo's as #3.
5. Just volume up and volume down with same combo's as #3.
In all cases Odin was running before USB connected, running as administrator. I'm running 64bit windows, but I'm sure I have the correct drivers because I did this the first time with Odin and download mode and I haven't added or changed anything. But just for arguements sake I did uninstall, and then install the drivers again.
Any combination of power and volume buttons just gives me a battery charging logo. Occasionally when holding up until the second black screen I will get a quick indication that the computer might see something, but it dissappears withing a handful of seconds showing it promptly removed.
I'm downloading the Android SDK in the hopes that when I get the normal at&t splash screen after the "jingle" that something might actually be running in the background and maybe I can adb reboot download it but I'm not holding my breath.
Anyone seen this that has managed to get out of it? I'm starting to think the "unbrickable captivate" can be bricked. Assuming it is bricked, short of taking it back, is there anyone on the internet that can jtag these and in some fashion bring back to life?
Cheers,
Tim
This doesn't belong in Development.
MikeyMike01 said:
This doesn't belong in Development.
Click to expand...
Click to collapse
ditto
and download mode is easy.
1. start odin3 and have data cable plugged into the computer
2. insert proper files if needed
3. hold volume up and volume down for 2 sec (no power button needed) then insert usb cable, continue to hold volumes till either the download mode screen pops up or odin3 sees the phone(if you bork the phone bad enough you can corrupt the download mode image, i did it with the not to successfull manhatten project kernel) but despite the screen being black it very well may be in download mode.
4. start flash
5. if it doesn't work send it to me ill find a use for it
alternatively if the phone can go passed the splash screens and boots fully you can adb reboot download. just get the development kit and drivers on your pc.
Dani897 said:
ditto
and download mode is easy.
1. start odin3 and have data cable plugged into the computer
2. insert proper files if needed
3. hold volume up and volume down for 2 sec (no power button needed) then insert usb cable, continue to hold volumes till either the download mode screen pops up or odin3 sees the phone(if you bork the phone bad enough you can corrupt the download mode image, i did it with the not to successfull manhatten project kernel) but despite the screen being black it very well may be in download mode.
4. start flash
5. if it doesn't work send it to me ill find a use for it
alternatively if the phone can go passed the splash screens and boots fully you can adb reboot download. just get the development kit and drivers on your pc.
Click to expand...
Click to collapse
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
MikeyMike01 said:
This doesn't belong in Development.
Click to expand...
Click to collapse
Could a moderator move this to Captivate General then? Sorry about that...
timmy22 said:
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
Click to expand...
Click to collapse
just to be clear, you are holding volume up as well as volume down starting with the phone being powered down and continue to hold them after you plug in usb untill something shows on the screen?
if your phone is not seeing the volumes buttons you are one of the very unlucky few that had a problem at the most inopportune moment.
there is also a way where you hold all three buttons till the phone reboots twice, or something. let me try it and ill give more specifics.
timmy22 said:
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
Click to expand...
Click to collapse
Pull the battery, open odin, plug usb into computer, hold vol up and down, plug usb into phone still holding vol buttons, drop in battery still holding vol buttons, when dl screen pops up and yellow com port lights up in odin release volume buttons. Do not touch power button at any time
Swyped...and sorry I don't proofread
Have you tried rebooting into recovery mode instead of download mode? Stock recovery is adb-ready and you should be able to adb reboot download. Its a long shot if you're having problems using button combo to get to d/l mode, but it's probably still worth a shot at this point.
If you were able to use 3 button combos before all this happened, and did NOT have to install the 3 button combo fix, its strange you don't have access to it now... Could restoring a Rogers Cappy to AT&T stock be the problem?
Dani897 said:
just to be clear, you are holding volume up as well as volume down starting with the phone being powered down and continue to hold them untill something shows on the screen?
if your phone is not seeing the volumes buttons you are one of the very unlucky few that had a problem at the most inopportune moment.
there is also a way where you hold all three buttons till the phone reboots twice, or something. let me try it and ill give more specifics.
Click to expand...
Click to collapse
Yes, that's exactly correct. I do this:
1. everything pulled (battery, USB, sim, sd)
2. Open Oden (1 click)
3. Install battery
4. hold down (and keep holding) volume up and volume down
5. insert USB cable
6. depress (i.e. don't hold) power button
Goes straight to battery charging indicator.
If I swap #6 with holding the power button down, it continually reboots while just barely showing the battery charging indicator. I've tried letting go between black screens on the 1st, 2nd, 3rd, 4th, and 5th black screen. Still no android dude with the shovel.
Try all the steps you stated but not the last one where you press the power button. Don't press the power button.
newter55 said:
Pull the battery, open odin, plug usb into computer, hold vol up and down, plug usb into phone still holding vol buttons, drop in battery still holding vol buttons, when dl screen pops up and yellow com port lights up in odin release volume buttons. Do not touch power button at any time
Swyped...and sorry I don't proofread
Click to expand...
Click to collapse
Goes straight to battery charging.
johnny13oi said:
Try all the steps you stated but not the last one where you press the power button. Don't press the power button.
Click to expand...
Click to collapse
Goes straight to battery charging.
Pull out battery for 10 seconds, hold volume up + down, connect usb into other usb port.
Sent from my GT-I9000 using XDA App
Seriously, try adb. It works wonders.
Sent from my SAMSUNG-SGH-I897 using XDA App
10tonhammr said:
Have you tried rebooting into recovery mode instead of download mode? Stock recovery is adb-ready and you should be able to adb reboot download. Its a long shot if you're having problems using button combo to get to d/l mode, but it's probably still worth a shot at this point.
If you were able to use 3 button combos before all this happened, and did NOT have to install the 3 button combo fix, its strange you don't have access to it now... Could restoring a Rogers Cappy to AT&T stock be the problem?
Click to expand...
Click to collapse
Trying to get into recovery mode gets me the at&t logo and the "jingle", but no recovery mode menu to reboot, etc.
This is what I'm worried about, restoring the Rogers stock over top of the Odin 1 click restore (which is an AT&T image) has bricked it and prevents download mode from invoking.
fatttire said:
Seriously, try adb. It works wonders.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I know, I played with adb before I bricked it. ADB needs to "see" the phone, it no longer sees it (I have three computers, all three can't see it, but they can see my friends cappy with no problems first time, every time). Same process for his phone works every time to get into download mode, but not on mine.
And yes, have tried other USB ports on the same computer, both on the mainboard, and on the front ports.
Keep the ideas coming though please, I will try every one.
timmy22 said:
I know, I played with adb before I bricked it. ADB needs to "see" the phone, it no longer sees it (I have three computers, all three can't see it, but they can see my friends cappy with no problems first time, every time). Same process for his phone works every time to get into download mode, but not on mine.
And yes, have tried other USB ports on the same computer, both on the mainboard, and on the front ports.
Keep the ideas coming though please, I will try every one.
Click to expand...
Click to collapse
There's a trick to prompt download mode through a "jig" which you can hack together for about $2 in parts and a sacrificial microUSB cable...it works on the other SGSes, but I think it should work on the Captivate as well. Never tried it personally...
Merlin_reloaded said:
There's a trick to prompt download mode through a "jig" which you can hack together for about $2 in parts and a sacrificial microUSB cable...it works on the other SGSes, but I think it should work on the Captivate as well. Never tried it personally...
Click to expand...
Click to collapse
I work in a tech shop so have access to electronics, sacrificial cables, soldering irons, resistors, caps, etc.... could you point me in the right direction?
Oh, nevermind, found it in the i9000 forum. Will test first thing in the morning!
Cheers,
I bricked one today as well. Exactly what you are talking about here. The only thing is that i was still under the 30days so i swapped it out for a new one. As of right now ive been debating whether i want to do the voodoo fix (which i think is what bricked it to begin with)
Ok, so I had my Captivate flashed back to stock and had it rooted. I decided to update from JF6 to JH7 through Kies Mini. After it finished updating, my phone was stuck at the Samsung Galaxy S screen and then it turned black, but the buttons still light up.
I already tried doing the 3 button recovery/download mode in every way possible, but my phone won't seem to go into recovery mode or download mode no matter what I do.
When I leave the usb cable plugged into the phone as I turn it on, my computer plays the notification sound where a device has been connected, but still black screen on the phone. Happens when the AT&T screen loads, wonder if that would help somehow
Please help!
Raeon said:
When I leave the usb cable plugged into the phone as I turn it on, my computer plays the notification sound where a device has been connected
Click to expand...
Click to collapse
If you had usb debugging enabled you can send a "adb reboot download" or "adb reboot recovery" command to reboot the phone. If not then you probably have to make one of those usb jig's with the 301k resistor.
But you should still be able to enter download mode if you pull the battery, press the vol up/down and put the battery back. My stock phone couldn't enter recovery but it could get into download mode, keep trying.
Hmmmm. Still doesn't work when I pull out the battery, plug in the usb cable, hold the volume + and - down, and put the battery back on. It just shows the battery charging.
i have something similiar just have battery showing and wheel spinning when connected to pc or AT&T logo flashing if powered on and can't get into download mode...How does one get back to reality at this point.
your phone does not have the button combinations required to enter either download or recovery mode. I guess what you should have done before doing anything to your phone was test the button combinations in case something screwed up. then you should have flashed stock with the odin package posted in the development forum with the 3 button fix. I had to do this for my friend's captivated after realizing the button fix was disabled, but I hadn't broken the booting of the phone then. but now to fix it, other than trying to use adb to reboot into download, I have no idea what to do.
Looks like you'll need to make a JIG. Here's one thread on it:
http://forum.xda-developers.com/showthread.php?t=841512
norcal einstein said:
Looks like you'll need to make a JIG. Here's one thread on it:
http://forum.xda-developers.com/showthread.php?t=841512
Click to expand...
Click to collapse
Made a jig with parts bought from Radio Shack.
the jig was a success to get the phone back to download mode
Hi,
So I have 2 Captivates here with me, one is running on AOKP Milestone 6, and is recognized just fine by the PC, so we can rule out drivers issues
On the other hand the other captivate had eclair, so I got into download mode, and used a one click Odin package to KK4, after that I can't get in anyway to Download mode, I nevertheless can go into stock recovery. I should note too, that I have a jig that is working with captivate1 but not with captivate2, like I said, it is not going into download mode, screen stays black.
Whenever I try to get it connected to the PC, a pop up on the PC says (roughly translated): "that one of the USB devices linked to the computer ididn't worked correctly and Windows couldn't recognize it. click on this message to get more info on how to solve this problem".
After I click on it, a windows with the title " USB device not recognized" is shown and listed is what I know is supposed to be my captivate but instead it says "unknown device".
If I insert the battery the device would turn on, no need to press the power on button, but if I shut down the device, I can't turn it on with with the power on switch, I have to reinsert the battery, in other words it's like the power on button is stuck, I don't know how to verify this, and I don´t know if this is what is causing me the problems, though I dont think so. Power on behaves just fine inside recovery or with the device turned on.
I can charge the device with the PC or with wall charger just fine.
Thanks
Probably the power button as you suspect... They have problems with the power button, so I have heard.
But what about the usb not being recognized, and I should also add, that it intermitently gets recogonized and when it does, it gives the message I typed on the OP. Could the power button affect to this extent?
Is there anything that can be flashed from 3e recovery (from KK4 update)??
Nope. Stock recovery is very constrictive.
Hello for Everyone!
I've a SAM Galaxy TAB 8.9 (GT-P7300) branded for T-Mobile (TMH). There are few of strange things about it.
The first: can not communicate with my PC and with my laptop. On PC runs WIN7 x86, on laptop I use Ubuntu 10.4 (Studio). I had installed the USB drivers for WIN, and the only thing is happened after plugging the USB-cable WIN wrote: "Can't identifying the plugged in Android device". The Ubuntu doesn't recognize my tablet
The second: I can not reach the Bootloader mode, download mode. When I push the VOL down at same time with the POWER ON nothing happens.:crying:
The third: after some minutes of sleeping mode of the device (for example: charging, not using) it POWER OFF. Or...something like this...blank black display and nothing happens if I push any of the buttons. Pushing about 20 secs of POWER ON button resulting a reboot.
The device is in stock 3.2 .
Any ideas what can I do for rooting process nad for custom ROM?
simpleimage said:
Hello for Everyone!
I've a SAM Galaxy TAB 8.9 (GT-P7300) branded for T-Mobile (TMH). There are few of strange things about it.
The first: can not communicate with my PC and with my laptop. On PC runs WIN7 x86, on laptop I use Ubuntu 10.4 (Studio). I had installed the USB drivers for WIN, and the only thing is happened after plugging the USB-cable WIN wrote: "Can't identifying the plugged in Android device". The Ubuntu doesn't recognize my tablet
The second: I can not reach the Bootloader mode, download mode. When I push the VOL down at same time with the POWER ON nothing happens.:crying:
The third: after some minutes of sleeping mode of the device (for example: charging, not using) it POWER OFF. Or...something like this...blank black display and nothing happens if I push any of the buttons. Pushing about 20 secs of POWER ON button resulting a reboot.
The device is in stock 3.2 .
Any ideas what can I do for rooting process nad for custom ROM?
Click to expand...
Click to collapse
On your second point, to reach bootloader, turn on tab, wait until the moment the samsung logo pops up, then press volume down (the one closer to power button).
To root, add custom recovery and ROM, read the stickies in the android development forum. These may help your other problems. There are several reasons why your computers fail to recognize your tab. I would try different usb ports and cords if you can. I would install kies on the windows pc and see if that recognizes the tab. If none of that works, it may be a hardware problem.
upconvert said:
On your second point, to reach bootloader, turn on tab, wait until the moment the samsung logo pops up, then press volume down (the one closer to power button).
To root, add custom recovery and ROM, read the stickies in the android development forum. These may help your other problems. There are several reasons why your computers fail to recognize your tab. I would try different usb ports and cords if you can. I would install kies on the windows pc and see if that recognizes the tab. If none of that works, it may be a hardware problem.
Click to expand...
Click to collapse
Thanx for your quick reply. There are few cganges about the problems. Here they are:
The second problem about the bootloader and download mode is off. I picked parts of the device and there was a liitle problem with the VOL buttons...repaired and everything is fine with it.
The first problem about the communication is half-solved. On SAMSUNG laptop without (!!!) any drivers works fine the device. Flashed with a "stock" 4.0.4 (Checz) no boot, just splashed on the SAMSUNG logo. After ODIN-flashed one-file other ROM it was very nice...everything goes.
But the third problem is here after the good-flashing, too. In sleep mode or long not-usage periods it is something like POWER OFF.... During the picking to parts period some of the pieces (battery, flexes) were supervised...everything is normal. I think the device's main panel is wrong, but I don't know how I could look at it and fix it.