Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
galamdring said:
Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm thinking that there must be something off in the bootloader. I'm hesitant to go playing with it since that is a quick road to bricking. I might dissect the boot.img that is included in the cm10 zip. I'm thinking there is a missing module, or something similar.
Any input would be appreciated.
New update. I was able to get back to CM10. I had forgotten to wipe data. Thats what I get for flashing when half asleep.
Still trying to understand what happened to stop my cardock from working. Charging in the dock works fine, but it doesn't start car dock mode, or push audio through the usb. I'd really like to get that working again.
Related
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
Will I need to flash the stock kernel back on my phone to take the OTA or will it work with Imo's kernel? I tried to reflash the boot.img from my nandroid and wifi was not working, so I reflashed Imo's kernel and wifi works again and I am sitting in a holding pattern. I'd rather not have to ODIN back to full stock because I only have access to PC's at work and don't really have time in the day at work to be doing stuff like that while there.
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
What exactly makes you want the update? If it's the radio (which imo is the only reason to consider the OTA) then just get the radio and flash it in CWM.
i already have the radios flashed but I've had this weird issue that seems to only happen after flashing the kernel but has only happened on a few occasions mainly on the weekends at my daughter's 2 soccer games to be exact. Camera and video have acted weird, first was video controls were upside down, had to reboot a few times for it to fix and just yesterday everything I shot shows fine in gallery but when I go to import into Instagram the pics are all rotated 90 degrees.
I can't afford to have data issues which is the reason I haven't installed a custom ROM since I use my phone for work quite a bit. Figured go back to stock kernel, take OTA to clean out any weird issues that would linger and wait for either official JB or for ROMs to get solid on data issues.
mav3rick478 said:
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
Click to expand...
Click to collapse
Yes, but remember if you don't already have the OTA notification nothing with come just because you removed the custom recovery. If you've already received that notification then disregard this post.
Sent from my SCH-I535 using xda app-developers app
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
mav3rick478 said:
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
Click to expand...
Click to collapse
No problem. If you still notice weird issues then Odin to an older firmware and accept the OTA from there.
Sent from my SCH-I535 using xda app-developers app
I've had my S3 for about 3-4 months or so, and I've recently been having this problem.
The day I got it I rooted it and everything was going good, battery wasn't amazing, but definitely reasonable.
After the boot loader was unlocked, I unlocked it with the EZ unlock in the Play Store.
I then loaded up Synergy r50 (nightly at the time) and everything seemed improved.
Anyways, I have since then loaded Paranoid Android, CM10, Beans, and Incubus' Jellywiz.
I went to Beans after Synergy, everything was still fine, then I loaded up Jellywiz RLS7 for a day, and it ran extremely warm and I was dropping
a percentage of my battery every 2 minutes. I nandroided back to Beans, and had the overheat and battery drain problem on that too. I wiped everything and went to Synergy (newest nightly, forgot the number) (edit: added the ktoonsez kernel after many FC's) and the problem still exists. I'm also getting horrible cell signal (not 4g, 4g is fine) at my school where it used to be perfectly fine. Anyone know what I could possibly do besides returning it? I already used Odin to go back to the latest non-leaked stock, and it's still doing it. Thank you very much.
TL;DR: After flashing multiple roms, then flashing Jellywiz, my phone runs much too hot for comfort, borderline burning, battery life goes fast, and I get next to no signal at my school.
Thanks again for any help!
chisandwich said:
I've had my S3 for about 3-4 months or so, and I've recently been having this problem.
The day I got it I rooted it and everything was going good, battery wasn't amazing, but definitely reasonable.
After the boot loader was unlocked, I unlocked it with the EZ unlock in the Play Store.
I then loaded up Synergy r50 (nightly at the time) and everything seemed improved.
Anyways, I have since then loaded Paranoid Android, CM10, Beans, and Incubus' Jellywiz.
I went to Beans after Synergy, everything was still fine, then I loaded up Jellywiz RLS7 for a day, and it ran extremely warm and I was dropping
a percentage of my battery every 2 minutes. I nandroided back to Beans, and had the overheat and battery drain problem on that too. I wiped everything and went to Synergy (newest nightly, forgot the number) (edit: added the ktoonsez kernel after many FC's) and the problem still exists. I'm also getting horrible cell signal (not 4g, 4g is fine) at my school where it used to be perfectly fine. Anyone know what I could possibly do besides returning it? I already used Odin to go back to the latest non-leaked stock, and it's still doing it. Thank you very much.
TL;DR: After flashing multiple roms, then flashing Jellywiz, my phone runs much too hot for comfort, borderline burning, battery life goes fast, and I get next to no signal at my school.
Thanks again for any help!
Click to expand...
Click to collapse
Did you try to odin back to Stock, get the new OTA and maybe odin the leaked radio on top? I'd give it a try and see how it works out for you 1-2 days. People are reporting better single with the leaked radio. You flashed a lot of stuff in a very short time and you missed the latest official radio from the G7 OTA.
If you still have issues return the phone to VZW. If not DebugFS, EZ Unlock (make sure to use version 1.2 from rootzwiki) and EZ recovery again. Make a clean Nandroid and go back to your favorite ROM.
All the downloads you need can be found in droidstyle's sticky in devel.
BlackBytes said:
Did you try to odin back to Stock, get the new OTA and maybe odin the leaked radio on top? I'd give it a try and see how it works out for you 1-2 days. People are reporting better single with the leaked radio. You flashed a lot of stuff in a very short time and you missed the latest official radio from the G7 OTA.
If you still have issues return the phone to VZW. If not DebugFS, EZ Unlock (make sure to use version 1.2 from rootzwiki) and EZ recovery again. Make a clean Nandroid and go back to your favorite ROM.
All the downloads you need can be found in droidstyle's sticky in devel.
Click to expand...
Click to collapse
Thank you very much! I just finished installing the OTA and I'm about to flash the leaked radio through Odin.
I'll post back in a few days or so in case this doesn't end up working or if any one else is having this issue and doesn't want to post (much like I was until I realized I can't stand the issues I was having)
Hopefully this works, thanks again!
(If anyone else has any other remedies for this, would be nice to post just in case this doesn't work, thank you)
chisandwich said:
Thank you very much! I just finished installing the OTA and I'm about to flash the leaked radio through Odin.
I'll post back in a few days or so in case this doesn't end up working or if any one else is having this issue and doesn't want to post (much like I was until I realized I can't stand the issues I was having)
Hopefully this works, thanks again!
(If anyone else has any other remedies for this, would be nice to post just in case this doesn't work, thank you)
Click to expand...
Click to collapse
you are welcome,
by the way - try to avoid Jelly Bean ROMs like CM10 or AOKP. They all have issues with the RIL and we have to wait for someone to figure out a fix or an official JB TouchWiz leak.
Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!
Are you sure it is due to CM? I have the same issue with the stock Rom rooted.
Well it only happens on any nightly past the experimental M1.
Have you tried a clean flash? Or have you just been doing dirty flashes over and over?
Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium
Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh
Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app
Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium