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
Related
hi people,
I was trying to upgrade my firmware via Kies. However after the completion of the process and reboot, only thing that I could see that black screen with the turning "S".
That was just the beginning, I tried some recovery stuff myself and everything did go worse and worse.
Now my device (i9000s) has 2 options remaining which brings me nothing.
1. vol up +power+main screen ->
update.zip does not work, installation aborts, so I cannot move here.. (partition wiped, factory reset etc done...)
2. vol down +power+main screen ->
downloading.... (brings me nothing)
I downloaded a new "update.zip" from internet and moved it to external SD card and it also brings me nothing.
after I reboot, I get a black screen with Samsung I9000 text, nothing more.
Do you think that I can recover this stupidness of mine?
same problem was posted already in http://forum.xda-developers.com/showthread.php?t=809567.
I dont think that this is my situation
its exactly the same, and I have it too. Meaning the original problem after update.
ok I will try this also,
but I cannot find:
Upgrade Firmware upgrade File (.tar) can be downloaded from Samsung-Firmware.
only thing I see in ODIN:
0:[COM18]
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.
We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419
Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App
Keep hope alive glaze!
Sent using XDA App
Im going to get a jig hopefully all goes well.
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've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom
Hey guys,
i'm in trouble installing a custom ROM on a S4 Active (GT-I9295, Baseband IXXUDOB4, 5.0.1).
Flashed CF--Autoroot with Odin, no problem.
Then i flashed TWRP, Odin showed its green "PASS!"-message but i can't boot into recovery.
I'm well aware of the timing issue when doing the first reboot into a custom recovery, and i assure you this isn't the problem.
I tried countless times, after a while i installed ROM manager to try if i could flash the ROM file that way.
It installed another custom recovery -CWM- on top, and also showed up the TWRP recovery:
http://imgur.com/kSSiuld
Still, booting into any recovery does not work, neither from ROM managers menu or via any button-press combination.
When pressing vol up+home+power, the phone shows the blue "revovery loading"-line AND the red line *****ing about the root, but continues to boot as if it had been switched on normally.
I even looked for the ominous "install-sh" script in system/etc to understand why nothing gets me into recovery-
what the heck can this be?!
Did the same thing to S6 and S5 without any hassle, i'm stuck with this for several days now and i am running out of ideas.
Anyone...?
Not a very technical answer, but have you tried pulling the battery out for 30 seconds and trying again?
Yes we did, unfortunately, this also didn`t help.
Tried loads of things actually, still impossible to access that damn recovery