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.
Related
I flashed the latest builds from both Coffebeans - http://forum.xda-developers.com/showthread.php?t=1547778 and Pershoot - http://droidbasement.com/galaxy/roms/cm9/p4wifi/ and I'm having the same issue with both of them. The problem is my Tab will randomly reboot then get stuck on the boot animation and just sit there forever. It's already happened twice now where my Tab rebooted sometime at night and sat at the boot animation until the battery was dead. I did do a full wipe before flashing.
Does anyone else have this issue?
Thanks.
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
foliage green said:
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
Click to expand...
Click to collapse
I came from Task650's version 14, but I've been flashing the CM9 KANGs for a while and haven't had this issue.
i have had some strange reboots...but never gotten stuck on the boot animation like that..thats the bad part about not having a battery to yank unfortunately
Sent from a Gtab 10.1 running Build 30
Well whenever I can't get something to work right, I Odin stock firmware on it and restart the custom rom process from scratch. Having a clean slate is time consuming and might not even be necessary but it's the only full proof way I can get things to work.
I wiped everything and also formatted /system in CWM and then flashed Coffeebeans latest build from 4/8. I haven't had the reboot and stuck boot animation issue, but now I'm having an issue where every time I charge the tab fully it won't wake up. I have to hold the power button to reboot it. It seems like it's the deep sleep issue, but it's been fine leaving it overnight as long as it's not connected to the charger.
..
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.
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 :-|
I was running CyanogenMod 10.1 on my GT-I9300 for several months and it worked great. But the other day I was using Google Navigation as a sat nav while driving and the battery went to 1% and the phone froze. Tried hard Reset ect but ended up having to remove the battery to turn it off.
When I had charged the phone I was stook at the Samsung Galaxy S logo screen and would not boot. I tried everything and several roms to get my phone back in working order.
For some strange reason I can only install CyanogenMod 9, which the wifi and mobile does not work at all so its of no use. When trying the CM10 builds I get stook at the same screen and if I use a Stock ROM I get stook at the Samsung blue animation logo in a boot loop.
Any help would be deeply appreciated.
Tried a couple of other roms installing through Clockwork Mod, including Phenom but only the CM9 one works.
Also just tried the KIES firmware installation, installed fine but on first boot its back into loop
Hello Guys,
i have one big Problem.
From time to time the Screen from my s3 freezes.
The Hardware Buttons are lightning and turns dark and if you touch, they are lightning again
The Status bar/notification bar is also displaying Motion (if you download files and it freezes)...
But the other Screen freezes, the only Thing you can do, is turn out battery restart... everything works fine...
i tested various Roms (whole Omega Series (v59., omni Rom v5, v34, AOKP Rom), Slim Rom), but with EVERY Rom the same..
it freezes sooner or later
is this a Hardware defect? what else can i do? i have wiped all data every flashing...
now my last test ist do Flash original sam Rom...