Hey everyone, new member and my first post and I need help. I have a SGS I9000 and did the same thing as "michaelg117" did in this thread: http://forum.xda-developers.com/showthread.php?t=890987
I installed OCLF and saw it needed to have a rooted phone. I installed z4Root temporary root and when I ran the OCLF lag fix it rebooted and I now have a phone that is frozen on the blank screen after the S animation.
I notice that while sitting at the blank screen I get one buzz followed by three buzzes. I assume that because of not being rooted it's the OCLF failing then being forced closed and then getting stuck in that loop.
I've been searching for any solution. The phone is only a few weeks old and I can recover my contacts from Outlook but I do have a few pics that will probably be lost if they're not already.
Is it possible to re-root the phone so she'll start "normally" with OCLF so I can then remove it and unroot back to normal? I've tried the Galaxy S OneClick Root for I9000 (by TGA Gunnman) but keep getting the following errors:
E:failed to open /mnt/internal_sd/update.zip (No such file or directory) error.
E:signature verification failed
Installation aborted
Does anyone think that being able to root would cure the problem? What other options are there for forcing a root in this condition?
Thoughts?
Thanks in advance.
Well, I ended up booting into recovery mode using ADB then doing a factory reset. Lost my pics but backed up my contacts. At least the phone still works. I think I'll wait for 2.3 to come out before I try to change anything else.
I did the same on mine but i did a recovery too. You can do the permanent one now + OCLF without any problems.
Sent from my GT-I9000 using XDA App
Hi,
I have the same problem you had: z4root temporal + OCLF = Soft Brick.
It was my fault not to check that I had access to download/recovery mode using the three buttons. But fortunately, I had the debug mode enabled and can use adb to reach recovery mode...
BUT, I was advised in another thread _NOT_ to use factory reset in this situation because then I will lose the debug mode so if things go wrong I would not be able to reach download/recovery mode with adb again. They recommend use first a 3 button combo fix instead. This:
http://forum.xda-developers.com/showthread.php?t=821698
In this way, I would not depend on only debug mode for subsequent manipulation. What do you think?
Related
I'd like to start of saying I've read almost every thread regarding this and I understand that there's a good chance that my internal SD is permanently blown up I'd just like to establish some things here that may put me in a different boat.
hatdrawn said:
I just want to be clear ...
So I last night I flashed JPK, PDA/MODEM/CSC with 512pit installed latest oneclick lag fix 2.1.1, SGS tools and other basic apps. Was running perfect all night except that RAM seemed to be eaten up easily.
Then this morning Advanced Task Killer Froyo Beta started acting up. So I tried a reboot and then I got this black screen issue.
Tried reflashing JPK again. Just successfully flashed JH2 but still the black screen.
Recovery/Download mode work. With 2.2 recovery mode I was getting SDCARD connect errors on screen, but since JH2 I don't see them. Tried wiping cache partition, and factory reset. Still black screen. I've tried without external SD and SIM and just recently with external SD.
In this JH2 recovery mode "update media, finished" and Apllying MultiCSC works properly too. When in recovery mode, Kies tries to recognize it, but boot/blackscreen I get nothing.
Is there anything else I can try? I have read through this whole thread, but it's a lot to read and understand. Anything with ADB? When in recovery mode ADB shell returns a device not found
Click to expand...
Click to collapse
Currently it's back on JPK for the time being and using ADB I can finally get it to recognize there is a device, but it says it's offline. What does this mean? Does this mean that it wasn't in debug mode when it crashed? Or something else? At this point does this help me at all. At one point I did get internal and external drives to show up in my computer, but I couldn't acess them. As if they weren't mounted. Actually, that's how it's behaving now.
Can anyone think of anything else for me to TRY at least? I don't want to give up just yet. I realize all signs point to bricked but I just want to try a few more things.
Any tips are appreciated.
Thank you very much
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...
I have a rooted Gt-P1000 it crashed and now right from factory reset it keeps saying process android.process.acore has stopped unexpectedly. I can get onto the internet through going back through the initial set up screen after reset. I can also download something to get a download failed to get to my files. All system files fail to restore.
I have no working menu settings and process android fault constantly appears. I also get process.com.android.setupwizard has unexpectedly stopped. I have searched the internet and found no answers.
I went and bought a new pad only to find z4root does not work any more. And oneclick is an unopenable file!
Hence i have an unrooted pad that is as much use as a chocolate fireguard and a rooted one that is corrupt. The unrooted one is crap as i work in saudi and need to run market enabler, which wont run here unless routed. Please can someone give me an UPTODATE METHOD OF ROOTING, TELL ME HOW TO FIX FAULT, THANX!
Do a hard reset: switch off the tab and boot into recovery by holding volume up and power button. choose factory reset.
NOOB rooting guide: http://forum.xda-developers.com/showthread.php?t=812367
Already done loads of resets, as above - after reset i still have all the above problems!
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.