I flashed EDT FlagshipV4 yesterday, and it was working fine until I changed the lockscreen and tried it out, but right as I pressed the sleep button the phone just shutdown. I booted the phone up again and the EDT animation played and the phone looked like it was ready to go (could move the homescreen and such). However, as soon as the media scanning thing was done, the phone would reboot and this would happen over and over again. During each reboot the phone vibrated in a specific pattern.
Now I'm pretty new to Android, so I did a battery pull, booted it to recovery and proceeded to flash the phone to the Trigger 2.2.1 zip I had on the SD card and the booting issue stopped. Can anyone tell me what went wrong with my phone? I'm hoping that it wasn't Flagship, because I really like the look of that ROM. Thanks!
Did u flash a new lock screen or just change to a different one via settings/display? If u flashed a new lockscreen sometimes the system files aren't the same as the Rom which cause it to do so.
Currently running ______________! (
Haven't had any issues with that rom, you must have flashed an incompatible framework for lock screens. If you haven't, I'd download the rom again and reflash.
Related
I flashed over Bionix V 1.3.1 with NextGen V2 last week by wiping data/cache/etc instead of flashing back to stock first. Everything worked really well (except for TW4 that force closes everytime) but I was just a little bugged by the 1 sec lag it takes to turn on the lock screen from sleep (the lag is absent when charging). I thought I would ODIN it back to stock and try again. Strangely, the stock has this lag now too. When I try to wipe Dalvik, I got an error "E: Can't mount /dev/block/mmcblk0p2 (File exists)". Also, my phone is still SIM unlocked after ODIN. Does this mean there are some parameters from previous flashes remaining in the system? How can I REALLY get it back to stock?
with windows plug the phone into pc then right click on the internal sd on my computer then format, should get rid of anything left from previous roms, remember to back your stuff up
dont know how to do it on mac
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
donnygg said:
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
Click to expand...
Click to collapse
id leave it from the moment it first comes on before
when i was flashing between 2.2 roms i always went back to simply galaxy and that had the old start up thing but i use to leave it before going through it then reboot then go through it then reboot after
1 reboot should do it though
Tried formatting but no improvement. Tried softlocker app and was able to turn on the lock screen instantly. However, I was losing about 5% battery life every hour, so that's not quite a solution. I then tried something really simple - remove the external SD. Immediately, I could see a reduction in lag when turning on the lockscreen from sleep (<0.5s vs >1s, if you call that a lag). It seems like the external SD card is the problem but I don't know what. The card seems to be lacking the ext2 partition, thus it couldn't be mounted or formatted in CWM. From what I understand, ext2 may improve I/O performance but I may be wrong. I couldn't get it to partition in my phone. The phone seems to format it back to FAT. I'll try getting a microSD adapter and partition it outside the phone and see if it helps, just out of curiosity.
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.
After I restarted my Cell the boot animation keeps on replaying after the slight vibrate, same thing hapens for 10 mins then the mobile starts.
Its not normal
Can anyone help?
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
hirentherock555 said:
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
Click to expand...
Click to collapse
Found a partial solution after formatting the cell twice like a fool
Last night while playing Dangerous chambers 3D or somthing my cell got hanged.
Later it wouldnt restart or anything so had to pull out the battery.
After it started it went into loop mode.
I got worried
Formatted it once.
All ok later then again after some apps it went in loop mode.
Couldnt figure out which app was causing the prob.
Then today morning after some reasearch found out that:
In CM7 settings in settings menu> Tablet tweaks> disable lock screen> Tick
This is what i used to do to use an alternate lock screen.
After removing the check all is fine untill now.
Will update if anything happens next.
I also met this problem when trying to develop a CM7 ROM myself (from HPA CM7 BETA2). My problems are:
1. After building successfully, apps inside the output /system/app folder are bigger (in size, of course) than the original HPA ROM (ADWLauncher in HPA is 731.5K, and mine after building is 1M)
2. After flashing to DV, my phone hangs at the CM7 logo. It's OK to type "sudo adb devices" to see that my device is attached, but then any command other than that will receive "error: closed"
Guys, do you know what's the problem with my build?
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
go in e3 recovery and perform factory reset
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
Go to recovery and wipe cache and wipe dalvik Cache. If still not working then do Factory Reset. If the problem is still there than flash the rom again.
Sent from my GT-I9100 using Tapatalk
As my main goal was to get my data from the phone I suprised myself a lot and I'm copying as we speak the whole /emmc/ via SDK tools.
It's gonna take a while - I assume it's copying the whole 16GB.
After that I'll try factory reset's etc. and check if I can use my phone again.
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
blint6 said:
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
Click to expand...
Click to collapse
That SMS thing is strange
Have you tried another recovery version? Or perhaps changing recovery? This isn't a normal issue, since you already tried installing another ROM.... You can try another Kernel either
If none of this works, consider flashing the original Samsung's ROM or some samsung-based ROM (they usually do a nice clean-up, at least for me these ROMs fixes the majority of my problems)
@blint6:
1. Maybe the hardware though. This you can test by flashing actual firmware and running it under normal conditions for 1d.
2. Reboot is a known reaction to RAM-lack on LP, too. Flash Omni cleanly and run it for 1d without GApps and bigger apps.