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...
Related
I have a bell Galaxy S2. Today I rooted it and after hours of confusion, I finally managed to install resurrection remix 4.04 ICS on my phone.
So far I've run into tons of issues:
1) No GPS
2) No wifi (stuck on 'obtaining IP address, unlikely that this is my network's fault)
3) No software buttons, so I can't multitask (have to use task killer to kill unused apps right now)
4) Rom Control crashes everytime I go into the Navigation bar page
The phone in it's current state is useable, but I will go back to stock settings if I can't fix these problems. Maybe there is a better ROM out there? Though I heard resurrection remix is the best one. Also, could it be that I installed the wrong kernel? The one I installed is:
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Can somebody help me out? Any tips would be appreciated.
EDIT: I just realized that USB connectivity (file transfer) doesn't work either - not even in clockwork menu!
anthraxcp said:
I have a bell Galaxy S2. Today I rooted it and after hours of confusion, I finally managed to install resurrection remix 4.04 ICS on my phone.
So far I've run into tons of issues:
1) No GPS
2) No wifi (stuck on 'obtaining IP address, unlikely that this is my network's fault)
3) No software buttons, so I can't multitask (have to use task killer to kill unused apps right now)
4) Rom Control crashes everytime I go into the Navigation bar page
The phone in it's current state is useable, but I will go back to stock settings if I can't fix these problems. Maybe there is a better ROM out there? Though I heard resurrection remix is the best one. Also, could it be that I installed the wrong kernel? The one I installed is:
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Can somebody help me out? Any tips would be appreciated.
EDIT: I just realized that USB connectivity (file transfer) doesn't work either - not even in clockwork menu!
Click to expand...
Click to collapse
Sounds like you might have flashed the wrong kernel for your phone.
did you first check what was the original kernel on your phone? acutally, run me through your root process so i can figure where you went wrong, because the Resurrection remix rom is just about perfect
I know it was KG2 kernel originally. Don't remember the other numbers.
I'm now on a different kernel because when I used KG2, the phone wouldn't work at all (the buttons were screwy).
The process went something like this:
1. Rooted KG2 kernel installed
>Phone still works like before, but rooted
2. Put Res remix rom on my phone's storage
3. Go into clockwork recovery
4. Flash/Recovery
Format /system
Wipe Cache
5. Install ROM from SD card - twice (since the video I was watching told me to do it twice)
>Phone turns on but the buttons don't work so I can't navigate menus
6. Install CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
>Buttons sort of work now but lots of problems
>All of my old files/music are still on the phone despite all that format/recovery stuff. Is that normal?
Now when I try to install KG2 kernel phone doesn't even turn on. If it helps, the phone currently tells me the baseband is I9100MUGKG2
k, yep you missed the gapps install. did you make a backup in CMW recovery before you flashed remix?
Mv101 said:
k, yep you missed the gapps install. did you make a backup in CMW recovery before you flashed remix?
Click to expand...
Click to collapse
*lowers head in shame*
Nope. But if I understand correctly gapps is just the google stuff (maps, gmail, etc) but that all works fine for me.
anthraxcp said:
5. Install ROM from SD card - twice (since the video I was watching told me to do it twice)
>Phone turns on but the buttons don't work so I can't navigate menus
6. Install CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
......
Now when I try to install KG2 kernel phone doesn't even turn on. If it helps, the phone currently tells me the baseband is I9100MUGKG2
Click to expand...
Click to collapse
whats wrong with you brother? installing CF-root on an AOKP rom???? CF-root is matched with the Kernel not with the Baseband.
Yourself dont know what is being flased on what.....did you make sure of your model before flashing there are many S2s I9100 /I9100G / I9100M / 9100T many more...
please read all the instrction first before attempting anything my friend...There is no substitute for reading and learning for comprehension .it is not like that any thing can be applied on anything.
I have a bell s2 and i did this
Google: how to root galaxy s2 kg2. Use the one that comes up. Will show the right cf root.tar to flash through odin
Follow these steps to the T
http://androidforums.com/galaxy-s2-...ock-root-bell-galaxy-s2-step-step-guide.html
Sent from my GT-I9100 using XDA
ooh you messed up real good! think you need to flash the insecure kg2 kernel through odin again
ZACQ8 said:
whats wrong with you brother? installing CF-root on an AOKP rom???? CF-root is matched with the Kernel not with the Baseband.
Yourself dont know what is being flased on what.....did you make sure of your model before flashing there are many S2s I9100 /I9100G / I9100M / 9100T many more...
please read all the instrction first before attempting anything my friend...There is no substitute for reading and learning for comprehension .it is not like that any thing can be applied on anything.
Click to expand...
Click to collapse
It's the I9100M (bell) and the Kernel before I started was KG2. I already mentioned this.
@kilometers4 that's the exact kernel I tried the first time (from that tutorial) but it didn't work.
anthraxcp said:
It's the I9100M (bell) and the Kernel before I started was KG2. I already mentioned this.
@kilometers4 that's the exact kernel I tried the first time (from that tutorial) but it didn't work.
Click to expand...
Click to collapse
yes it was before, but when you flashed Reserection Remix you got Cyanogenmod Kernel...
ZACQ8 said:
yes it was before, but when you flashed Reserection Remix you got Cyanogenmod Kernel...
Click to expand...
Click to collapse
Ok, some good news.
I installed the CF-ROOT KG2 kernel.
I went into recovery, formatted/wiped everything that needs to be done. (Then USB connectivity began to work!) so I put a 2.3 Cyanogen Mod on there and now everything seems to work (USB, WIFI) except for the home button. I still can't exit out of applications.
anthraxcp said:
Ok, some good news.
I installed the CF-ROOT KG2 kernel.
I went into recovery, formatted/wiped everything that needs to be done. (Then USB connectivity began to work!) so I put a 2.3 Cyanogen Mod on there and now everything seems to work (USB, WIFI) except for the home button. I still can't exit out of applications.
Click to expand...
Click to collapse
I dont understand what are you doing, it is your phone and up to you...do any experiments you want...
but dont ask for support when you get into deep treble with your stupidity doing without reading and knowing.
CF-root will not work with AOKP roms.
ZACQ8 said:
I dont understand what are you doing, it is your phone and up to you...do any experiments you want...
but dont ask for support when you get into deep treble with your stupidity doing without reading and knowing.
CF-root will not work with AOKP roms.
Click to expand...
Click to collapse
Yes but I can't find any other rooted kernels out there that will work for my phone. I've googled it but all the GS2 rood/mod tutorials I've seen use CF-Root.
If you can let me know what kernel or rom to install that would be great. I'm not going to touch my phone until I figure out what to do.
anthraxcp said:
Yes but I can't find any other rooted kernels out there that will work for my phone. I've googled it but all the GS2 rood/mod tutorials I've seen use CF-Root.
If you can let me know what kernel or rom to install that would be great. I'm not going to touch my phone until I figure out what to do.
Click to expand...
Click to collapse
Why not start with a working phone + a nandroid backup before you start playing with roms .
Stock rom + CWM and root kernel = Nandroid backup .
If CM does not work then read the CM thread faqs and instructions .
jje
first of all get into reserection remix thread and ask whether this ROM supported for I9100M or not, if yes ask somebody can provide CWM flashable CM9 kernel (if it is the original kernel of your rom) then flash from CWM and try..
ZACQ8 said:
first of all get into reserection remix thread and ask whether this ROM supported for I9100M or not, if yes ask somebody can provide CWM flashable CM9 kernel (if it is the original kernel of your rom) then flash from CWM and try..
Click to expand...
Click to collapse
It does work with 9100M.. I have the same phone and am running v1.4 flawlessly
Sent from my GT-I9100 using XDA
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 .
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:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Sent from my GT-I9300 using XDA Premium HD app
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
solarisrulez said:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Click to expand...
Click to collapse
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Guys, Thank you all, trying to reply to everyone:
Enea307 said:
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Click to expand...
Click to collapse
Thanks, maybe I'll give that one a go as first try.
converse5 said:
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
Click to expand...
Click to collapse
No, I'm pretty sure that's not the case. Checked my router admin configuration tried to enter my wi-fi pass about 30 times before giving up.:laugh:
chrismast said:
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
Click to expand...
Click to collapse
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
lefttobleed said:
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Click to expand...
Click to collapse
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
solarisrulez said:
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
Click to expand...
Click to collapse
(1) The best would be to read the mega wipe thread. I use it all the time, it will delete ANYTHING excep the external SD card (also not EFS etc, hence dont worry). Therefore you need a flashable rom on the external sd or via Odin later on. But basically your phone won't start after a mega wipe, just download & recovery will work.
Your wipes are correct I think, whereas /system is missing wich is needed, at least for SlimBean (4.3).
(2) The best would be to read the guides & kernel thread's how-to's first. It is basically the same as flashing a rom, yes.
solarisrulez said:
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
Click to expand...
Click to collapse
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Misleading title .
#There have been a number of identical posts and some have fixed by copying older WiFi files over . But you need to search and read and no i don't know where they are . .
Its not a custom rom problem but a non Samsung custom rom problem on 4.3 .
jje
lefttobleed said:
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Click to expand...
Click to collapse
Yes, reading the guides, so first of all decided to backup my EFS (coz that sounds reassuring before doing more ROM flashes) with EFS Professional from this thread: http://forum.xda-developers.com/showthread.php?t=1308546
Installed BusyBox on my phone, and I'm stuck because of a missing applet: http://cl.ly/image/1a1J1A0I3V0H.
I think I'm going deeper than what I can handle
BTW, Enea307, tried CM 10.2 (4.3) this morming, and same wi-fi problem. So it's most likely not a custom rom issue, as most of you suggested.
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
JJEgan said:
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
Click to expand...
Click to collapse
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
Done everything according to http://forum.xda-developers.com/showthread.php?t=1671969
And the firmware is also the one for my phone, and the *.zip that contained the tar (md5) is not damaged http://cl.ly/image/322h3634211J
Any ideas? thx!
solarisrulez said:
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
JJEgan said:
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
Not installed KIES yet, as I read that that's a big brother or something to Odin, and that his little brother is much better at flashing. Should I give KIES a go? Anyways, trying to redownload the firmware.
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
JJEgan said:
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
Click to expand...
Click to collapse
I had installed Samsung Drivers beforehand, before even rooting / doing anything. Did not had KIES until now.
Still cannot flash to stock firmware with Odin.
BTW in the guide: http://forum.xda-developers.com/showthread.php?t=1671969 i see that it should be blue, but mine is yellow when I connect my phone to Odin: http://img600.imageshack.us/img600/9231/odin4c.jpg and mine: http://cl.ly/image/473N1E0Q3G2X
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
IC3CR34M said:
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
Click to expand...
Click to collapse
Thing is, that I am rooted, done with Odin, by following this guide: http://www.androidrooting.com/how-to-root-samsung-galaxy-s3-gt-i9300-or-gt-i9300t-cwm-recovery/
So I have CWM, and with I tried Android 4.3 via SuperNexus, Android 4.3 via ParanoidAndroid 3.97 ROM, then, lastly CM 10.2 (4.3). With none of them did I managed to get the Wifi going.
Here is my current "About device": https://www.dropbox.com/sc/8hp04dn5o5flytd/LpoJCgZ7sK
Is this stock samsung firmware? Coz I can't tell. It seems stock, but maybe it changed with the rooting procedure.
So I repeat, only with this setup/build does the wifi work. With no other custom rom does...
I did backup and recovery to my current working wifi rom. That's how I recovered after trying these custom roms mentioned before.
Guys, help me pls, with at least flashing to the stock samsung rom with Odin or Kies (Odin failed, scroll up see my recent posts with screenshots)
Note that on my last try, Odin just froze yet again: http://cl.ly/image/0o0o0k2L3J3m
If not with Odin, then how do I restore it to stock samsung rom with KIES?
thx!
You dont do it with kies. Kies is such bull**** software. Dont use it at all. You wanna backup, use TI(titanium backup) or nandroid backup. Take a system backup from CWM. As you said in your post, u want to go back to stock, dl the stock rom, do the same procedure u did to root your phone via odin (pda, etc etc), just this time instead of the root zip file, just put the stock rom zip file.
It should take some time, and aftet its done, your phone will be as good as new. To restore the backup via TI, dont select system apps. Only the apps which are in green font or downloaded apps. Other wise u will have force closes.
Also, when u flash the stock rom via odin from your pc, you will not have root. Just a note.
You can simply remove bloatware like live wallpapers, samsung "never gonna use" features like Svoice via TI by just uninstalling them, but note, if fiddling with system apps, them make sure u take a backup.
I have written it all in simple language so that you understand every essential part and have fun with your rooted phone.
Happy to help
As always last resort restore original firmware with Kies and probably a better method than some others posted.
SEE The how to restore your original firmware using Kies post .
Sent from my GT-N8010 using XDA Premium 4 mobile app
Hello XDA Dev. I, Azeem, come to you guys with a problem and I need you all's help on solving it. Here's the story.
I was previously on Cyanogenmod 10.1.3 Stable for my phone and decided to try out the new 9-28 nightly of CM 10.2. However, when installing the rom, I rebooted in to recovery after installing it, gapps 4.3, and ajk 4.9 AOSP, but it got stuck at the Samsung logo and I could not enter recovery mode anymore nor could I boot to the homescreen. Knowing using odin to go back to stock would fix the issue, I did just that, and booted to the homescreen. Btw, I odined back to ICS 4.0.4 since I couldn't find an Odin-able tar file for Jellybean UCMD8 (if you know of any, please tell and link it to me). Anyway, I went and installed Mobile Odin to my phone and the N.E.A.K kernel ( http://forum.xda-developers.com/showthread.php?t=1614150 ) for the ICS stock ROM, booted into recovery, wiped data, cache, and dalvik cacke, installed Cyanogenmod 10.2 nightly, gapps 4.2, went to advanced, and clicked reboot into recovery.
Next thing I knew, guess what? It was back to being stuck on the damn samsung logo and I couldn't boot into recovery, yet again! I went and though why not give it another try, so I redid all the procedures I had done prior, but this time flashed the 10.1.3 stable, AND IT HAPPENED AGAIN! I was like wtf! That leads me to the question. Is there anything I can do to prevent this from happening again? I really like cyanogenmod and would love to go back, but I don't want to repeat all of this a 4th time. Thanks for your help in advance!
EDIT: Nevermind. I got UCMD8 Cooked to work, but I am scared to flash 10.1.3/10.2 because I don't want to have to deal with doing all that I did in OP again. However, I really want CM 10.1.3/10.2 back. A dilema.
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
creepyncrawly said:
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
Click to expand...
Click to collapse
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
azeem40 said:
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
Click to expand...
Click to collapse
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
votinh said:
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
Click to expand...
Click to collapse
I fixed the issue by doing the OP things and just restoring nandroid backup.