Related
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Never heard of this problem. Which roms are you loading, I would suggest asking the dev of the ROM, including all of the steps you use to install it.
Sent from my SAMSUNG-SGH-I717 using XDA
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
busybeebusy said:
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
Click to expand...
Click to collapse
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
omniphil said:
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Click to expand...
Click to collapse
Did you flash the ATT fix after flashing RC7? If not, download ATT fix, flash Saurom RC7, wipe cache and d cache, flash ATT fix and then reboot system...
Update.....yesterday i opened the cwm and just cleared the wipe cache and then rebooted the phone and everything came back to normal...error code 492 disappeared and i was able to download all my apps.. I hope it will help somebody. Running saurom rc7. Everything looks fine so far....only data speed needs to go up some more but it could be the area....
Sent from my SGH-I717R using XDA
omniphil said:
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
Click to expand...
Click to collapse
What is the problem with the kernel that you need to flash the kernel fix? Is that only if you use holo kernel?
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
So my com.andoird.phone has been crashing constantly which means I can't even do anything without the stupid popup coming up. I believe it's due to a faulty application. Anybody had any luck on fixing this? (running CM10 test build on my Evo 4g LTE)
Secondary question. Is it possible to remove the app from fastboot USB or recovery? If that were possible I think the system would sort itself back out. Thanks in advance
First, which build are you running? There have been like an average of 3 builds a day since Sunday.
Second, they have seen progressive improvements on each build.
I suggest getting the latest build from IRC if what you are running is a day or so old.
Also there are a lot of great people in there to help if you stick around.
sent from my LTEvo
elitelimfish said:
So my com.andoird.phone has been crashing constantly which means I can't even do anything without the stupid popup coming up. I believe it's due to a faulty application. Anybody had any luck on fixing this? (running CM10 test build on my Evo 4g LTE)
Secondary question. Is it possible to remove the app from fastboot USB or recovery? If that were possible I think the system would sort itself back out. Thanks in advance
Click to expand...
Click to collapse
Did you get this sorted out? I had the same problem of speradic fcing on that from the latest buil at 8pm last night. I wiped everything and reinstalled. It fc'd continuously until I got through the setup with my turbo fingers.
Everyone will tell you the same thing. The builds are on IRC and so are the bugs. Deck has not made a fix for this bug. It is a known issue. Get on IRC and off XDA for these builds.
AsinX said:
Everyone will tell you the same thing. The builds are on IRC and so are the bugs. Deck has not made a fix for this bug. It is a known issue. Get on IRC and off XDA for these builds.
Click to expand...
Click to collapse
I can talk wherever I please thank you...get off xda and go back to irc
Sent from my EVO using Tapatalk 2
ditto
I had a variation on this same issue. Did a TB of my user apps and system settings (not system apps) from my flex 1.75 install. Full wipe, installed the latest 8/2 CM10 from IRC, phone started fine, got one com.phone crash dialog and then everything seemed to be fine. Did the TB restore and when I rebooted I was stuck in an endless com.phone and android.process.acore crash loop. Only clue I have is that I noticed my wifi was connected when I rebooted (since my settings were restored).
Flashed to venom :-/
I'm on latest radios/firmware, s-off etc, latest TWRP, matching md5s etc
ristrettodreams said:
I had a variation on this same issue. Did a TB of my user apps and system settings (not system apps) from my flex 1.75 install. Full wipe, installed the latest 8/2 CM10 from IRC, phone started fine, got one com.phone crash dialog and then everything seemed to be fine. Did the TB restore and when I rebooted I was stuck in an endless com.phone and android.process.acore crash loop. Only clue I have is that I noticed my wifi was connected when I rebooted (since my settings were restored).
Flashed to venom :-/
I'm on latest radios/firmware, s-off etc, latest TWRP, matching md5s etc
Click to expand...
Click to collapse
Yeah i didn't have the issue except on reboot until I rebooted this morning then it went psycho. Its a pretty solid build otherwise.
Sent from my EVO using Tapatalk 2
ristrettodreams said:
I had a variation on this same issue. Did a TB of my user apps and system settings (not system apps) from my flex 1.75 install. Full wipe, installed the latest 8/2 CM10 from IRC, phone started fine, got one com.phone crash dialog and then everything seemed to be fine. Did the TB restore and when I rebooted I was stuck in an endless com.phone and android.process.acore crash loop. Only clue I have is that I noticed my wifi was connected when I rebooted (since my settings were restored).
Flashed to venom :-/
I'm on latest radios/firmware, s-off etc, latest TWRP, matching md5s etc
Click to expand...
Click to collapse
Pretty sure restoring system settings fro sense to aosp is a bad idea. It made it so you could not connect to data and that's why you had the error loop. just saying
sent from my LTEvo
Yep, user error
Rxpert said:
Yep, user error
Click to expand...
Click to collapse
I retried full wiping/flashing just restoring user apps, and while it didn't immediately go into the loop the same way, it still did it if my wifi was on and associated when I rebooted. It's apparently something to do with not getting data making the process go nuts.
ristrettodreams said:
I retried full wiping/flashing just restoring user apps, and while it didn't immediately go into the loop the same way, it still did it if my wifi was on and associated when I rebooted. It's apparently something to do with not getting data making the process go nuts.
Click to expand...
Click to collapse
Are you having the problem before restoring user apps? Sometimes I have found it best to re-install via market using appbak. Then once the apps are re-installed that way, just restore only the app data you need from TB, don't restore all apps/data at once.
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?