I have been keeping up with Jokersax's ICS roms, and every once in a while I'll flash a rom, this time it was 6.0 over 5.2, and I lose radio. It's set to CDMA auto PRL and enabled, but I get nothing. Anybody else have this issue? Only solution I've found is SBF-ing. I've tried wiping everything known to man, re-flashing multiple ROMs, fixing permissions, but can't ever get it back after it's gone without SBF-ing. Ideas???
Fixed
Found the fix. Flash this in CDMA fix in CWM from Jokersax's page. Can't post the link because forum rules are dumb.
Related
Details of my problem are here: http://code.google.com/p/atrix-dev-team/issues/detail?id=115&can=1&start=100
Samcripp asked me to open an issue, but it was later closed as its not related to CM7.
Basically after updating to 0.19 Faux kernel and OCing, my bluetooth does not work (does not turn on) and my wifi says "error" and reboots if I try to turn it on. Logcats are attached in the link above.
Before this, I also tried the 1.35 Radio but I'm pretty sure it worked after flashing back to 1.77.30P.
I've tried everything from erasing via fastboot and clean installing stock 2.3.4, alien and CM7 -still nada. Tried restoring pds partition, nada. Tried different radios, nada. Only thing I didn't try was to SBF to stock. Can someone point me in the right direction to a SAFE SBF that I can used on an unlocked ATT Atrix?
Here is the dmesg: http://db.tt/92GSbZ4
Says something about buffer overflow, vdd.
Any help?
Sent from my MB860 using XDA App
Here is another (see bottom)
http://db.tt/3I2A7ca
Sent from my MB860 using XDA App
I got it to work momentarily but then phone froze and went back to error. I had followed these instructions: http://forum.xda-developers.com/showthread.php?t=1077329 and then did a dalvik cache wipe.
What could this be? Hardware?
Think its definitley a hardware issue. I can get the bluetooth/wifi to work by taking out the battery and tapping on the back of the phone..but then it dies later.
Next question: Any way to get "Unlocked" from showing on the bootscreen?
Had a similar issue
I once had a similar issue with my wifi after installing the same kernel. Consider restoring the stock kernel before you consider your phone broken. When you change kernels, since the kernel is central often, hardware is messed upOA component,
Have tried stock kernel, 1.83 kernel, faux kernel and kholk's kernel..all the same. Wiped cache/dalvik cache after all.
Getting replacement device from ATT. Just trying to figure out if I should send back with "Unlocked" text or not.
Theres got to be a solution, somewhere ... I can't get it replaced.
Someone...
was there a solution to this i am having the exact same problem
ive been running jokersax cm9 shortly after flashing 0.33 i noticed i no longer was hooked up to wifi. After looking into it i noticed bluetooth is also a no go.
it never gets past "turning wifi on" i have since done a complete format/factory reset, flash .33 and .4, went back to Cm7 still no change i have also flashed multiple kernels.
Last try was flashing radio N_01.77.37p still no luck
Having the same problem. Wonder if we can buy just the system board of this phone
Sent from ATRIX (CM7) using the XDA Premium App
Yes, Wifi/Bluetooth is a hardware issue! My phone just died of this same fate. If you want to take advantage of your warranty, then flash the 2.3.6 SBF after wiping all user data. BE CAUTIOUS. And can we make a big sticky for this problem? There are literally dozens of threads about this
There's another thread about rebooting, but that seems to be about a hardware issue and I don't think this is.
I got a new T-Mobile UK Atrix last week, followed the guides to unlock the bootloader and flash a custom ROM and kernel. I've tried several combinations, but they all result in me getting 3-4 random reboots throughout the day.
I've tried with Alien 4 and HomeBase 2.2, and with Faux's 0.19 and 0.20 kernels, both overclocked and at stock speeds. Even with the stock kernel, it still happens.
I've gone back to stock Froyo 2.2.1 using the Fruitcake method, and I'm no longer experiencing any problems.
Has anyone else experienced this? Is there some procedure for flashing a ROM that I'm getting wrong? What I normally do for a ROM is to wipe data and cache, then flash. For a kernel I would just wipe the cache.
If anyone else has a UK Atrix can they walk me through their procedure to get a stable Gingerbread?
There are not just one but several other threads about this, some as old as the Atrix forums. Afaik none of them offer a simple solution, because there is not one. I dont think anybody will be able to tell you, "do this and it will solve your prob". This is what will happen: you get a few "me too" posts, a few speculation posts with no real helpful information, and a few "I dont have this prob on X rom" posts, also with no helpful info. That being said, i havent had a random reboot on Alien4. Also, here is search results.
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
benny6812 said:
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
Click to expand...
Click to collapse
If it helps, i accidentally formatted the PDS partition a while back and the reason for reboot is AP KERNEL PANIC
Any help would be greatly appreciated.
I am having similar problems. Just last night my phone started rebooting frequently after having turl's v8 build of cm9 for probably a week and it was working great. However, now I have tried wiping everything, putting on different cm7 or cm9 builds and what I have come to the conclusion is anytime I turn the WiFi on, it reboots.
It is not even connecting to anything, just turning it on makes it reboot. I was on the .36 radio with this issue, I tried using the .37P radio and it did not fix it.
Does anyone have any other ideas to try and fix?
Benny,
Do you get the option to turn it on? I'm on cm9 and it'll show up like the attached after it reboots.
No. I dont have that screen. It just says wifi error and Bluetooth crashes as well....
Sent from my MB860 using XDA App
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
bassmarkie said:
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
Click to expand...
Click to collapse
But, how come whenever I flash a new rom, the WiFi will work temporarily, i.e. it would connect, obtain IP etc for a few minutes then just not work until I reflash?
Surely that is not hardware?
Bump
Sent from my MB860 using XDA App
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Drakonas said:
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Click to expand...
Click to collapse
Tried all of the above and still nothing unfortunately. Just want to update on symptoms of the phone if that helps:
Everything eventually gets more and more buggy, even recovery is really laggy and slow
Data will stop after a few days use, and only fix that i know of is to reflash
WiFi does not work, it connects for about 30 seconds after a reflash, but then nothing.
Logcat says - Failed to Load WiFi Driver (after reporting WiFi HUNG)
The phone can crash when I plug in the MicroUSB to charge, when it restarts it says AP KERNEL PANIC.
I have tried everything except for flashing via RSD lite, do you think that could work?
Thanks
BUMP,
Any help at all with this unique situation would be very helpful.
Thanks
Ever since I got a PRL update from my carrier, I have had no luck whatsoever with having data on any of the ROMs I tried flashing which include CM7 Nightlies and THS ICS. Even after following droidstyle's guide to key no luck. Anyone have any info as to just how important PRL updates are or what their connection is to my problem? Thanks.
normally the sd card is the culprit for issues with flashing cm7 & cm9 based roms... especially if your getting cant mount errors.
Would you recommend I try clearing my SD card of everything besides the ROM itself before installing? And would it somehow lead to broken data?
Could have been when your prl updated it updated something else along the way. Or just doesnt happen to work with your phone. For example i flashed a galaxy s and had to use a paygo prl as the latest i had on my phone wouldnt work for it. Its def a possibility that something with that update caused ill effects.
What exactly have you tried? Flash back to stock ? Data doesnt work still with new prl? ?
Yup...pretty much droidstyle's guide word for word as far as flashing back to stock and installing CM7 or CM9/ICS.
I looked up something that flashes through CWM called alt carrier data fix...apparently for cricket users...thought it would help for my phone...from the flashing on/off 3g it just basically went dead...so that didn't work...
***Pre warning***
Turning your phone s-off gives you a chance of bricking your phone. I am not responsible if you try these steps and have problems. Also you will loose all your data as you will be wiping your phone multiple times. Make sure to backup all your data (I used Titanium backup) OK?! :good:
I had done a ton of research trying to fix the GPS on my HTC Jewel and never found a solution that worked. Issue was the GPS would not lock. I was originally running MeanRom, then JellyBam, and finally switched to CM10.1 nightly builds, all with no GPS. Last night though I finally fixed it and wanted to post this for anyone else having this problem.
Prior to last night here is how my phone was setup:
S-On
Hboot 1.19
Radio 1.12.11.0890
CM10.1 20130224
I saw that HTC released a new update, and started digging on how to update when on a custom ROM. I realized that I needed to go s-off which I had tried last year with LazyPanda, but it failed.
Last night I was able to go S-Off following directions from FacePalm: http://forum.xda-developers.com/showthread.php?t=2163013
It was a lot easier than DirtyRacoon and I'm running Win7x64 which DirtyRacoon says is not supported by them.
Once I was s-off I downloaded the latest Radio 1.12.11.1210 from: http://themikmik.com/showthread.php?13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection
I confirmed that the radio upgraded successfully and rebooted. I was then prompted to activate my phone, and when I tried to activate it gave me the error that I was not authorized! With some help from the FacePalm IRC channel I was pointed to having to flash stock to be able to re-activate and then flash again back to your custom ROM.
I downloaded and flashed with Stock_Rooted_Deodexed_2.13.651.1 found here http://themikmik.com/showthread.php?14585-ROM-Kernel-2-13-651-1-Stock-Rooted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Booted and re-activated, and confirmed GPS working! Then I re-flashed with CM10.1 20130228 and GPS was still working!
I hope this helps others as I have seen a lot of forums with people complaining about the HTC Jewel GPS and saying it's faulty hardware, unfixable, or their fixes are all in app software related.
Thanks!
One thing that I would like to add is if you go stock, do NOT turn off your GPS after you get a lock. I usually have GPS turned off to save battery, but it was the reason why the new ROMs couldn't get a signal.
So to recap
1. Go back to stock
2. Get any old signal even for just a second
3. Immediately flash your new ROM without turning off GPS
4. Enjoy
This indeed works.
I don't like Sense-Based ROMs, so the first thing I did after getting my Jewel was S-Off, and I'm running AOKP. The GPS was driving me crazy, and I couldn't figure out how to get it working.
I updated my radio, flashed a sense-based ROM, locked GPS, then reverted back to AOKP, and it works flawlessly!
This method works!
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
The way I fixed the problem before was to flash back to sense, clear maps data and flash back to CM10.1. Voilà
I use waze
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
The only reason you have to go back to stock is to re-activate your phone.
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
pbedard said:
I use waze
Click to expand...
Click to collapse
So do I, but before I did this waze just searched for GPS signal.