I was flashing apex overtop of fastyIII rom instead of reverting to stock prior to the new rom. duh. lesson learned...
here's the symptoms now:
i can see the device with adb, it shows the imei serial no problem.
i can't use any of the button methods to get into download mode, the device will just try to boot normally.
i can't boot up to change anything, instead the phone constantly reboots to an at&t world edition logo, then cyanogen bootanimation, then repeat.
if i put in the usb cable with the volume buttons depressed i get the depleted battery logo indicating it would charge, but it doesn't. This is when adb will recognize the device.
Issuing an adb reboot download command will indeed reboot the phone, but no download mode.
a USB jig that i made doesn't seem to do anything at all. 300 K Ohms resistance and it doesn't even trigger a normal boot.
My phone is the canadian-rogers i896, the last stable rom running was 2.1 at&t stock.
I'd like to either soft-brick the phone (via adb) so i can get back into download mode or troubleshoot the setup i have in some other way i dont know. Any help would be greatly appreciated!!!
can we close this thread please?
just found other open thread with similar issue: http://forum.xda-developers.com/showthread.php?t=1294555
i guess close this one if required, will now post in other thread.
Related
Hi,
I want to say that everyone is very helpful in this forum and you all rock. I'm having some problems with my rooted samsung captivate. I installed the I9000 Full rom, and it was running fine for a few days then I notice it was very sluggish, so I did a factory restore, but data and apps didn't delete. So I then when in to recovery (R2) and deleted cache and all user data files, then it did a factory restore, and it went in boot up pass the att and samsung S i9000 screen and when to the lock screen, but once I unlock the phone, its just in the black screen, when I click and hold on to the home button it goes to recent, no recnet application and under Task Manager, I have 0 active applications. It won't load any programs or apps. I tried restoring the phone by holding the down volume key and power on button, it goes to R2 recovery and then reinstall package, but it can't find the package. I have it on the memory card, but I guess I deleted it from the internal memory when I did a factory restore. Am I screw, or can someone guide me through this and fix my fone. Thanks in advance. XDA Rules.
Odin one click back to stock, assuming you can get into download mode. Also do a master clear just to be sure. A fresh start might be just what your Captivate needs.
Sent from my SAMSUNG-SGH-I897 using XDA App
The same thing happened to me yesterday. Phone was on, battery fully charged. I got on my flight and left it on (forgot I guess) and when I got off the flight, the screen was black. I'll also add, that over the past 3 days the phone was starting to get extremely sluggish (for no reason that I can think of). But back to the rest of the story...
I couldn't get it to turn on, so I pulled the battery and tried again. This time I got the AT&T logo and the Samsung animation. Once the animation was completed the screen goes black.
The phone is still on. How do I know? If I touch any of the bottom buttons they light up.... and stay lit up until I do a battery pull.
Deleted/cleared everything, same behaviour.
I tried reflashing JI6, it works but fails to reinstall the packages, otherwise same behaviour.
I tried reflashing JF6, same behaviour.
The flashes always succeed, but always end up in failure.
Now for the interesting part. I went into recovery mode on JI6. I try to format the internal /sdcard, I get a message that it cannot mount /sdcard /dev... not found.
So to recap, phone not working, recovery mode available, download mode available. adb doesn't seem to be working, but if someone can tell me how to access the phone with "adb shell" while in recovery mode, I might be able to diagnose why /dev... is not mounting... Or at least how I could fix it using adb.
Any help would be appreciated. I'm traveling and needless to say, this is a huge inconvenience, I'm lucky I had my backup phone to at least be able to get online and be able to make calls.
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
hksmr2 said:
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
Click to expand...
Click to collapse
the shovel is NOT recovery mode, it is download mode.
have ODIN running BEFORE you get your phone in download mode
OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?
OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.
Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...
Hello,
I was previously using LG True version 0.6 ROM but wanted to go back to stock.
So I used it via the NVFlash way, half way through it putting it back to Stock, I accidentally unplugged my device thinking it was finished, now my phone won't boot up. Whenever I try to re-flash it with NVFlash the CMD auto shuts off with a message I can't read since it's that quick at shutting off when trying.
I have tried restoring via Smart Flash but that doesn't work (Tried holding vol down & plugging in but doesn't populate anything).
My phone won't boot.
I've tried re-installing the NVidia drivers, same issues.
The NVFlash gets the different stages before failing (Usually it gets to the point where my phone goes into S/W Upgrade mode, then fails)
I cannot get into S/W Upgrade mode to restore via Smart Flash as nothing happens.
Device manager picks up the phone as an NVidia USB Recovery device.
I appreciate any help as I'm lost without my phone.
Step-by-step guides are preferable since I'm new to flashing etc.
The phone is in download mode.
You need to find a way to send the rom to the phone, so the phones downloads the rom again and starts working.
Try pm'ing Paul over Twitter.
This is fixed now.
Unsure why, but trying a different USB port enabled me to use NV Flash and now booted up fine.
Thanks anyway guys and sorry for wasting your time.
Hi,
I've flashed multiple times before without an issue until today.
First, here's my background information:
Samsung Captivate (ATT)
Was running Continuum 5.4.1 but it felt laggy so I attempted to flash MIUI 1.5.13.
Here's what I did:
I wiped my phone using the Odin One click tool, then flashed CM7's kernel and then performed formats of the cache, system, and data, then installed MIUI RC2. After this step the phone should have restarted, then I planned to shut it down and reboot into recovery and flash 1.5.13 onto it.
My problem(s):
-Boot into recovery/download mode using key combinations is not working.
-The ADB console reports device not found when I try to run adb shell.
-The phone is undetected in Droidexplorer.
-When I attempt to download an app to boot to recovery with the phone says there is no space even though nothing has been installed other then MIUI.
What I would like to do:
Get back to stock with download/recovery modes working.
On a side note: MIUI works, but in a very limited way. I can navigate through it, but it won't allow the installation of applications due to there not being room on the phone (as said before).
Thanks!
Update - my phone was being identified as a Nexus S, so without those drivers my phone could not be debugged via USB. I now have the drivers and can perform ADB commands, however rebooting into recovery and into download mode both result in the phone restarting without going to the download or recovery mode.
Try using ODIN and repartitioning. I have good videos on standard ODIN and Heimdall on YouTube just search them. If you can not get out of this contact me, I have been able to partition debrick in the past and it's actually considered by me far more annoying than standard bootloader JTAG in certain situations. Let's hope yours is easier to bail out of!
First of all thanks for the reply and direction.
Secondly:
After working on this all last night I was able to get the phone recognized by Odin and my computer, now I am stuck at one of two screens depending on what I do.
If the phone is powered off then plugged in, the battery charging screen appears but there is no animation and after unplugging it the battery charging image remains.
If I power the phone on it hangs on the Samsung boot screen.
Repartitioning does sound like the proper direction for me to take, but, when I use Odin it freezes while setting up the connection to the phone.
when the phone is powered off try holding both vol keys and plugging in the cable. That could possibly get you to download mode. If not try vol down/pwr at the same time since you are now on GB bootloaders the keys are a bit different. Let me know what happens and good luck
maybe you should try to build a jig and use it to get into the download mode first. or you can buy it on ebay, just search for "micro usb jig".
I've tried every volume and power combination possible to no avail, I can't get into download mode. I've given in and am exchanging my phone. Thanks for the help anyway guys!
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.