Related
Hello Everyone,
I had this random reboot problem and posted it in various forums on the web but had not found the root cause of the problem.
But now I seemed to have completely solved it. Here is how for those experiencing similar issues.
1. If you are having it from just few days, then it is surely got to do with the phone trying to fetch data when the signal strength is very low. I found out that -113dbm is the least signal possible and the phone displays a '+' mark in the signal status notification bar. Hence when the signal goes to somewhere near -112dbm and -102dbm the phone goes into a reboot.
So if this is your problem, then you need to download "Shutupbatterymanager" from the market and set the phone to turn off data connections when the signal is below a certain threshold. It is also attached in this post below. For example you can slide the signal bar in the app and set it to -102dbm cutoff after which it will disable the data connections. This is one way of solving the issue if you have had reboot problems occur very recently.
2. The best way to solve this issue is to compromise on your 'downgradability'. For me the above option did not work well after a few test runs and then I accidentally found out that flashing this file (thanks to Higgsy for making this) is the best way. Maybe motorola found out the issue after numerous posts in their support forum and has solved it with a change in the kernel. So just download the file and flash the froyo 2.2 GB UK sbf file with your RSDlite.
It would be helpful if someone can post their kernel version. The flashed one after using this file that seems to solve the problem is [email protected] #1
Hope it solves all your reboot issues. Google you can please index this for some much needed help for desperate Defy owners.
Thanks to: Higgsy and Sorensiim
PS: Important point i forgot to mention is that the change in the kernel is reflected when you get into recovery by holding Vol down + power button. Here if you are on newer and changed version, touching the corner of screen does not work. Instead pressing the volume rocker simultaneously up+down will enter recovery functions.
Substantially is the UK 3.4.2-117 sbf that have you flashed?
alezzandro said:
Substantially is the UK 3.4.2-117 sbf that have you flashed?
Click to expand...
Click to collapse
Yes, but it is not the complete sbf. Some segments have been knocked off and it has been repacked by Higgsy so that there is no locked bootloader and downgradability problem.
Which means the complete SBF already has this fix built-in?
Yes it should.
Sent from my MB525 using XDA App
okidoki - thanks good to know
I would verify the change by going into stock recovery.
Sent from my MB525 using XDA App
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
OK before I get confused with the build numbers do this. Power off phone and boot with power button and volume down. Once recovery appears tell me if you are able to enter recovery using the corner of the screen or is it through pressing the volume rocker up and down simultaneously.
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
mrt3k said:
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
Click to expand...
Click to collapse
OK then you are already on the newest froyo kernels and not on the eclair ones which had the problem.
Now tell me, is your rebooting problem still there?. When do you face it? What is your observation?.
i think if you are using pays rom, then you must've flashed the whole sbf already. you don't need to flash this partial old sbf, since the new sbf should include the old fix (of course some assumption here, hehe) you probably can't downgrade using official sbf either...
mrt3k said:
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
Click to expand...
Click to collapse
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
mrt3k said:
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
Click to expand...
Click to collapse
OK then. Continue your observation on the sim card and come back again to report if this occurs again. All the best.
Ok I will do so. Thanks for your help!
But apart from the hint on the sim-card (which is not yet proven) - Any idea? Do we know that the brand new kernel does not have the error anymore? Or could it still be part of the release if Moto did not realize and fix it?
So, do you see any other thing that could cause all the reboots?
Every rom out there has ways by which you can still maintain downgradability. I did the same. I loaded chinese sbf and then tried various roms by restoring it by nandroid backups. Also people like jboogie and higgsy give boot only and safe sbfs which can be tried. For me flashing the above attached sbf from higgsy and restoring the rom posted by Iaoa PL deblur solved the problem totally.
Sent from my MB525 using XDA App
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
mrt3k said:
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
Click to expand...
Click to collapse
Yeaaah, thats some good news. Enjoy your Defy
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
mrt3k said:
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
Click to expand...
Click to collapse
This is exactly the same problem I had. Why dont you do this. Flash the new poland leaked sbf and then restore nandroid backup from Iaoa. He has a rom for the same poland version.
This solved my problem. Hope it works for you too.
And please remember that you can get back to 2.51 roms and nothing below that if you flash this sbf.
I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?
Nandroid restore, if that won't work nvflash?
you mean use NVflash to do the rom install vs the recovery?
I made a topic about this, check my post (not able to give you a link right now sorry)
I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?
Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612
You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.
I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.
This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.
Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.
If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app
It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8
rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.
The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.
Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!
You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.
I would have posted this in the Sensation Android development area, but I don't have sufficient privileges to do so.
I no longer have WiFi.
I am using the 4.1.2 CM Kang, and I originally had WiFi working with that ROM, but it stopped working about a weeks ago, and I can't get it to come back.
If I watch the Wifi on/off toggle, I can see it blink white for a split second then return to grayed out about once every 5-10 seconds.
I've checked the WiFi settings, and the only thing that looks peculiar is that the region code under Advanced says "Europe," but when I try to change that, it just reverts.
I have tried a factory data reset,re-flash of the ROM, and installing newer versions of the ROM with no luck.
Does anyone have any suggestions?
tried this ?
WiFi will not turn on
ganeshp said:
tried this ?
Click to expand...
Click to collapse
I tried to install WiFix Manager, and I followed the directions closely, but WiFi still will not turn on.
The country code always reverts back to Europe in the Advanced WiFi Settings.
I'm on T-Mobile US, running AOKP aokp_pyramid_unofficial_Oct-19-12.zip; a JB ROM; 4.1.2
I previously tried the CM10 Kang for the HTC Sensation, but switched ROMs to make sure that it wasn't issue with the ROM.
To be clear, my problem is not that the WiFi radio never locks to a particular signal, it's that the WiFi radio won't even turn on.
When I go to WiFi settings it just says, "Turning on WiFi...," and never actually turns on.
My best guess was that it had something to do with the WiFi country code, but that's really just a stab in the dark; open to suggestions.
Thanks
bump
Surely, there's someone out there that can help?
kosstheory said:
Surely, there's someone out there that can help?
Click to expand...
Click to collapse
In order of easiest and quickest to longest time it will take to do each one...
Install the latest version of the ROM (10/23) overtop of your existing rom (5 minutes)
If that doesn't work...
Do a full wipe and install a fresh copy of the latest version. (15 minutes, with Nandroid backup)
If that doesn't work...
Format your SD card (save all the contents to your computer first) (40 minutes between copying every to the computer and back to the SD card)
NON ROM RELATED OPTION IF YOU ARE S-OFF
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops. (5 minutes, but a little more involved)
My guess is that the full wipe and fresh install is the most likely to work the first time.
Skipjacks said:
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops.
Click to expand...
Click to collapse
is there a sensation specific guide for this procedure?
Still perplexed
How do I know which kernel and radio combination should work best with my ROM. I switched out to AOKP to see if that was the problem, and I believe I'm using the 3.33 Kernel, but I don't know how to check to make sure it installed correctly.
Had the same problem as you but a full wipe and reflash would bring it back. Seems to be a CM10 problem since it happens with Bruce's and Paranoid roms. Try a Sense rom and see if wifi works.
Is OpenSense considered a "Sense ROM?"
http://forum.xda-developers.com/showthread.php?t=1926858
Try that rom, more stable and better performance than all the popular roms.
I had the same problem only option was another room Android_Revolution_HD-Sensation_6.8.0 (this is the rom)
so long, and thanks for all of the fish...
I figured it out.
I bought a Samsung Galaxy S III. WiFi is working again.
Thanks for all of the help!
wifi cm10
I have tried several CM10 roms. It is as you said about the region code. It reverts back to the original and doesnt save it on the settings
Even though editing db file doesn't work. Actually it changes the country code. I guess the ROM changes it during booting. Because while it boots you can see that the wifi is connecting first then goes off. I have tried several roms. DOnno what the problem is. probably JB both on cm10 and aokp
This has happened to me several times and I am seeing that other people are running into this problem with no fix found.
Everytime I try to install CM10.2 onto my xt926 I can never get past the unlocked bootloader warning screen after a reboot. I can still access CWM which is the recovery I'm using. I have tried clearing cache, data, factory reset, fixing permissions, reflashing the rom. The only way to get a working phone again is to flash stock 4.1.2 using RSD.
Then I remembered seeing an article a while ago saying that their were two versions of an OTA update for Razr HDs because for some reason their were slight differences between some phones, hardware wise.
Could this be the reason for these random phones not accepting CM10.2 installs?
Also if anyone has any ideas to get past this. I read someone had luck toggling bluetooth on and off for some reason but it didn't help me. I'm at a loss here and would love to play with Android 4.3 but I guess its just not in the cards...
ive got the same problem to i finally decided to get rid of safestrap and unlock my phone. now im stuck on stock rom because no roms will work after a reboot. theres two diferent stock 4.1.2 firmware files. one says mr4 the other one says mr2 anyone know the diference?
Not sure. I just use the RazrHD Utility 1.21 for that, its a lot easier. Also I have heard that 10.1 may work for us, just not 10.2 for whatever reason
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: