Hi all, I flashed today Paranoid Android 3.99 - 29.08.2013 (I come from Vanilla RootBox) on my Samsung Galaxy SII, and I noticed that except for gapps everytime I flash something else the phone stuck on the bootscreen.
I flashed Dorimanx 9.39 and it worked at first but after a reboot it got stucked, after I kept the stock kernel of the ROM and try to flash PurePerformanceX and it got stucked again.
Procedure before and after flashing ROM and everything else:
1. Nandroid Backup
2. Wipe Data
3. Wipe Cache&Davlik
4. Flash PA 3.99
5. Wipe cache (just for safety )
6. Flash Gapps
(6.1. Flash PurePerformanceX the second time without installing the Dorimanx)
7. Flash GS2KernelWIpe2.09
8. Flash Dorimanx 9.39
I tried also to do point 7&8 before the 6, but it's the same.
Anyone else having this kind of problem?
Cheers!
Moae
Nope, I haven't tried that version of PA yet, it's on my to-flash list but testing something else right now. You mentioned using hawkerpaul's kernel wipe script...
What I would do (and personally follow every flash) is:
Flash ROMNuke script by hawkerpaul
Flash PA
Flash Gapps
Flash dorimanx
No other wipes other than the ROMNuke script. Then, see if it boots (& reboots). If it does, then flash your performance mod. If that causes bootloops, my guess is that the performance mod isn't updated for 4.3 yet. Either find a new performance mod, or tune dorimanx so you don't need one
See how you go.
Sent from a galaxy far, far away
at first I tried without PurePerformanceX, just PA+Gapps+Dorimanx. I actually use to flash the kernel before flashing gapps, 'cause a lot time flashing gapps before the kernel gave me some problem.
to answer to the other question, yes, I used the GS2KernelWipe by hawkerpaul
By the way, there is a guide for a good tuning of Dorimanx kernel?
Ok so have you tried his ROMNuke script? Never had an issue if I flash that before a ROM /kernel /gapps.
Hmm. Depends on what you want it for. I tune mine for battery, but not to the point of any lag. Someone else doesn't care about battery, and just wants s3 speed on a 2 year old phone. See what I mean? In saying that, read the last 5-10 pages of the Dorimanx discussion thread. That'll give you a pretty good idea of what works for performance. Obviously a god step is the 'performance' profile in Stweaks
Sent from a galaxy far, far away
I'm doing backups before trying . Let you know how it will go.
I'm actually looking for a good battery life but avoiding lags , anyway thanks for the tips
it seems working properly now! thx for all
Moae said:
it seems working properly now! thx for all
Click to expand...
Click to collapse
Good to hear! Re: tuning dorimanx, search for (it may even be linked in OP of dev or discussion thread) for a post by droidphile on governors, i/o schedulers etc. That's a great place to start. Wait I just found it, look here http://forum.xda-developers.com/showthread.php?t=1369817. Start reading up there :good:
Related
I don't get what all the hype is surround Philz-CWM6 kernel anything that is even remotely related to it doesn't seem to work. His 4.00B21+22 just don't seem to boot at all, I have to go back into recovery and flash another kernel before it does anything.
Siyah 6.0b4 will boot but doesn't seem to have a working home button.
I can't seem to find the latest CM10.1 Kernel for 4.2.1 roms. I've currently got LS8 modem.
I have no problems with DorimanX I just don't find it a very good Kernel, not very power efficient, don't get me wrong it's fast, but I want my battery to last.
Okay, so what is your question? You name a couple of kernels that don't work for you without telling which rom(s) you run. If all these kernels seem to fail in almost everything I think you'll have to start thinking about you yourself do something wrong, because of course nobody would use and praise a kernel if it doesn't boot.
Sent from the Matrix
I have tried a few roms, I was a long term fan of Rootbox until they removed the DPI Changer, I had tried 3.2 & 3.5, I've also tried stock CM10.1, Paranoid Android 2.99 and a few others that I now can't remember.
My question should have been more to the point, what the bloody hell am I doing wrong? I've been testing a few roms because I'd like to find one that I'm happy with for performance, customizability and battery life, I know it's never going to be a perfect balance, but that's why I'm testing so much.
I've been doing clean installs for all of them, factory reset, wipe cache, wipe dalvik, format system, install rom, install gapps, kernel cleaning script, new kernel, boot.
Ironically after stating in my OP that I couldn't find the CM10.1 kernel, I have just come across one, I just find that they have the best performance, I don't like the stupid complexity of Siyah 6+ and DorimanX, there's too many options that I have no idea what they do and I feel just aren't needed.
Oh yes. Siyah & Dorimanx are stupid because some n00b in Q&A says so You crap on about how much you want to customise, yet you want to run a 'vanilla' CM kernel which offers nothing of the sort compared to those two.
But, eh, whatever works for you.
Edit - Donnie, don't waste your time. OP obviously knows best.
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
Guyz I recently install jb v5 with phantom kernel. I had some problems with led,sound and battery.. I was charging the phone everyday..I install v4 but same any help?
Sent from my ST25i using xda premium
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Re
MagicMagicD said:
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Click to expand...
Click to collapse
Let me tell you exacly.. I had a problem with the phone .. About led so i decide to change the version and use v4 .. But i recharge it full and i had it on my desk w/o using it for 3 days. The battery was at 40 % and i use it only 1 time for 1 call .. Nothing more...
I flash the kernel wth flashtool. Wipe everything.Install Jb wipe cache and then use the phone. Wait for power off buttom then open again..
I don't know what is the recovery mode btw.. I search it but i didn't find something usefull .I still don't know if i will use Jb Unofficial yet...
I haven't tried v4 of that ROM but I can say for sure that the LED bar doesn't work very well on V5, at least nowhere near as well as DevSwift1's V3 ROM with the latest Phantom kernel.
It does seem to be quite good on battery though; I'm on 1 day, 12 hours uptime with 47% charge left, although I don't use it a whole lot to be fair -- mostly just for music during the day.
I guess you must have used a recovery to flash the ROM zip file... as in CWM (ClockWorkMod)? The Phantom kernel comes with one installed; 1.0.7 has CWM Touch whereas 1.1.0 (the latest version) has a non-Touch version.
The only thing I can suggest is that you try reflashing it again; I'll tell you exactly what I did...
Using Flashtool, put Phantom kernel 1.0.7 on the device and then go into CWM Touch by restarting the phone and repeatedly pressing the Volume Down button when you see the LED bar light up.
Once there do a wipe of data and cache and then go in to the advanced menu and wipe Dalvik cache too.
Next go back to the main CWM menu and flash the zip, then reboot and wait for the phone to start up (should take a while).
Once it has settled down restart it and let it start up again (should take less time)
Finally, use Flashtool to put the latest version of the Phantom kernel on, restart and you're done.
With all that said, I expect I'll be going back to V3 of DevSwift1's JB ROM this weekend as although it's not quite as smooth as pipi14's ROM, the LED bar does work a lot better and for me that is quite important.
Good luck, keep us informed how you got on.
A
Thanks a lot for the informations mate. You help me a lot . But i'm the only one who have this problem with led and battery?
What Jb version you suggest me to use? (link )
What kernel you suggest me to use ? (link)
Any other good apps who will help me ?
Again Thanks a lot .
Btw what is "recovery flash" . I read at pipi's site flash in recovery. What exactly is this?
I've personally tried two Jelly Bean roms:
DevSwift1's V3 ROM (it's now up to V4 which is based on an Xperia Go firmware and has lower-res graphics and some other issues compared to V3, which was ported from the Xperia P).
link
pipi14's V5 ROM (which you have tried and are currently using.)
link
As for kernels I've only used the one that came included with DevSwift1's V3 ROM and Phantom kernel's from v1.0.7 upwards. I know that a number of people have used the Experimental v8 kernel with success on JB but it looks to be more complicated than Phantom.
Experimental v8 kernel
Phantom kernel
From my own experience I will say that I think pipi14's V5 ROM is smoother but I can't get the LED bar working how I want and although it still had a few issues on DevSwift1's V3 ROM it was definitely better.
As far as apps go, it seems the fewer apps the better if you want to stick with JB on your Xperia U -- it doesn't have enough memory and the more apps you have running the worse it will be. Task killers will not help and will probably end up draining your battery more than they help.
A custom recovery is basically a low-level program that you can use to flash new kernels, ROM's and other things on to your phone. ClockWorkMod (CWM) is the most common but others are available. You must have used a recovery to flash JB to your phone before, and if you have a Phantom kernel it comes bundled with one. To get in to recovery mode you need to restart your phone and then press the Volume Down button when you see the boot logo (e.g. Phantom).
a
That's the reason why sony will not send the updates to official JB version .
I will not use Jb now . If they fix it about the bugs i will use . Thanks for the info mate
Btw i use something custom like tera check this http://forum.xda-developers.com/showthread.php?t=2141726&highlight=tera
It's nice based on the ICS w/o so much battery drain and leds bug. I suggest you use this .
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
I have a Galaxy S2 i9100. I was wondering if it's a known bug that sometimes the screen never turns off unless I press the power button? No matter what I set Display -> Sleep to, the screen often never turns itself off. I can't see any pattern to it for when it works and when it doesn't. Is there any known apps that can mess with it, like NoLED?
Am on NeatRom v2.4.1, no such issue here.
Try wipe cache and dalvik from recovery, then report back please...
Another question, are you looking at your phone and waiting for it to turn off?...
If yes, Smart stay causes it to stay awake...
Disable it from Settings>Display>Smart Stay...
marjune23 said:
Am on NeatRom v2.4.1, no such issue here.
Try wipe cache and dalvik from recovery, then report back please...
Another question, are you looking at your phone and waiting for it to turn off?...
If yes, Smart stay causes it to stay awake...
Disable it from Settings>Display>Smart Stay...
Click to expand...
Click to collapse
Apparently my phone isn't too smart, for this is no such option under Display. What does that mean?
Well right now, and since I wrote this thread it's been behaving like a dream and I can't make it not work. Yesterday, for the life of me, the screen wouldn't go out.
djondjoe said:
Apparently my phone isn't too smart, for this is no such option under Display. What does that mean?
Well right now, and since I wrote this thread it's been behaving like a dream and I can't make it not work. Yesterday, for the life of me, the screen wouldn't go out.
Click to expand...
Click to collapse
Oh forgive me, I was thinking of v5.6 hahaha...
Please disregard the Smart Stay, that is not present on NeatRom AOSP v2,4.1...
Just do my first advice, wipe cache and dalvik from recovery mode...Then Reboot...
1. Reboot to recovery...
2. Wipe cache partition...
3. Advance>Wipe Dalvik...
4. Reboot your phone...
Alas it still often doesn't turn off the screen after wiping the caches. Tried as low as a 15 second sleep but no dice.
djondjoe said:
Alas it still often doesn't turn off the screen after wiping the caches. Tried as low as a 15 second sleep but no dice.
Click to expand...
Click to collapse
Oh thats bad...would you consider reinstalling the Rom without full wipe or full wipe again?...
I guess it will solve now the issue....
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.4.1
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
For now I'll try to live with it. I can confirm that a reboot fixes the problem for some time.
I still can't find any pattern to it. I tried shutting down all active programs, but when it's in no-turn-off-screen mode there's nothing to do but reboot. This has happened every day so far.
djondjoe said:
I still can't find any pattern to it. I tried shutting down all active programs, but when it's in no-turn-off-screen mode there's nothing to do but reboot. This has happened every day so far.
Click to expand...
Click to collapse
Sorry to here that mate...
It looks like you need to do a full wipe now...
Optional, do a nandroid back up...
1. Flash compatible KK cwm...
2. Wipe data...
3. Wipe cache...
4. Wipe advanced>dalvik...
5. Format cache, system, data and preload from mount and storage...
6. Flash Rom and Gapps.
7. Reboot and enjoy...
8. Report back please...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.4.1
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version? I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
Maybe there's something I don't quite understand, if so please educate me
djondjoe said:
I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version? I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
Maybe there's something I don't quite understand, if so please educate me
Click to expand...
Click to collapse
Before we start the lesson, let me ask you first if your issue has been resolve already?...
Don't worry I won't give up on you until I satisfied you baby hahaha...
Q. I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
A. How did you manage do flash Rom without flashing compatible KK CWM Recovery?...Unless you came from another KK Rom, it is possible...
It is necessary coz simply it is the basic requirement of KK Roms (with maliV3 drivers)
Q. Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version?
A. Yes, as you can see in Post #3 in NeatRom AOSP thread (last paragraph)...although it is already integrated with Philz kernel...
Q. I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
A. CWM are just type of recovery. Other than CWM there is what you called TWRP (touch wiz recovery program, which is used by NeatRom AOSP)). TWRP is more on just tapping on your screen to navigate your recovery.
So you need to find compatible CWM or TWRP to be able to flashback to 4.1.2. And same with Kitkat, you need to find compatible CWM or TWRP.
But there are some kernels who is now working to be able to handle to flash a KK or Jellybean. (e.g. is Dorimanx Kernel)
Well my phone is living a life of it's own. For the last three days the screen has worked fine except in the afternoons and evenings where the screen doesn't turn off by itself. I must say I am puzzled. I still suspect NoLED of having something to do with it all.
Yes I came from Omega ROM, and before that Cyanogenmod and others. I guess I only manually installed CWM the first time I rooted the phone. All the other times they were included in the ROM, so it's new to me I need to do it manually to revert from NeatROM. Let's say I want to try NeatRom 5.6, I can't just download the ROM and install it with Philz KitKat CWM Recovery which I already have installed? If no, what exact CWM must I use?
djondjoe said:
Well my phone is living a life of it's own. For the last three days the screen has worked fine except in the afternoons and evenings where the screen doesn't turn off by itself. I must say I am puzzled. I still suspect NoLED of having something to do with it all.
Yes I came from Omega ROM, and before that Cyanogenmod and others. I guess I only manually installed CWM the first time I rooted the phone. All the other times they were included in the ROM, so it's new to me I need to do it manually to revert from NeatROM. Let's say I want to try NeatRom 5.6, I can't just download the ROM and install it with Philz KitKat CWM Recovery which I already have installed? If no, what exact CWM must I use?
Click to expand...
Click to collapse
Wwaahhh read carefully mate my comment above...if you want to go back to neat 5.6, Post #3 last paragraph....
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
I read it, don't worry
Just don't get why, but I assume it's because the KitKat CWM ONLY handles KitKat ROMs and I must revert back to an older CWM recovery for older Android versions, and I also shouldn't ask all my pesky questions and just do what I'm told :laugh:
djondjoe said:
I read it, don't worry
Just don't get why, but I assume it's because the KitKat CWM ONLY handles KitKat ROMs and I must revert back to an older CWM recovery for older Android versions, and I also shouldn't ask all my pesky questions and just do what I'm told :laugh:
Click to expand...
Click to collapse
Nice nice...safety first ...
Hhmmnnn AFAIK there were different versions of recovery...As of now it's so hard to follow....So for me I just follow instructions (ofcorz reading comments) before proceeding....but sometimes I like being risky always hahaha...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
SO close to having 10 posts now :laugh:
If I want to upgrade to 2.5, is it really the hard way with installing the ROM all over and having to reinstall all apps? I thoughtthese custom ROMs all had an upgrade functionality in a menu somewhere.
djondjoe said:
SO close to having 10 posts now :laugh:
If I want to upgrade to 2.5, is it really the hard way with installing the ROM all over and having to reinstall all apps? I thoughtthese custom ROMs all had an upgrade functionality in a menu somewhere.
Click to expand...
Click to collapse
If you want to retain your apps do dirty flash...but if something went wrong or you want fresh installation do the full wipe...see post below...
http://forum.xda-developers.com/showthread.php?p=49887400
Ooopppsss just a tips also, please hit thanks button if somebody help you on their comments to your post
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
Thanks!
I guess I'll be dirty then. What are the odds of success and no boot loops?
djondjoe said:
Thanks!
I guess I'll be dirty then. What are the odds of success and no boot loops?
Click to expand...
Click to collapse
As you can see on my post 1% fail and 99% success...
The only main problems sometimes why bootloops occurs is users don't follow the steps provided to them...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...