..
SmOoTher_BeAn_4.1.2 Birds Screen
I have been switching between Black Bean and Smooth Bean, but I occasionally get stuck on the birds with smooth bean and the cat with black bean.
I have nvflashed twice with the files provided by the OP.
mounted the System
Formatted the system, and followed all the other steps mentioned in both posts.
My problem right now is, with Smooth Bean installed, I am stuck at the cat screen. The screen went black and came back, and now I'm stuck.
I'm guessing that in my last installation of Smooth bean, I didn't fully erase black bean.
Long pressing power does nothing.
I'm going to let the tablet run out of power.
But I was wondering whether a solution was found for this problem. Wiping Dalik cache and cache before every boot seems to help, but doesn't always work.
I saw in the Smooth Bean post that someone else had a similar problem, but I'm not sure how it was resolved.
I installed the DRH JB rom before this, which had no problems booting, it just ran really slow for me.
Related
I installed CM10.1 Jellybean 4.2.2 using this guide http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123, and for a couple of weeks it worked perfectly. I used CWM to install cm10 and gapps, everything went smooth. Yesterday I was on Youtube on my tablet, and the video and audio kept stuttering and freezing up, so I rebooted. After that, whenever I press power it either A: boots to the boot animation and won't continue further, or B: does absolutely nothing. I can restore to a backup I made and it will work perfectly until I reboot, where the issue above happens. I can also boot to an sd card I have made with Jellybean 4.1, and that seems to work well. I also tried resetting to factory and then completely reinstalling cm10.1, and the same thing occurs. Now I'm actually having problems booting in general. I've tried plugging into the power cord etc, but it just does not want to boot. Does anyone know what I can do to fix this?
Hello,
since yesterday my Galaxy S2 (summer 2011) started to act wierdly and I am trying to figure out what is the problem.
I was running the latest Sentinel ROM, and I found it "freezed". So I forced restart long pressing the power button. After the restart, I found it freezed again after some (short) time. It also freeze on the boot process.
Apparently in a random way.
So I tried from recovery a factory reset, full wipe, and reinstalling the ROM. Problem still present.
Today I tried logging with ADB logcat, but I can't figure out the issue from the log. I thought a problem with Mali driver shipped with the ROM, but actually it freezes sometime also on boot (so before loading the drivers)
I tried then to flash back the Samsumg original ROM (JB 4.1.2), which apllied nicely. However it freezes also with Sammie's ROM. Also on boot. By example I one time I got the black screen with the writing "Samsung Galaxy GT-9100" getting grey, with some horizonatl black lines. So frozen.
Flashed again with ODIN, again nicely, but it keeps on freezing on boot.
I am clueless. Could it be some issue with the battery? (it's the original, never replaced)
Any help or suggestion appreciated
Thanks
Update:
I tried to flash it back to GingerBread stock by Samsung with Odin. Applied nicely.
It still keeps on randomly hanging :-|
Hi guys, I was using my phone messaging my friends. I put the phone down for about half an hour. When I pick it up again it is hot and will boot to the glowing slimbean logo (boot animation). I assume the phone ran out of battery, but even when I plug it in it will not boot past the logo. Do you guys have any idea as to what is going on, and how I can get my phone working again?
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
SteveMurphy said:
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
Click to expand...
Click to collapse
Thanks for your reply Steve!!
The reason why I'm still using 7.1 is because I was having battery problems on 8.0. I wasn't sure if the bug I had was fixed so I decided to stay behind. This was probably not the best choice but convenience and stability were something I wanted. I will try 8.1 after I backup my current setup if it works.
I believe its Google Now that has been causing me problems. Ever since I started using it my battery drains much faster, and the phone is hotter than usual. If wiping the cache works then I will delete it , otherwise I will probably have to wipe to factory which I really don't want to do.
OK so wiping the dalvik cache has allowed my phone to get past the bootloop. I get this message "Android is Upgrading.. starting apps" and its been stuck on it for a while. Any ideas?
This is weird, don't really know why - out of nowhere - your rom just all of a sudden won't boot.
And yes Google Now will kill ANY battery!
One other method would be to dirty flash 7.1 without doing any more wiping, if you want to keep it. If that doesn't work, full wipe/format system and start over.
Hope you get it working again!
I Installed slimbean version slim-vibrantmtd-4.3-build.2.2-OFFICIAL-1788.zip a few days ago. It was working ok, I then subsequently loaded the Slim_AIO_gapps4.3,build.2.zip(maybe that's a conflict?). Now the issue arose where the slim bean logo appears randomly and the phone freezes on this screen till the battery drains.
Also I am not married to Slimbean, I am considering any ROM that resembles Jelly Bean that has google Apps(playstore, maps and gmail). So I would be open to additional suggestions.
Hi all, hoping to get some help. I rooted my phone the other week and was using viperrom. I had no problems whatsoever, no glitches that I could remember. That is, until I decided to trade my m8 with a friends Note 3. I factory reset it and give it to her, I left the viperrom on because she didn't mind but then the glitches started to happen. The onscreen bottom 3 buttons disappeared for her (home, back,etc.), So I reset it again but the problem persists. I searched for an at&t stock rom and sideloaded that after master resetting, wiping the dalvik cache and all that... now a different problem popped up. It hangs at the HTC logo for what seems like forever, but then I noticed the volume up and down make a noise as if the phone is loaded up. I pressed the power button a few times and eventually the screen turned on and I could see the home screen. This happens every time I restart the phone and I have tried reinstalling the stock rom a few times. I am now in the process of trying a different stock rom.. the first was odexed and this new one is deodexed, I dont know if that makes a difference in my situation but does anyone know what could be causing this? Any help would be appreciated.
Nvm, after a few more master resets it seems to have sorted itself out... not sure what it was but its gone now.
If its the latest version of Viper, based on 2.22 software, you need to update the firmware package, otherwise the long boot times will continue.
Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592