Database Develop

[Q] Interesting boot loop problem.

2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?

hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?

bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????

I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...

Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?

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

Galaxy S Problems - Need Help Fast!

Ok so I have been looking around for two days now and have not been able to find an answer to my problem. I've even searched and tried everything on these forums so please don't ask me to google or use the forums search.
I've got a Bell Canada Samsung Galaxy S GT-I9000M, it was working fine a few days ago and I picked it up to check my messages and it was frozen. After a few minutes I pulled the battery and went to restart the phone.
The phone will now only show the Samsung Galaxy S white logo and simply restart itself and play that logo over and over. If the phone is plugged into the wall it will show the battle charge logo briefly and than restart to the logo. It will go no further than this point.
I have tried to do a factory reset via Home + Power + Vol Up but it seems to reset itself before it will actually load into that menu. Home + Power + Vol Dn will bring me to the download screen which is stable and will not reset the phone.
This is where it gets strange, I have tried Odin and a 100% stock flash on the phone with no luck the phone just sits resetting. After a download of DarkyROM it will actually load the white Galaxy S logo along with the DarkyROM logo and simply go back to resetting.
So the phone is clearly in some state of a working order able to download and accept ROMs but just keeps restarting itself after the white initial Galaxy S logo.
Any and all help would be appreciated! I hope I have explained this problem well enough, maybe it is in need of being brought to a shop to be fixed? Just happens that the warranty expired last week, almost seems coincidental.
Thanks!

After you installed DarkyRom (or any other ROM with CWM), did you try re-entering the recovery menu? Perhaps you will now be able to enter recovery?

tptp said:
After you installed DarkyRom (or any other ROM with CWM), did you try re-entering the recovery menu? Perhaps you will now be able to enter recovery?
Click to expand...
Click to collapse
No, after the install of the ROM it would load up the white galaxy logo along with the DarkyROM logo and than just go back to resetting itself over and over. I could still go back to to the download but not access the reset menu.

Knagar said:
No, after the install of the ROM it would load up the white galaxy logo along with the DarkyROM logo and than just go back to resetting itself over and over. I could still go back to to the download but not access the reset menu.
Click to expand...
Click to collapse
run through My Android Solutions, link below and do the first step after that to immediately to recovery or download mode , than flash a rescue or resurrection kit from My Android collections, link below, all this done without sim card or exts SD card inserted

None of this has worked, I have tried every trick I can find on the net but I can't seem to get it to go.
As before the phone will go into download mode, will accept roms and so on as shown by the DarkyROM logo showing up and going away with the removal of it.
After every attempt I am still not able to get into recovery mode but am still able to access download mode. The phone seems to be in some state of working order but continues to reset itself only when turned on but will run stable in download mode.
ADB doesn't see the device and even if it did I think it would still just reboot once it started into recovery.
It's almost as if the phone starts and after it shows the starting Galaxy S GT I9000 it just turns itself off for some reason
Is their any way to totally reformat the phone and start 100% from scratch without getting into recovery to do factory reset?
Step by step instructions on what to do and download for Odin would be fantastic. I am still not sure 100% on what the PIT/Bootloader/PDA/Phone/CSC are or do so the files I need to put in those and a good explanation would be great!

This happens sometime. To fix, Do this.
1. Boot into download mode.
2. Flash stock ginger bread with Odin using 512 pit.
3. Now boot into recovery and wipe data/factory reset.
4. Boot again into download mode.
5. Flash devil or semaphore kernel.
5a note. Your phone doesn't need to be able to boot. All we need is recovery mode.
6. Boot into the new recovery and wipe data/factory reset.
7. Format /system.
8. Flash ROM / gapps etc.
9. Boot with success.
10. Happy dance time, brings good luck.
Sent from my GT-I9000 using xda premium

Knagar said:
Step by step instructions on what to do and download for Odin would be fantastic. I am still not sure 100% on what the PIT/Bootloader/PDA/Phone/CSC are or do so the files I need to put in those and a good explanation would be great!
Click to expand...
Click to collapse
ok, try flashing a gingerbread Ezboot loader, visit My Android collections, link below, has complete guide at download page

Well I've tried both suggestions with no luck. I am starting to think it's some sort of hardware problem which I can't understand because it is 100% stable and won't reset in download mode. It will accept ROMs and so on but instantly just starts to restart itself after the first logo is shown. No work around will let me into recovery mode and no method I have found so far will just reload how the phone boots. I guess it's time for a new phone eh chaps?

