Hi there,
I flashed my s2 galaxy with the rom here;
http://forum.xda-developers.com/showthread.php?t=1696419
However for some reason on the two occasions i have flashed this rom everything works fine except for when i reboot, when i do that, the animation just loops on booting up, left it overnight to see if i havent waited long enough and have had no luck, so on the second occasion i thought i would flash the rom again after deleting cache/dalvik etc first and still have the same problem, is it something anyone else is having an issue with or is it just a bug in the rom? (couldn't post in the android development forum where this rom is posted due to being a new member).
thanks guys
Aaron-Marcus said:
Hi there,
I flashed my s2 galaxy with the rom here;
http://forum.xda-developers.com/showthread.php?t=1696419
However for some reason on the two occasions i have flashed this rom everything works fine except for when i reboot, when i do that, the animation just loops on booting up, left it overnight to see if i havent waited long enough and have had no luck, so on the second occasion i thought i would flash the rom again after deleting cache/dalvik etc first and still have the same problem, is it something anyone else is having an issue with or is it just a bug in the rom? (couldn't post in the android development forum where this rom is posted due to being a new member).
thanks guys
Click to expand...
Click to collapse
Did you wipe data/factory reset in Recovery?
When you dont do that, the result is always a bootloop!
Sent from my Galaxy S2 GT i9100
Aaron-Marcus said:
Hi there,
I flashed my s2 galaxy with the rom here;
http://forum.xda-developers.com/showthread.php?t=1696419
However for some reason on the two occasions i have flashed this rom everything works fine except for when i reboot, when i do that, the animation just loops on booting up, left it overnight to see if i havent waited long enough and have had no luck, so on the second occasion i thought i would flash the rom again after deleting cache/dalvik etc first and still have the same problem, is it something anyone else is having an issue with or is it just a bug in the rom? (couldn't post in the android development forum where this rom is posted due to being a new member).
thanks guys
Click to expand...
Click to collapse
Do a full wipe and reflash the rom
Related
Hi
first of all, i know i should be posting that on and dev section, under task650 thread but due to an account never used since activation I cant without posting at least 10 posts, and i don't like flooding so here I am
flashed task650 rom, now I have this red X even when I charge on wall with the plug that come with the device. tried to revert to Galaxy task 14 rom, still have the same issue. Did it all, full wipe (factory reset, cache and dalvik cache), repaired permissions; followed step by step the guide, and am not at my first flashing experience. Reflashed couple of times also. I've been flashing for 2-3 years now.
Could someone help me out here?
does your tab show the charging animation when its OFF ?
locality, nopictu
yes. I had the charging animation. But well I flashed Ganbarou Rom and for some unknown reasons it's all back to normal.
Dont know what happened, but it is fixed.
Ok I hate starting a new thread but I have a problem that I can not seem to find any information on it,
I have had my S2 for 1.5 years and have run many many custom roms. Been using Paranoid lately. Today I tried flashing the newest Wanam Lite as my second rom keeping Paranoid as primary. (using dorimanx kernel)
Wanam failed to install. After boot the screen goes black. No problem... I will just go back to my Primary rom. Tried, Tested and True, Paranoid Android.
What's this? My phone is asking for SIM unlock code. I unlocked this phone 1 and a half years ago. Ok so I unlock it the same way i had done in the past for my S2 and many friends S2. I installed "Galaxy S Unlock" from the market and ran it. Ok phone is unlocked and I can use it like normal, as I have network signal.
But as soon as I reboot it is locked again. So now I have to unlock the SIM every time I reboot my phone.
Does anyone know why this is happening?
This is what I have tried so far.
- reinstalled ROM
- wiped dalvic
- wiped data
- wiped cache
- fixed permissions
Nothing I try solves the problem. Every time I reboot I lose my sim unlock.
Any help is appreciated.
Thanks.
anyone have any insight into this??
has this happened to anyone else?
kevjef420 said:
Ok I hate starting a new thread but I have a problem that I can not seem to find any information on it,
I have had my S2 for 1.5 years and have run many many custom roms. Been using Paranoid lately. Today I tried flashing the newest Wanam Lite as my second rom keeping Paranoid as primary. (using dorimanx kernel)
Wanam failed to install. After boot the screen goes black. No problem... I will just go back to my Primary rom. Tried, Tested and True, Paranoid Android.
What's this? My phone is asking for SIM unlock code. I unlocked this phone 1 and a half years ago. Ok so I unlock it the same way i had done in the past for my S2 and many friends S2. I installed "Galaxy S Unlock" from the market and ran it. Ok phone is unlocked and I can use it like normal, as I have network signal.
But as soon as I reboot it is locked again. So now I have to unlock the SIM every time I reboot my phone.
Does anyone know why this is happening?
This is what I have tried so far.
- reinstalled ROM
- wiped dalvic
- wiped data
- wiped cache
- fixed permissions
Nothing I try solves the problem. Every time I reboot I lose my sim unlock.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
First of all , use the following to unlock your phone, if it works for you that would be gud otherwise flash the rom again (Fresh Install)
https://dl.dropbox.com/u/21618136/GalaxSimUnlock.apk
You cannot dual boot Leaked JB based roms as of yet ..
Exatley same things happend with me at this afternoon. My sgs 2 was unlocked nearly a year ago, and I'v been tryed a new "leaked - out" rom which I've found on the Sammobile forum. I9100XXLSJ - Offical, beta... or alpha.. dunno, but 4.1.2
Few minutes later I also tried an another rom... http://forum.xda-developers.com/showthread.php?t=2037363 XXLSJ tweeked by Alliance.
I've wiped everything before every install, and I'm not sure where I've lost my "unlocked" status... Lol.. First time I was thinking its a PIN code only. Obviously I never seen this before. In the last few year I installed, and tried many roms without any issue. Mostly Darky's, CM 7-9.
But long story short: your tool solved my problem under a minute. Thank you so much MR.Killer
Ps: maybe I also tried a CM10 nighty build today.. I cant bear in my mind everything
jstonehun said:
Exatley same things happend with me at this afternoon. My sgs 2 was unlocked nearly a year ago, and I'v been tryed a new "leaked - out" rom which I've found on the Sammobile forum. I9100XXLSJ - Offical, beta... or alpha.. dunno, but 4.1.2
Few minutes later I also tried an another rom... http://forum.xda-developers.com/showthread.php?t=2037363 XXLSJ tweeked by Alliance.
I've wiped everything before every install, and I'm not sure where I've lost my "unlocked" status... Lol.. First time I was thinking its a PIN code only. Obviously I never seen this before. In the last few year I installed, and tried many roms without any issue. Mostly Darky's, CM 7-9.
But long story short: your tool solved my problem under a minute. Thank you so much MR.Killer
Ps: maybe I also tried a CM10 nighty build today.. I cant bear in my mind everything
Click to expand...
Click to collapse
Glad i helped and you never clicked the thanks button
Please CLICK THANKS IF I HELP
Mr.KiLLeR said:
First of all , use the following to unlock your phone, if it works for you that would be gud otherwise flash the rom again (Fresh Install)
https://dl.dropbox.com/u/21618136/GalaxSimUnlock.apk
You cannot dual boot Leaked JB based roms as of yet ..
Click to expand...
Click to collapse
THANK YOU VERY MUCH. This app solved my problem with the sim unlock. Saw it on the market but it wanted me to pay
I didn't know that the leaked JB could not be dual booted. That would explain the black screen. I think I will back up my primary to SD and try installing that rom again. Does this work on any kernel or just the one it is supplied with?
Anyways. Thanks again. You solved my BIG problem.
kevjef420 said:
THANK YOU VERY MUCH. This app solved my problem with the sim unlock. Saw it on the market but it wanted me to pay
I didn't know that the leaked JB could not be dual booted. That would explain the black screen. I think I will back up my primary to SD and try installing that rom again. Does this work on any kernel or just the one it is supplied with?
Anyways. Thanks again. You solved my BIG problem.
Click to expand...
Click to collapse
only 'Philz' kernel does support the leaked Jb rom or one based on it for know
The app is free to use if you get it from Spockys thread.
I believe you have to pay if you get it through play store.
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button