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.
Related
A few weeks ago, I wanted to move from CM9 to MIUI. So I flashed MIUI in CWM, as normal, and went through the AROMA setup. I chose to flash Siyah 3.something (not the brickbug one.)
So I flashed it, and then it asked me to reboot. I chose Yes. The text 'Rebooting...' appeared at the bottom the screen, but then the screen went dim. Left it for a couple of minutes, and then the screen started flashing random colors. Frightened, I pulled the battery and put it in.
It took almost ten seconds after me holding the POWER button for the device to get to the 'i9100' screen, and when it did, loads of green dots appeared on my screen.
I did a battery pull again, and all was fine. I got the same problem again whilst flashing Resurrection Remix not too long ago.
I don't get the issue after subsequent flashes.
Does anyone know why this happens, or has anyone else had this problem?
What wipes are you performing prior to flashing new ROMs?
Sent from my GT-I9100 using xda premium
I did a data wipe, a /system wipe and a dalvik cache wipe.
Please note that I don't get the problem anymore - I was just wondering why it happened.
yup happens sometimes to me too while flashing siyah based kernel..like some graphic corruption..but i think it aint harmful.has happened to me 3-4 times but nothing wrong till now..
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
eranyanay said:
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
Click to expand...
Click to collapse
u can just rewert to stock ICS 4.0.3 firmware on both the phones and check for the issue (whether its firmware related or any hardware issue as such)
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
eranyanay said:
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
Click to expand...
Click to collapse
1) with 403 for some time once again to ensure no issues of freezing.
2)then a different 4.1.2 stock/custom rom altogether to check for the same(freezing) issue.
stay for some time on those firmwares and see (may be one or two charge cycles).
3) do not install any mods on top of the firmware, just stay stock and see
One of the devices is already back to 403, while the second one on stock 412
the hardest thing to tell if 403 solves it or not, as it happens occasionally, once in a week or two.
I tried two different stock roms, so that would rule out #2.
The weird thing is that wiping data is enough.
data is separated from the rom itself, yet it causes the entire device not to boot anymore.
Last night my phone grew legs and ran all the way across the room while i was sleeping. When i woke up, after searching for my phone for 10 minutes, the vibration no longer works. I didnt know if it was a software or hardware problem. So, I flashed a backup from the day before (where vibration was working) and still no luck. So i flashed back to my current backup, when i rebooted, right before the bootanimation, it vibrates. Odd? It works when the phone is booting up, but not when the phone is booted. I'm running houstonn's Vanilla RootBox (4-20 v1) with houcha kernel. All help is appreciated!
Tyler44346 said:
Last night my phone grew legs and ran all the way across the room while i was sleeping. When i woke up, after searching for my phone for 10 minutes, the vibration no longer works. I didnt know if it was a software or hardware problem. So, I flashed a backup from the day before (where vibration was working) and still no luck. So i flashed back to my current backup, when i rebooted, right before the bootanimation, it vibrates. Odd? It works when the phone is booting up, but not when the phone is booted. I'm running houstonn's Vanilla RootBox (4-20 v1) with houcha kernel. All help is appreciated!
Click to expand...
Click to collapse
Thanks for everyones help...
I was able to fix this, and find the root of the problem (for me atleast). Everytime i click the Dark RootBox, vibration stops working. To fix, you must wipe the device completely, and reflash the rom.
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!
Hello. I have a boot loop issue with my SM-G850F. It happens immediately after camera launching, boot loop can last for minutes, but eventually the phone turns on and works alright except camera. Sometimes camera may work fine for some time but later it goes to boot loop again. Also if i restart my phone manually it also goes to boot loop. I tried to reflash it using Odin, different firmwares, home and factory, Kitkat and Lollipop, i did it with data and cache wiping from recovery every time. When Odin finishes it's job and a phone tries to reboot after reflashing - here boot loop starts again. But when i reflashed 4.4.4 and got a Lollipop OTA update, my phone got back to life, camera worked fine, it restarted fine with no boot loop anymore. But after about 6 months it happened again. The same situation, wiping didn't help, reflashing didn't help, and again reflashing 4.4.4 + OTA update did help, i don't know for how long. What may be the reason? I assume it's not a camera problem, OTA update shouldn't fix it, and it's not a battery for the same reason. What do you think?
ThorosPWNZ said:
Hello. I have a boot loop issue with my SM-G850F. It happens immediately after camera launching, boot loop can last for minutes, but eventually the phone turns on and works alright except camera. Sometimes camera may work fine for some time but later it goes to boot loop again. Also if i restart my phone manually it also goes to boot loop. I tried to reflash it using Odin, different firmwares, home and factory, Kitkat and Lollipop, i did it with data and cache wiping from recovery every time. When Odin finishes it's job and a phone tries to reboot after reflashing - here boot loop starts again. But when i reflashed 4.4.4 and got a Lollipop OTA update, my phone got back to life, camera worked fine, it restarted fine with no boot loop anymore. But after about 6 months it happened again. The same situation, wiping didn't help, reflashing didn't help, and again reflashing 4.4.4 + OTA update did help, i don't know for how long. What may be the reason? I assume it's not a camera problem, OTA update shouldn't fix it, and it's not a battery for the same reason. What do you think?
Click to expand...
Click to collapse
Maybe a hardware issue? Did you try ozcan or epsil rom? Do you have the same issues on those roms?
BarryPooter said:
Maybe a hardware issue? Did you try ozcan or epsil rom? Do you have the same issues on those roms?
Click to expand...
Click to collapse
After several hard resets the problem has gone, i don't know for how long though. So i have no idea is it a hardware issue or not. May it be a flash memory problem?