Knagar said:
Well I've tried both suggestions with no luck.
Click to expand...
Click to collapse
hmm, its strange..anyway, you should remove SIM Card and Ext SD card, and try to use any tool from My Android Collection, to format the Internal SD card and flash a 2e recovery to see , if you can get your recovery back or even a i9000 rescue kit would be good to go after formating your Internal SD card
Formatting you Internal SD card, will resolve any settings, data, delvik cache etc that would be the cause of your initial problem.. there are formatting tools as well a recovery tools that can be used to achieve this

Did u flash the correct stock firmware for ur I9000M? try this http://www.hotfile.com/dl/162558059/7efd7bc/I9000UGKG3_I9000BMCKG3_VMC.zip.html.
Source : http://www.sammobile.com/firmware/?page=3&model=GT-I9000M&pcode=0&os=1&type=1#firmware

Ok progress is being made, first I used Odin to load I9000UGKG3-I9000BMCKG3_VMC in the PDA slot without doing a reboot. Then I loaded JPK_Root_Recovery_2e using just the i9000_Kernel and was able to boot recovery.
After doing a Wipe Cache and then Factory reset the phone went back to a boot loop and I was unable to get back to the recovery menu.
After repeating the first steps I am once again in the recovery mode with no boot loot but am unsure as to where to go from here.
Currently the screen reads
Android system recovery <2e>
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache
-------------------------------------------------
E: Invalid command argument
-- Install from package...
Finding update package...
Opening update package...
# Manual Mode #
--Appling Multi-CSC...
Installing Multi-CSC
multicsc : src /system/csc/BMC/system/ .
*EDIT* Seems once you restart from the recovery mode it goes right back to a boot loop, was not able to apply the SD card update either. So getting to recovery is currently a one time deal without having to go back and reload VMC and 2e. Once restarted all is lost.

You will need to flash another firmware with 3 file method @odin. Search on this forum a firmware and flash it!
Don't worry, u can't brick your phone that easily. I flashed my phone 10times in a day, for boot loops, when i tried to upgrade to 4.0.4
Sent from my GT-I9000 using xda premium

Ok so this time I used Odin to do VMC in the PDA slot, then I9000 Kernel went back to VMC and loaded that then when I restarted the phone it went back to the same boot loop.
I have no way to clear the internal SD or anything like that because the programs will not see my phone connected to my PC.
What could be causing my phone to just continue to restart?

Knagar said:
Ok so this time I used Odin to do VMC in the PDA slot, then I9000 Kernel went back to VMC and loaded that then when I restarted the phone it went back to the same boot loop.
I have no way to clear the internal SD or anything like that because the programs will not see my phone connected to my PC.
What could be causing my phone to just continue to restart?
Click to expand...
Click to collapse
I gave u a source, download the guide on flashing through odin. It should work. Dun flash 1 file by 1 file.
EDIT : u can find more firmwares here. http://forum.xda-developers.com/showthread.php?t=1102881&page=1
Pm me if you need any help!

Ok so here is where I am at..
I have tried everything everyone has listed so far. The only think that has made any sort of progress at the moment is going into download mode, connecting to the USB after loading Odin. Using JPK_Root_Recovery_2e I9000_Kernel.tar will bring me to the recovery screen.
wipe cache partition + reboot = boot loop
wipe cache partition + wipe data/factory reset + restart = boot loop
wipe data/factory reset + restart = boot loop
Any of the above mentioned plus loading stock firmware results in a boot loop.
Any of the above mentioned plus loading DarkyROM Resurrection 10.2 will again show the Galaxy S I9000 Logo plus the DarkyROM logo and proceed to boot loop.
Clear cache and factory reset than load of i9000XXJVT pit/pda/modem/csc results in boot loop.
If I am missing something please explain in detail and not shunt me off to some other page.
As before I have tried everything mentioned with no luck at getting past this boot loop. Clearly the phone is able to accept roms and so on so the internel SD seems to be ok but the boot sequence seems scrambled. Strange that it will boot to download and boot to recovery with JPK but upon restart it just boot loops and without Odin and JPK I can only get back to download mode.

Seems to me you also have some partition woes. Try to find an older rom (Milky's worked for me) that requires re-partitioning to be done. Flash via ODIN, wait for 10-15 mins for whole process to complete. CWM flash any rom from there ... (Darky's Extreme also repartitions)

[Q] Rooted Captivate running 2.3 freezes after Android load

Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.

ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.

BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT

ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.

Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K

galaxy note 4 (sm-n910t) caught in boot loop and won't enter to recovery.pls help

my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..

You didn't mention how you tried to install the stock ROM . Did you use Odin?

I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.

Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?

Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk

chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery