HELP needed. - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi all.
I was a happy flasher till about an hour ago. In my 5 weeks of Galaxy use, many of you have made me feel very good about buying this mobile by drastically omproving the performance. I went from standard India version to DDJG4, the JPC, the JPK, then JPM & finally settled down on Sztupy's Highly experimental 0.1 which was a SUPERB ROM. Then I went & did a blunder. I downloaded docs experimental with Sztupy's fix & tried to flash it via CWM. I went into Rom Manager, selected Install from, selected the test5.zip on my internal sd card, it asked me if I wanted to do a backup & wipe data etc. I didnot do a backup but said wipe, & went ahead. It restarted, went into clockwork recovery & about 5-6 lines later, said something wrong on line 4 & said failed & a log was created at such & such a place & shall I reboot? The home button did not work, so I pulled the battery pushed it in & tried to start, I get the white Galaxy S logo & it doesn't go ahead.
The vol-up + menu + pwr, doesnt put me into recovery. vol-dn + menu + pwr puts me into download BUT the phone isn't recognised by the computer, says the usb device isnt recognized or some such thing & Odin cant recognise it.
I have tried it on two computers.
Please somebidy HELP ME.

Related

USB/Charger reboot the phone, download mode lost, vibrant rom on i9000

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...

[Q] Phone black screen at boot, no buttons work for booting.

Hello there, nice people of these forums
Yesterday my phone randomly wouldn't boot anymore. I was on an ICS ROM I had just flashed the day before, so it wasn't that much of an issue though. I just thought I'd reflash a stock ROM via Odin and that all would be well again.
Here's what happened:
- I flashed with the PDA, Phone and CSC boxes checked (and yes, I've got the right files in the right places).
- I flashed with a .pit file I've used countless times before
- I flashed with the repartition box checked (also tried it a few times without, actually).
So after this, my phone reboots, and goes straight into ClockworkMod Recovery. When I try to install a zip from the SD card (another ROM) OR choose the "reboot system now", option, it doesn't matter which I choose, it just goes off (or boots into a black screen, I can't tell).
When I then try to manually reboot the phone by holding the power button, it doesn't do anything (I've reinserted the battery lots of times). Also, my 3-button-combo for the recovery menu isn't working. The only thing that's working is my download mode.
Would you please help me with this problem? Thanks!
EDIT: While I have no idea how I did it, I seem to have fixed my phone. It now boots again and everything works flawlessly. Thanks for your time anyway

[Q] Phone stuck on boot by himself

Before I startת I tried to find this problem also search on Google and here but could not find any information about this problem.
This night I did not put the device to a charger because he had already 90% battery, so I left it disconnected,in the morning I got up I saw the phone is turn off, I tried to turn the phone light up and the ATT screen turn on,
I went and when I came back after 10 minutes I saw that the phone is still stuck on the "Galaxy S" screen.
I removed battery, changed, and it's still stuck.
I'm running version CM7.1,
The phone can get into the recovery menu.
Can anyone help me?
I do not understand in the android system and I don't have any backups of my pictuers...
Any chance to save the phone?
update: I search for a solution, and found on the CWM the option of "Mount USB storage" and I copied my pictures to my computer...
so now my new question is how can I get the phone to turn on again? only format and install new rom?
I can use CM7.2 zip file and install via the recovery menu?
you can go to cwmr and can do a data wipe which will uninstall all your apps and data but will not touch your sdcards
You won't lose your pictures on the sd card. If you are still stuck, try wiping dalvik cache from recovery
Sent from my ICS Samsung Captivate
I have a similar problem. Like eidoll32, I did not plug in my cappy and when I went to turn it on the next day, I was only able to get a boot loop at the AT&T screen. Currently, I cannot get into recovery, but only download mode.
I originally rooted the phone with the Galaxy_One_Click_Root tool, and installed CyanogenMod 7.1 for the captivate, when CM7.2 went to RC1, I flashed that from CWM, doing a full wipe. Later I wanted to try ICS, so I flashed AOKP - captivatemtd - M5 b30, doing a full wipe (twice).
That's where I was when this happened, and where I am now.

[Debricking] Hang at samsung animated logo

