So, i just updated to CM11 nightly 15112015, then i went to Settings → Storage and cleaned up Misc and Cache. I opened Xposed and i saw that SDK 19 is not yet supported. I was messing around then i pressed Uninstall, and it went on bootlooping eversince. I tried to remove the battery for a day but it didn't work. I could only access recovery mode, which is glitching, and download mode.
Galaxy S3 I9300 running CM11 15112015 nightly, Boeffla kernel.
Note: There is little chance for hardware error like problems with the buttons, because it is a combination of 3 buttons, and the phone stopped booting on battery insert when i came home.
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
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.
Hi
I have had Slim ICS 4.2 working ok for a month or so. Yesterday it suddenly started to give FC to all apps, so I rebooted it. The only thing that changed was that, when trying to update the Adaway lists, it gave me an error and could not do it. From that moment, it was stuck in the Slim logo for three reboots. After that, it started a reboot loop, showing the semaphore logo and rebooting back again. I have managed to enter Recovery by connecting it to a USB cable, after some reboots it gets into it. Three button combo was working for Download Mode but not for Recovery.
Can I simply reflash Slim ICS, without doing a wipe? I don´t want to lose my apps, at least not before backing the data conveniently. It would suffice to be able to boot and do a Titanium Backup, then move on to Slimbean or something. I still have the original zips I used to install it.
Thanks!
hi, i have read developers forum and CM11 seems no issues for others except some dock keys and USB3. but for me still freezes:
- at firts time I installed CM11 from official JB, it was some nightly build from march, CM froze within few seconds in setup screen.
- then I cleared again all caches, installed next nightly build, all went ok, CM worked ok for me (FIFA14, music browsing, etc...) but then i installed some Angry birds series for children, and tablet became unstable (maybe more core apps have been updated), froze during games withing 10-20 minutes, I thought it is issue of the game, i uninstalled all Angry birds games, tablet became more unstable, froze within few minutes.
Then i downloaded and installed yesterday nightly build, installation went ok, but again tablet freezes within few minutes...in setup menu, in stand by mode, in game....OS is not working but battery is discharging. then i downloaded and installed today night build, and installed CM completely without keyboard dock, and local language i set to English (original i am using Slovak) to avoid possible issues with dock, keyboard, language set...but it is the same...tablet freezes within few minutes.
then i installed back official JB...all is going ok.
Any idea what is wrong? I have installed CM on Galaxy Tab, on Samsung S4, no problems.
i have working boot loader 10.26 and CWM recovery 6.0.4
-before installation i did factory reset, cleared cache, dalvik cache
-installed CM
-installed signed GAPS
any idea please?
Update your fw/bootloader to 10.26.1.18.
This can be done via microSD update method from ASUS.
Installing an OTA may not install the needed FW/BL in all cases.
No matter what 9 out of 10 times I can no longer access TWRP recovery and Odin Download mode.
I'm currently on GA Lineage 7.1.2, rooted G900V. I have magisk 20.3 installed.
I've been having to change roms android 7.1-10 constantantly over the past couple years due to instability. Today the rom I was on I could not close the screen manually with power button otherwise the advanced power options would show. It's a bug!
Now all of a sudden after doing a full wipe and installing another rom I went to back it up and got the maintence boot mode rather than TWRP. I have already done factory resets, flashed other roms, re-flashed TWRP and my firmware. All of this several times over!
When I do mange to get TWRP I do wipe everything and restore backups of roms. Sometimes in download mode it wont stay and within a few seconds it bootloops into maintence mode.
I have no idea why this is happening again but now it seems it might be permeanent? Ive seen this maintence boot mode thing before but switching to another rom and or getting rid of bad modules stopped it. But not anymore.
Any ideas what is causing this and what can I do? Is my S5 done for? I guess at this moment I should stay on the buggy rom I was trying to get rid of until I can do regular backups again.
Droid9684 said:
No matter what 9 out of 10 times I can no longer access TWRP recovery and Odin Download mode...
...Today the rom I was on I could not close the screen manually with power button otherwise the advanced power options would show. It's a bug!
Click to expand...
Click to collapse
Well a bad power button could explain all 3 problems.
Or are you saying that even when using the advanced Power menu it will not reboot in Recovery or Download mode?
Droid9684 said:
Now all of a sudden after doing a full wipe and installing another rom I went to back it up and got the maintence boot mode rather than TWRP. I have already done factory resets, flashed other roms, re-flashed TWRP and my firmware. All of this several times over!
Click to expand...
Click to collapse
That never happened on my S5 G900M. I'm curious: could take a photo of it using an other device and post it here please?
Using this XDA site search: site:forum.xda-developers.com/ sm-g900v maintenance mode you can find other G900V users with a similar problem.
One user posted this:
I ONLY
GET "Maintenance Mode Recovery Menu" Which has 3 options
1 Normal Boot
2 Factory Reset
3 Safe mode Boot
But Sadly and STRANGELY I CANNOT GET THEM TO WORK EITHER!!!
Click to expand...
Click to collapse
A troubleshooting step could be to flash the most recent stock Samsung for your G900V which will re-lock the bootloader, test thoroughly to make sure it works properly then unlock the bootloader following one the numerous threads on XDA about it.
FWIW my Galaxy S5 G900M LineageOS 17.1 build 2020-11-29 + Open GApps Pico build 2020-11-05 + Magisk 21.0 + Magisk Manager 8.0.3 + TWRP 3.4.0 recovery is running smoothly without any major bugs.
See [OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
***
Sorry for late reply I been busy. So the problems are happening again off and on. I'm going to have to switch roms again because mine keeps soft rebooting itself and dropping SIM card at times.
Next time I get maintenance boot screen i'll try to take a picture of it. The thing is from the restart menu I have the option to boot into recovery. When I do it only sometimes goes into TWRP otherwise goes into the maintenance boot mode and I have seconds to make a choice Boot normal, safe mode and factory reset. None of which options work. Within seconds my phone boots itself. I have the same issue in download mode if i'm able to get into it within seconds reboots itself. So it's very hard to do anything with ODIN. I've re-flashed twrp and my firmware a few times but it takes hours sometimes to be able to due to the self rebooting phone. There is also the problem of when I power off the phone in menu options it shuts off then powers itself back on again. I may have a bad power button its been a couple years that I can remember changing it. But it broke to where I couldnt power off my phone. When trying to lock the phone the reset menu pops up sometimes other times it locks phone as it should. It would be a ton of work for me to switch to a stock rom and do all that crap over again. I mean I wasnt having this problem this constant until recently.
I'm staying on 7.1.2 because bluetooth and music are working. I was on 8.1+ bluetooth would always drop and music would stop working in background due to how background foreground processes changed after 7.1.2. Also the camera file location is messed up and not in DCIM it's located in a lineage file. Whenever I take pictures they are auto uploaded into my dropbox. It doesnt work on newer android versions after 8.1. I have the G900V Verizon maybe thats why i'm having all these problems. I know for sure the No sim is one of them on this device.
I dont plan to buy a new phone until next year and it will be a 5G one. It's too early to invest in one at this time since 5G is just slowly rolling out.
@curiousrom here are two photos of the S5 booting into recovery / maintence boot mode.
Droid9684 said:
@curiousrom here are two photos of the S5 booting into recovery / maintence boot mode.
Click to expand...
Click to collapse
Thanks for the photos.
So it seems it's a Bootloader Maintenance Mode, not recovery.
The first splash screen is the bootloader's which is named Aboot in the S5. See the attachments.
You installed a custom bootloader to unlock your S5 G900V & that's probably why it's acting up.
Ask in S5 G900V unlocking threads & includes those photos.
***
curiousrom said:
Thanks for the photos.
So it seems it's a Bootloader Maintenance Mode, not recovery.
The first splash screen is the bootloader's which is named Aboot in the S5. See the attachments.
You installed a custom bootloader to unlock your S5 G900V & that's probably why it's acting up.
Ask in S5 G900V unlocking threads & includes those photos.
***
Click to expand...
Click to collapse
Odd because I really dont have this problem often and yes that was the only way to unlock the bootloader on 6.0.1. Anyhow I ordered a new power button should arrive soon. That might help with it being sensitive it does look a bit pushed in. I noticed it seems to not boot into TWRP if I choose to go to advanced restart menu and choose to boot into recovery. When I manually do it after powering off i'm not having the problem. So maybe it's a bug with all the ROMs out there when choosing recovery from advanced restart menu options.