I have been running Slimbean 2.8 since it came out, tried to upgrade to 2.9 when it came out and got a bootloop. I saw some where to hold the power button down till the phone shuts off to fix the bootloop, the problem is my power button doesn't work. Thought I would just wait for the next release to come out, so I went to upgrade today to 3.1 and same problem.
It may not actually be a boot loop, but that is the best way I can describe it. It boots the first time and goes through the app initialization then reboots. After that it hangs on the slimbean boot animation.
I have tried pulling the battery and reinstalling, re-wiping dalvik/cache, re-downloading zip. I haven't tried a factory reset(hoping to avoid that).
Any suggestions?
Thanks
WSlinky said:
I have been running Slimbean 2.8 since it came out, tried to upgrade to 2.9 when it came out and got a bootloop. I saw some where to hold the power button down till the phone shuts off to fix the bootloop, the problem is my power button doesn't work. Thought I would just wait for the next release to come out, so I went to upgrade today to 3.1 and same problem.
It may not actually be a boot loop, but that is the best way I can describe it. It boots the first time and goes through the app initialization then reboots. After that it hangs on the slimbean boot animation.
I have tried pulling the battery and reinstalling, re-wiping dalvik/cache, re-downloading zip. I haven't tried a factory reset(hoping to avoid that).
Any suggestions?
Thanks
Click to expand...
Click to collapse
Have you tried flashing the ROM, rebooting into recovery and re-flashing it?
I tried that and it didn't fix the problem. However I started doing some playing, since it seemed to boot the 1st time and die after it loaded the apps I figured it was app related. So I formatted datadata and data and re-flashed, everything worked fine after that.
Thanks for the suggestion
Sent from my SGH-I897 using slimbean 3.1
Related
Need a little help here...out of the blue today my phone started continuously re-booting itself. Only gets to the HTC screen and then re-boots. I have done multiple battery pulls with no results. I cannot boot into recovery either, tried that many times as well. My only option is a screen that I have not seen before that asks if I want to clear all data and then reset the device. Anyone have an ideas? Running Fresh 2.3.3, had no previous problems.
I had the same thing happen today. I had just flashed Fresh 2.3.3 to try to fix the GPS issue in the CM6 830 nightly, and my phone started rebooting every minute or so. I pulled the battery and immediately booted into recovery by holding down <home> and <end call>. I was able to get to recovery, where I flashed a different ROM I had on my SD card. I hope this helps.
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
Hi All!
I flashed the last build available from http://forum.xda-developers.com/showthread.php?t=1777398 on my P7300.
Every thing was OK (well, after the flash I had to fix permissions, since it didn't boot) until I had to switch the tab off. After switching on again, it didn't boot, black screen after the Samsung splash, back light was on.
So, I wiped/factory reset, and installed every thing again and it worked, until I switched off the tab again ... I can reset long pressing the power button and getting into recovery.
I already did the procedure three times, since I didn't find a way to properly boot when this happens.
Could anyone give a clue about what can be happening?
Many thanks!
try to reboot tablet multiple times. work for me
yoyurik said:
try to reboot tablet multiple times. work for me
Click to expand...
Click to collapse
Thanks! I will try it if it happens again. I am also considering to try the AOSP.
Mine always starts on the second boot. After the black screen after the Samsung splash, I just long press to reboot, and it always
works the second time.
Same here...
Hi Guys,
I am running Pandoriam and have twice had issues when moving the SIM card out of my S3 and the next time I rebooted it would hang at the SAMSUNG logo and wont boot up.
I would do a cache reset and a Dalvik wipe but doesnt fix it, have to do a full factory reset.
Any ideas ? I dont want this to randomly happen if the SIM slips out when knocking around my phone etc.
I think it might have something to do with Hot Boot, because if I do a Hot Boot from the Reboot menu it has the same outcome.
OK now it appears it might be linked to changing the Lock Screen.
When I change it and reboot the SAMSUNG logo appears and then it appears to generate the outside (clock / battery) icons and the overlay text (no sim / sim lock) appear... but the lock screen background is just BLACK and then crashes and reboots to SAMSUNG logo and doesn't go past the boot up.
I have some of the same issues. I left my phone charging over night. When i wake up it was frozen. I rebooted the phone and know it hang at the Samsung logo. Needed for install to fix this.
I can confirm the hot boot option. It makes a new clean re install go into Samsung logo hanging. But you can fix with a force shutdown and normal boot.
Both issues was on Pandoriam 4 Final new flash will be 4.5 maybe its fixed.
komig said:
I have some of the same issues. I left my phone charging over night. When i wake up it was frozen. I rebooted the phone and know it hang at the Samsung logo.
Click to expand...
Click to collapse
I had the same problem. In the end, i must reinstall the rom.
I have same issue when chose the persus kernel when flashing rom.
End up I flashed again with stock kernel
and the problem does not happen for a week.
Sent from my GT-I9305 using xda premium
Strange, Just to be sure Wipe Data/Factory rest before installing but if you have its a weird problem because I have rebooted and reinstalled and re-tested the rom ALOT of times and have chosen most of the options and kernels and I have NEVER had this issue.
Never had any Problems with the great Pandoriam ROM... It's a beauty !!
Sent from my GT-I9305 using xda premium
Hi guys,
Sorry I haven't been around to update, I re-installed and tried multiple different sets of options and every single time I changed the lockscreen from the default and rebooted it would just hang.
I did all 3 wipes from recovery before and after flashes but same issue. (I flashed from recovery not PC)
As I was running version 4 at the time I upgraded to 4.5 and ran through multiple different sets of settings but same issue
I will try it again in a few versions but for now I need a working phone so I am running rXTREME V2.1 for the time being.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.