Related
Hey folks,
being stuck in bootloops is one of the most annoying things for us powerusers.
Therefore I want to investigate a little bit deeper into this topic.
The normal procedure of "solving" the bootloops for me was flashing a base Gingerbread ROM by Ficeto (Mostly JVT) via ODIN, disabling Lagfix, entering CWM & flashing ICS again.
But one time (about 2 weeks ago) I had no time to go through this process, so I took the battery out of the phone (to abord the bootprocess & shut the phone down), placed it in again & putted the phone back in it's pocket.
About one hour later when I looked at it by accident (wanted to check the clock & forgot that it was bootlooping) the phone was fully booted & back to normal.
so the last 4 times my GT-i9000 (running nightlys of CM9) got stuck on the Bootscreen coming again & again, I took the battery out, placed it in again & let it bootloop for a while & after about 20 minutes baaam my SGS was properly booted?!
So my question/request is for you if you are stuck in bootloops:
[highlight]Please try the following:
1. Take the battery out & place it in again
2. Start the phone again
3. wait, wait, wait & be patient
4. Tell me if the problem solved itself or if after more than 2 hours of bootlooping nothing happened [/highlight]
if it didn't please tell me how long you've waited, what caused the looping & which nightly etc you where running!
just for clarification: with bootloops i mean being stuck on the Samsung Galaxy S / Cyanogenmod Screen where it is written in plain text which appears before you can enter recovery or the normal bootanimation appears. When my phone was/is bootlooping I also have no chance to enter Recovery. & I also know that it sounds strange that BL should solve themselves, but please try it!
[edit] I also read some time ago that there where other people with the same experience, this is why I opened a thread & I'm sure this is not a thing related to only my phone
I experienced something similar , also with CM9 . Phone working very hard , so i restarted it , but after the Galaxy S GT i9000 screen , the CM9 blue boot loaded for about 10 minutes and nothing , so I decided to enter in recovery ( I removed the battery , waited a minute , inserted it in the phone , and the recovery didn't work . Waited 10 minutes , and after that the recovery worked , and I reflashed CM9 , because it was the only rom I had in the internal SD card .
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Thomas. said:
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Click to expand...
Click to collapse
It would be nice if you could tell exactly what you did, if more people would do that we might be able to figure out why this thing happens to you and why it doesn't happen to me.
when i flash:
*phone not connected to pc or charger
*running stock kernel
*16 gb micro sdcard mounted
*all sorts of battery percentage, from 10 to 100 percent
*reboot recovery by terminal command "reboot recovery"
*format /cache
*flash the build from /mnt/sdcard/download
*flash gapps from same location
*run a script that wipes dalvic, removes several sounds and unwanted apps and fixes permission
*format /cache again
*reboot
I know this is a pretty weird procedure and it's in no way an advice to anyone, it is just an example of giving details that might lead to a common factor for bootloops.
Taptalked u see
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Thanks for your post!
What caused the bootloops?
fipsib said:
Thanks for your post!
What caused the bootloops?
Click to expand...
Click to collapse
1st time I got bootlooploop was [15/Jan/2012] I was trying to boot into Recovery via power button so I could upgrade from Build 12 to Build 13.
2nd time [2/April/2012]I was on AOKP B28 & I had booted into Recovery to wipe cache & dalvik & after successfully wiping, the bootloop came when I hit the 'Reboot' option to start the phone.
(AGAINST better judgement - since first bll I had avoided wiping cache & dalvik)
jep. I also had bootloop problems by wiping cache and dalvik cache. I was on SlimICS flashed midnight kernel. Everything was working just right but CPU scaling had some bugs for me so i removed init.d scripts went into recovery wiped cache and dalvik cache...and boom....bootloop :/. Now I'm back on CM7 because this is a rather annoying problem....
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Can you link me CM7 kernel for Odin? thanks
farid993 said:
Can you link me CM7 kernel for Odin? thanks
Click to expand...
Click to collapse
Yep, here it is,
View attachment 1012442
This worked for me both times
[remember to leave UNCHECKED
Ensure Reboot, Repart, F-Reset]
Then boot into Recovery and restore Nandroid - no need to be flashing gingerbread.
Ever since the first nightly, I have been plagued by bootloops. Usually formatting /system, /data and /cache helped. But not this time. I tried to install the 19/4 nightly, and had gotten into bootloops. Yes, I have used custom kernels before.
However, even clearing init.d, clearing NSTools, flashing from FixRecovery, the cm7 kernel, even flashing with Heimdall (flashing stock kernel and custom kernel) could not get me out of the loop. Note: I tried the method as described in the OP.
What I finally did was format everything, excluding ext-sd. Format internal SD as well, after backing up some files. And BAM! That was it! Something on the SD corrupted the install. No bootloops, can even install custom kernel, no problem.
So, that may be a tip for people not able to get out of the bootloop, or experiencing constant bootloops.
Hey it's under Devs investigation now:
http://forum.xda-developers.com/showthread.php?t=1627689
My galaxy with CM9 started to bootloop yesterday, no way to enter recovery
I'll make you know in a couple of hours if something change leaving it on ..
If nothing change, is there a place where I can find CM9 kernel to flash with odin ?
thanks
Read Bejda's post, one post above yours.
Taptalked u see
wooops didnt see the second page of the thread
anyway leaving it there to bootloop didnt solve the problem
flashing semaphore kernel seems yes
I finally upgraded my wife's Verizon Tab to the 7/25/12 CM9 nightly four days ago. In that time, she's experienced two random sleep-of-death instances, from which I succesfully recovered. Today, however, she put her Tab down after using it for a bit, went back to it later, and it was off again, and very warm. She plugged it in and tried to re-start it, but it would hang on the CM9 splash screen forever.
I tried to re-start it and got the same results.
Then I tried booting into CWM Recovery to reboot from there, but got the same results.
I tried to fix permissions in CWM, but CWM became unresponsive.
I rebooted into CWM again and tried to restore a nandroid, but it failed since /data couldn't be mounted.
I then tried to flash the 7/28 nightly, but it couldn't mount /data either.
I used Heimdall to reflash Recovery and kernel (5.0.2.7 if I remember correctly) I had used to upgrade to CM9, and then tried to flash the 7/28 CM9 again. This time, after a very quick flash sequence, and a very long time (20 minutes) on the CM9 splash screen, it finally moved on to the boot animation, and eventually booted...right into a screen that said "Encryption Unsuccesful."
Per that screen's instructions, I elected to do a factory reset and reboot. After a very long time, the Tab rebooted to the same error screen.
Bottom line is, I've since learned the "Encryption Unsuccesful" bug is an ICS one (especially with unofficial ROMs), and it does a number on your internal and external data partitions/SD card. I was lucky in that the SD card didn't get wiped, but my Tab is unrecoverable. My latest attempt is to load a rooted stock Verizon ROM/recovery/kernel using Heimdall, but after almost an hour, I've just made it to the "Verizon Wireless" boot animation. Most threads I've read on this issue end up in dead-ends, and I couldn't find a single one that pertained to the Original Galaxy Tab, much less Verizon's.
Does anyone have any ideas as to what else I can do?
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)
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
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