Related
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.
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
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
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
blkhrt13 said:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
Click to expand...
Click to collapse
Did you flash any audio mods or new firmware?
loonatik78 said:
Did you flash any audio mods or new firmware?
Click to expand...
Click to collapse
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
blkhrt13 said:
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
Click to expand...
Click to collapse
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
loonatik78 said:
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
Click to expand...
Click to collapse
Actually every single time I flash a new rom, I go into advanced wipe and wipe system, data, cache and dalvik cache 3 times. Every Time. But I flagged that new firmware and was rubbing digital high rom from the Verizon thread and did not have the music issue. I'm running fluent rom sense 7 from the Verizon thread now but have not tested the music yet But will update you guys in the morning. Thanks for all your replies