What files are independent in cm9 vs cm7 and can stick around causing cm7 to have issues?
is there a verbose boot, or a boot that shows current CPU speed?
i believe when i go back to cm7 i am running at a max of 200mhz during boot which is god awful for the software.
ok so i had aokp on the phone all night after 14 hours of struggle yesterday.
CM7 was always SLOW!!!
anyhow i was on AOKP, i only did a format data/wipe factory in recovery. just the one option
and installed cm7. just worked. smooth. fast.
so i rebooted, installed gapps. then wiped system, reinstalled cm7 and gapps.
and all worked fine.
the only difference from yesterday was i went back to ics to go back to cm7
also cm7 yesterday my first flash was the newest build. but i had gone to stock, back to new/back to old (may 1st) a few times
today after my first flash was may 1st.
i dont know what it was. seems fine. i will inform if it changes.
I added some alarm tones, and they werent visible from the alarm clock so i rebooted, and it rebooted in the slow mode. so i did a reboot again and then held power while i saw samsung, and it booted normally again. i wonder if my phone is crapping out on me
Related
Appologies for not replying to the original MIUI thread. I am not a new user and i am very experienced in flashing roms etc, especially on samsung devices. I have been around for a while now but this is my first post so i cannot post in the dev section yet.
Last night i flashed MIUI to my infuse. I followed the instructions in the op here exactly.
http://forum.xda-developers.com/showthread.php?t=1278053
I had no problems flashing and everything was successfull, however there were 2 major issues. First being the soft keys. The four buttons menu, home, back, and search buttons did not function at all. They werent even backlit. The volume rocker and power buttons functioned fine. I reflashed from blue cwm twice and still nothing.
This is where i ran into my second issue. There were no posts about anyone having the soft key issue however i did notice alot of people losing their recover and being stuck on the samsung boot screen. This eventually happened to me.
I went to samfirmware and downloaded 2.1 and odin'd it, then odin'd the community kernel to get ext4 and red cwm then restored my nandroid so i am back to normal. I wanted to post about my soft key issue but as i said i had to post in q&a due to my lack of posts.
Any suggestions? if not, i at least wanted to inform the dev of the issue.
Thanks
have you tired CM7, just asking cuz they have almost the same bugs....so i would curious to see if your softkey issue transfers to that rom as well. and if not........
i would try loading up CM7, wiping from the orange CWM and flashing MiUi from there. it Should have worked the way you did itk if you were coming from stock. but who knows maybe seeing if it happens on Cm7 will lead to your answer.
just an idea though
no i havent been able to try cm7 yet as i dont have a build environment set up anymore and havent seen a release yet, would love to give it a shot if someone wants to send me a zip.
i really hope it doesnt have the same issue or ill have to donate this thing to my fiance and get a gs2 or something lol.
Check your mail, you seem to know what your doing so test it out see what happens.
Happy Flashing
Happy flashing indeed, thanks for this im going to give it a go right now, bbl with results.
Hell the only reason i was flashing miui to begin with is b/c i am currently unable to build cm7 so hope this works..
Thanks a ton!!
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
powdered_donuts said:
Ok so heres how it went down.
After my fail last night with the softkeys i did a little research and flashed serendipity s7. So with the cm7 zip you sent me i started out flashing over this since they are both ext4 i didnt think there would be a prob.
Followed your instructions, wipe, flash, pull battery, wipe, flash. After the first flash i was in orange cwm. I didnt give it a chance to boot until after the second flash obviously, but it would boot directly into orange cwm everytime.
From there i decided to odin to stock and flash the community kernel again.
Now that i was back in red cwm and formatted to ext4 i repeated your original instructions and everything flashed just fine.
As far as the soft keys, i have no issues at all. Everything is working just fine.
I was flashing from 2.1 uke3 last night, and thats also what i flashed with tonight and was successfull with.
Anyways thanks for the help glad to say im not having the issue with cm7. much appreciated
--forgot to add i am going to try to reflash miui coming from cm7 and see how that goes if i still get the same issue
--Okay, booted to orange cwm, wiped and flashed the same miui zip as before. Only one wipe and one flash no battery pull or anything. Everything flashed perfectly and my soft keys are functional. Not quite sure what the deal was before but miui is booting just fine. I'm afraid to boot recovery to many times as everyone seems to lose it after a few uses. We'll see how it goes for now, never been an miui fan to iphoneish for my taste but until i can build a recent cm7 rom i need something, was getting bored with rooted stock.
Thanks again for your help!
Click to expand...
Click to collapse
Glad it all worked out.....
Hi,
so here's my situation: I've previously installed CM7 by tj_style (http://forum.xda-developers.com/showthread.php?t=1167750) on my phone and everything was working fine.
About a week ago, I flashed an overclocked kernel by squadzone (http://forum.xda-developers.com/showthread.php?t=1344440) (I flashed the 782MHz kernel, but after that for a while and getting a lot of shut down, I turned the max frequency to 715, which stabilized the phone) and again, it worked well.
I downloaded an app called Cpu Tuner from the market (https://market.android.com/details?...SwxLDEsImNoLmFtYW5hLmFuZHJvaWQuY3B1dHVuZXIiXQ..) because I wanted to try a new cpu tool (Had Antutu's Cpu Master free edition before). I used the "Check phone's capabilities" option on the Cpu tuner, and all of a sudden the phone just reboots straight into recovery mode. I try rebooting the system, and it gets stuck at the CyanogenMod logo, starts looping it without ever actually booting into the system.
I've already tried wiping data and cache (a lot), going back to stock Gingerbread, which by the way, does the same thing, loops the Samsung logo, re-installing the CyanogenMod and just about everything that comes to mind..
Is there anyone with a similar problem or any idea on how I could fix this?
PS: sorry about all the links, thought it might make it easier if it was clear what I was talking about
Okay, so I managed to get the phone working after all. I was already pretty hopeless, I read a few threads about the Riff Box and was ready to send my phone to the service, but I wanted to take a few last shots at it.
I got it to work by first flashing back to froyo, a package S5570XXJL9 that had separate files instead of a one package, then Gingerbread S5570XXKPI again with separate files, then to clockwork and finally CyanogenMod 7
Hopefully this thread may be of use to anyone facing the same problems as I've faced
Hello! Long time lurker, first time poster. I finally got around to making an account.
So, I'm having an issue when applying Da_G's overclocking kernels (Here).
The issue proliferates when I go into CWM and apply the AT&T .42 kernel and the 1.83ghz overclock script from the recovery menu. Basically, after cleaning the cache and the dalvik cache, I apply the .zips of the .42 kernel and the script, and reboot, and then I get a restart cycle that ends after the Samsung screen. I went ahead and did a full wipe of the phone, restored via ODIN to stock, and then tried flashing it again and this time I got to an "Android" logo followed by the same power cycling (this time with the camera LED flashing).
The strangest thing is that before I took my first Skyrocket back for dead pixels, I had gotten it running just fine before. But the last two I've had won't do it and get stuck in the aforementioned restart cycle.
I decided that it really wasn't worth the risk of bricking my phone (since I just got out of my 30 day warranty and had to take the phone back twice for dead pixels and the phone not turning on one day), and I guess in the end I'm just curious as to why I was having this issue. I guess if it's something stupid I'm doing, I'd go ahead and do it (especially since I have plans for that performance boost).
Anyways. Feedback appreciated.
The 1.83 isn't very stable that's what's causing the problems. Go one step down on the script
Alright, I'll try it right now. Maybe it was a fluke that it worked the first time.
EDIT: It booted up, but, then it shuts off when I open CPUTuner, but, they're talking about that in the official thread. Thanks!
1.83 is not stable and 1.78 and 1.72 are most stable with oc.
Sent from my SAMSUNG-SGH-I727 using xda premium
After running it for a few hours, now I'm getting Sleep of Deaths. I really want to speculate that it's the .42 version that I'm running, but, I haven't tinkering with it enough. I think I'll try downgrading to .3 to see if that fixes the issues, as that's what people seem to be saying is the most stable, and it's the one I ran before.
And if that doesn't work, eh, I'll flash back to stock kernel. Thanks guys.
Edit: Yeah, still getting SOD, flashing stock.
Did you try deleting your modules folder?
I had the same problem, 'cept I cranked it to 1.89ghz. I just flashed the stock att kernel and everything worked fine
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
well, regarding the screen issue, use the battery all the way, til it shuts down. then rwmove the battery n press the powere button as if u were turning on ur phone. then let the phone be still over a night. then re-insert the battery n plug the phone into charge but BEWARE THAT U WILL NOT TOUCH THE SCREEN AT ALL, TIL IT'S FULLY CHARGED. i tried this solution, n it worked. maybe so did it for u :-??
n about the lags, i recommend u to install Seeder 2.00 which is recently released n can decrease the lags as much as possible. and also u could try out making 256/128MB swap with 100% swappiness using Kernel Tuner v4. alsi set these settings IN THE ORDER I'VE TYPED in venom tweaks --> misc --> minfree settings
4
8
16
32
48
64
got no more idea
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
wildcardspv said:
Hi there,
I hope someone out there can help me fix my wife's sensation XE. We both have the same phone and generally the same ROM with no issues, but here's where we are now (apologies for length)
Background
A couple of months ago, she was running Viper 1.5.2. No issues, happy days
One day the screen just stopped responding while she was using either the official Facebook app or the stock browser (she can't remember which). She could wake the phone up but could not unlock it. The screen was perfectly responsive in recovery (4ext) so the problem was only apparent when the ROM was booted up.
I downloaded the latest version of Viper (as a more recent version had been released), fully wiped with superwipe.zip and flashed it.
Strangely, after flashing this, Aroma gave the option to reboot (as usual) and I selected yes, which then led to 'installation failed/installation aborted'. I then had to fully wipe again, flash the ROM again and say no to rebooting through Aroma, so I could manually reboot - which worked fine.
Unfortunately, the same problem with the screen was there right from the beginning as soon as the new version of Viper was booted up.
.
I went back to recovery and manually wiped data/cache/dalvik, as well as formatted system and boot, flashed the ROM again and it was still the same!!
I then fully formatted her SD card using Gparted and reflashed Viper, but it was still the same!!
I then went back to recovery, fully wiped everything again and flashed a different ROM (Elegancia 3.6.0 - sense 3.6) which worked fine straight away once it was booted up.
This seemed to clearly show that something about Viper ROMs had led to this.
Since then, I have flashed some other ROMs for her:
Elegancia 3.7.0 - worked fine
Viper 1.6.0 - screen locked up from the outset
Hypernonsense - worked fine
NB - Every time I flash any ROM, if the reboot option is selected in Aroma, the installation still fails. I have never, ever had this happen on my XE and I flash new ROMs all the time, from sense 3.6 to sense 4.x to MIUI.
The current problem
The problem is that her phone, is generally laggy, seems to run out of battery quickly and freezes a lot until it either catches up after several minutes (but is still then a bit laggy) or she has to pull the battery, regardless of what ROM she has been running. Again, mine has never had this problem and this has only been happening to her phone since the day that it first froze.
Her usage had not/has not changed, and the phone was running well before then, so I don't believe she is causing the lag/freezing/battery issues which she now has - it must stem from whatever caused the initial freeze on Viper 1.5.2.
I feel like due to the fact that full wipes, and formatting her SD card have not helped, the card cannot be the problem, plus I feel the fact that Aroma is no longer able to get the phone to reboot may point to a problem with the phone itself.
Can anyone help me to establish if there is a problem with the actual phone and if so, advise me if there is a way I can reflash/reset the phone itself, or whatever may be needed to get it back to how it was before this happened?
Also if it's not the phone itself and anyone might know what actually has happened, please, please enlighten me!!!
Many thanks for reading this and thanks in advance for any replies.
wildcardspv
Click to expand...
Click to collapse
Install TWRP (TeamWin Recovery Project) and use that to flash ViperS once more (after doing a full wipe of course). Since the only recovery that allows the installation of kernels on an S-ON device is 4ext, you will need to extract the boot.img file from the ViperS installer .zip and flash that using fastboot. Detailed instructions on how to flash a boot.img file through fastboot can be found here: http://forum.xda-developers.com/showthread.php?t=1752270
I don't really trust 4ext because 4ext gave me a lot of weird and nasty bugs. Using TWRP is worth a shot.
So over the past few weeks I've been extremely flash happy. I've practically flashed every ROM in the dev section besides the JB roms that have broken radios. The latest ROM I flashed to was MIUI V4, it was super SUPER laggy and sluggish so I decided to go back to my all time favorite ROM of eaglesblood 4.0.4 AOSP. I flashed the rom, my favorite kernel (trinity g2x ics OC), new baseband fix and ICS Gapps package. Everything went fine at first boot except for the fact that I had no battery meter. It was gone. When I went into settings > battery it said my battery percentage was 999%. I figured it must have been something I did to the ROM zip as I modded battery icons in eaglesblood a few weeks prior may have had a corrupt file or something. So did a fresh download of the ROM. Flashed everything again, in the exact order and had the same problem. From there, I went back to my trusty nandroid backup of vanilla CM7 and my battery meter is working just fine. I cannot find a solution on the internet to what would make my battery icon, stats and overall detection completely disappear. Any ideas?