Hi everyone, I spent all day trying figuring this out, even if probably the solution was really stupid, so I thought of doing a little post for future reference. If you have no time for my babbling, feel free to go to the short version (I wanted to put a link here, but I still have to learn how to do it and it's almost dinner-time...). If this post happens to be a duplicate feel free to remove it.
=== Whole story ===​A week ago I got a Galaxy SIII mini N (GT-I8190N) and just kept it that way because I didn't had a win pc to use Odin. Yesterday I finally came back to my parents, powered up the win machine and followed an awful lot of different guides to manage to install the Macław CM 10.1. So, for short: installed CWM touch trough Odin, installed the root zip trough CWM and finally installed CM 10.1 & Gapps trough CWM. Here I did my first mistake: the first thing I did after installing CM was formatting internal and external SDs. Where the Nandroid backups of the working Samsung firmware were.
After some experiments I decided to go back to Samsung stock (reason 1: no gtalk, only hangouts, reason 2: NFC support still in development, reason 3: trying to restore SMS from a SmsContactsBackup I (luckily) had I messed up the SMS DB so much the app couldn't start). NOTE: Macław's ROM is amazing, I'm surely going to try it again when NFC support comes up. Sadly, I am an idiot who thinks he knows better so I ignored all the warnings of doing a wipe of data/cache and restoring the Samsung original recovery. I just went to Kies for a "Firmware upgrade and initialization" instead.
The result was a disaster. The phone rebooted but hanged at the Samsung animated logo. After a lot of hanging I decided to redo a Kies firmware upgrade. Obviously I had no luck. So I switched to Odin, took the image Kies downloaded (since I didn't want to wait an hour and an half to the download from unofficial sites) and flashed. And flashed. And flashed. Always without success. After a little bit I decided to try changing Odin options (repartition, NAND erase etc). Still nothing. So I started trying all the guides out there (here?): repartitioned with a PIT file, reflashed a CWM, reflashed stock recovery, various combinations in different orders of all the "solutions" above... You guessed right: nothing worked.
Since I read somewhere that there are Galaxy have 25 partitions (what the ****???) and saw that Odin was flashing only 8 or so I decided that something some the other partitions was missing, so I switched to Heimdall. Since the Win version didn't want to start, I did a fresh Ubuntu 13.04 install (lucky for me I happened to have an empty HD waiting to be installed on the server that I could use for an afternoon ), installed Heimdall, started figuring out how it works, realized I needed a custom-made package (nowhere to be found, apparently), started looking into the partition scheme to understand where the problem could have been... Finally I realized my skills are a tiny little bit inadequate for that and found a reference somewhere to a "hard reset".
In all this it never occurred to me to try and enter Samsung recovery. The first thing I noticed was that it didn't start right away with VolUP + Home + Power, but I had to keep them pressed a lot longer than what it's needed to go in download mode. In practice the SIII mini logo went up two times before showing the android with the open belly. Then finally the recovery appeared, I navigated to wipe data and cache with the volume buttons, accepted with the power button and rebooted. Thus I finally had a Samsung animated logo that was followed shortly by an "installing applications" loading bar and the first start configuration tool.
So, what I learned today:
1) Samsung tools are not necessary evil
2) if you don't understand what you're doing and you're doing it anyway, be prepared to suffer
3) we probably need a unified guide/troubleshoot the whole community can edit (wiki-like). Threads are great, but it's really easy to miss the obvious (for the whole time I was sure it was a bootloader problem, never occurred to me that there could have been some data left... also because I did a NAND wipe through Odin and I thought that was supposed to wipe personal data...) and often propose a solution without explaining the rationale behind it. I'm sorry if there's something like that out there somewhere, I wasn't able to find it
Thanks to you that bore my babbling
And now it's time for:
=== The short version ===​
Problem: I messed up doing a Kies reset after installing a custom rom (CM10.1) without the dues precautions; the result was a phone caught in an endless loop at the Samsung logo. Installing firmware with Odin didn't solve a thing.
Solution: I booted in recovery (volume up + home + power) and wiped data and cache. After that I rebooted and waited a little bit, a progress bar appeared and everything was fine (well phone was at factory default but at least now it's working ).
I hope all of this could be useful to someone

URGENT - Need help with S5570

Hey guys
Samsung Galaxy Mini 5570 is a pretty old device now and definitely not worth to talk about, but It's for my aunt and she said i HAVE to fix it otherwise she will kick my butt.
This is the whole story:
Phone was running a very low android version (it was 2.1 or something) that i could barely install apps on it (Just installed WhatsApp), I decided to upgrade it to a higher version so i could install other applications like Line and Telegram for her, so basically i had to flash CWM file first because it was required, I flashed it using this link:
http://www.droidthunder.com/root-install-clockworkmod-cwm-recovery-samsung-galaxy-minipop-gt-s5570/
They said flash the cwm file and factory reset your phone but i flashed the cwm file and rebooted my phone without factory reset, everything was working fine :good: but i decided to follow the instruction so i rebooted into the recovery mode and factory reseted my phone (by my phone i mean her phone, but i'm gonna say my phone instead) and guess what, it never booted up again. stuck on Samsung logo.
But i could go into the download and recovery mode, so basically i followed this instruction:
http://www.droidthunder.com/update-samsung-galaxy-minipop-gt-s5570-android-4-2-1-cyanogenmod-10-1/
which is from the same guy, I flashed it using recovery mode and flashed gapps too, everything went normal without any errors. So i rebooted my phone and ............
a black screen poped up, I was really worried because i couldn't boot my phone, nor could i go into the recovery or download mode. I don't know if i could or not but the only thing I'm getting right now is a black screen or a backlight.
The only thing that seems to be working is when i hold Power+Volume UP button, my laptop can detect my phone (as Samsung CDMA Technologies) but can not flash anything using Odin, it stucks on "setup connection" message. Nothing else is working, I tried:
Home+power+volume down
Home+power+volume down+volume up
Power+volume down
Power+home
etc
I also tried a hundred different ways like completely uninstalling the drivers (with or without kies) pulling battery out, try those key combination while battery is out and reinsert battery while holding them but nothing is working.
I found this article yesterday which is for unbricking the hard bricked phones, but ADB can not detect my phone:
http://www.engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
Please help me guys, And do not suggest me to take it in Customer Service because i would if i could.
Thanks in advance

Categories

Resources