Hey there everyone, so since i flashed the CM10 nightly from the 24th, wifi has been nearly completely broken for me. You may have seen my posts where i described how my phone barely ever manages to load anything over wifi and when it does, it does so intermittently and at an extremely slow pace. This renders wifi pretty much useless on my phone. Mobile data IS working though.
Now, i first thought it might just be an issue with the nightly i was using, but this issue persisted on the nightlies from the 25th and 26th of this month (which i did full wipes between). So then, since i wanted to stay with Jelly Bean, i decided to try out Tgascoignes AOSP Jelly Bean (another full wipe here), but then this same issue was there as well. Then, i figured i'd try the first Jelly Bean CM10 nightly, since everything was working great on that one, but then this issue with wifi was still there.
So then i thought it must be an issue with Jelly Bean, so i went back to the most trustworthy and stable ROM i have used so far - One Maximus V2.1 with ICS. Then, this issue still persisted.
So, the tl;dr version of this is, wifi isn't working on any ROM for me and i can't seem to do anything to fix it and i really need some help with this. Do you guys think it might be a hardware issue? My router has been working perfectly for other wireless devices in my house. What plan of action would you recommend? Any help will be very very highly appreciated.
Also, the reason that i'm posting this as a new thread is because this isn't the same wifi antenna problem that has been documented a lot in the other thread. My wifi reception doesn't improve or vary depending on where i press on my phone and that's not the issue at all. If this post still doesn't deserve it's own thread then mods, please remove it and i will ask for help elsewhere.
The most complete restore would be to fastboot oem lock and.run the RUU for your device.
If that doesn't fix it, I don't know what will and neither will HTC I suspect, they'll likely replace the motherboard.
BenPope said:
The most complete restore would be to fastboot oem lock and.run the RUU for your device.
If that doesn't fix it, I don't know what will and neither will HTC I suspect, they'll likely replace the motherboard.
Click to expand...
Click to collapse
Well, i fully restored my phone back to stock and the issue is still persisting . Mobile data is also being really weird now even though i have set the correct APNs.
I also can't update my phone from the 1.29 firmware to the 2.17 base firmware because my carrier (Virgin) hasn't bothered to put any effort towards pushing out an update.
I think i will have to claim the warranty for my phone through Virgin and hope that they don't notice that it has been re-locked as other people have had such luck too.
Does anyone else have any other ideas about this?
I had a similar problem with my sensation after flashing some custom ( & official roms not meant for my region). Try WIFIX, somewhere in the forums. This could be a WiFi radio region code problem
magic_android said:
Well, i fully restored my phone back to stock and the issue is still persisting . Mobile data is also being really weird now even though i have set the correct APNs.
I also can't update my phone from the 1.29 firmware to the 2.17 base firmware because my carrier (Virgin) hasn't bothered to put any effort towards pushing out an update.
I think i will have to claim the warranty for my phone through Virgin and hope that they don't notice that it has been re-locked as other people have had such luck too.
Does anyone else have any other ideas about this?
Click to expand...
Click to collapse
just do it through virgin - in uk its the retailers responsibility to repair, replace or refund it if they can't prove that the fault was caused by you unlocking it etc.. (if before 6 months after purchase)
I don't know how this has happened now but I had a feeling that there was something wrong with the WiFi antenna of my phone, so I squeezed it really tight at the top left corner where the WiFi antenna is located (as seen in the WiFi faults thread) and now all of the issues mentioned above have been fixed . I have no idea if it was just pure luck and coincidence but now my phone is working normally again. If it wasn't a coincidence, then I really hope that this issue doesn't come up again.
I feel very lucky either way right now! No more need to worry about warranty issues and such . Thanks anyway to you guys for replying though, it's good that this forum chips in to help out those that are in need of help!
Dammit i have no idea what is wrong with my phone. Wifi and mobile data were working fine for a day and a half on the stock ROM, so then i decided to re-root and flash some custom ROMs again and this annoying wifi issue is back now :S. Why would this even happen? I am honestly at such a loss with this. Does anyone have any ideas about what's going on?
Related
I have just spent an absolute age with HTC tech support, and the answer to the few that have been suffering with no data via wifi is................send your handset in for repair.
I honestly have completely lost the will to live, no matter what i say to try and convince them the issue is software related as i can use 2.2.1 absolutely fine, it seems to completely be over everyones head, i even spoke to a manager, who after listening to everything i said, who then spent 3 minutes in silence came back with "broken wifi module"
Arghh, they now want to book my handset in for repair, which i am reluctant to do as they quote a turn around of 20 days currently, i dont want to be without a handset that long.
all i want is gingerbread on my handset and be able to use WiFi, 3G works perfectly
Has anyone had any luck in solving this? its not a router issue, i have tried 4 different routers, its not a signal issue (i have a full signal, and its not dropping the signal), i have tried every 2.3.3 custom rom and stock rom out there and still no data Via WiFi, tried different radio's, and different kernels,
If i go back to using the Android revolution 2.3.2 beta, it works fine, so its defo since the 2.3.3 update.
any help from anyone would be so gratefully recieved i will buy you a pint!
Hi there,
Have you flashed the matching RIL's for your radios? A similar issue affected me but it was only with CM7 and ARHD. I flashed the radio in my signature (good WiFi performance for signal and battery life) and the corresponding RIL and all was working after a couple of reboots.
Hope this helps.
i have indeed pal, really really struggling with this.
A work colleague has just completed his OTA update at work, same issue,
at least i know its not just mine
im wondering if its something to do with the wifi driver in the ota,
Actually its not just the ota, tried the RUU just now, same issue
any Dev's got any clues?
Mate,
I´ve downgraded the ROM as per this thread (http://forum.xda-developers.com/showthread.php?t=905003), and now it is working perfectly. No need of gingerbread, I noticed that I do not need it anyway. Instead of that, my baby is alive and kicking againg.
Cheers.
hmoroni said:
Mate,
I´ve downgraded the ROM as per this thread (http://forum.xda-developers.com/showthread.php?t=905003), and now it is working perfectly. No need of gingerbread, I noticed that I do not need it anyway. Instead of that, my baby is alive and kicking againg.
Cheers.
Click to expand...
Click to collapse
im back on LeeDroid 2.2.1 custom rom and everything works like a charm, there isnt anything on gingerbread i need, but i want the option, i prefare the menu, but i can not be without WiFi. I have just sent HTC a humerous letter/email, i have spent hours on the phone with them today.
Sent LeeDroid a pm, see if he has any idea why this is, or if there is anyway to sort it
hopefully someone soon can come up with something, there are only a few of us with the problems, but even so HTC should release a patch or something to rectify it. A guy who has a T-Mobile branded device at work has updated fine, but myself and another colleague (both unlocked sim free devices from the carphonewarehouse) have the no data issue via wifi
i am losing the will to live
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
shadowspires said:
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
Click to expand...
Click to collapse
So you just took apart and reassembled and that got it working?
Maybe
xvanwilderx said:
So you just took apart and reassembled and that got it working?
Click to expand...
Click to collapse
Tried to sell phone on ebay because the wifi adapter was showing issues with range... I bought another and it was clear that the range of the older phone was having issues...
Tried to sell on ebay and buyer couldn't activate... just sent back and I can't get it to accept a flash at all... maybe trying the taking apart trick again...
Crazy
Hello xda,
Firstly I wanted to say thank you all for existing, Ive had much fun customising my HTC Desire and now my One X because of your articles. Even using google, all roads led to XDA.
Now to the problem...
Yesterday the official Jelly bean update for my One X, and since then Ive had a bunch of Wifi problems:
As soon as I connect to Wifi, I get about 10 seconds of internet, then nothing will connect until I turn Wifi off/on again, when this repeats, of course. This happens on both the 2.4ghz and 5ghz networks at my home.
If I use a network that have other users on it, it will disconnect for everyone.
The Wifi works on my phone properly when I change the router to 802.11b mode, but signal strength is poor.
I cleared the cache in recovery and when that didnt work I performed a factory rest, also didnt solve the problem.
I have read up about the problem and tried all solutions but I was thinking about going back to having my phone unlocked and rooted etc as this was what I had originally until I relocked it to get the official update (which has come back to bite me in the butt)
I guess this biggest question would be: Would getting a custom ROM fix this problem? Im asking this instead of going ahead with it like I normally do because I dont really want to make it worse if I can help it.
If anyone else knows enough about this problem, or the cause of it, that would be swell. Is it because of the fact that its been relocked/unrooted? Others who have stock standard phones have had the same problem but I want to be sure.
Some info:
HTC One X - unbranded CID HTC_023
Software #: 3.17.728.1
Android: 4.1.1
Stock Kernal
Stock Recovery
S-ON
HBOOT: 1.39.0000
Relocked Bootloader
Network 2Degrees New Zealand
WIFI Router:
TP-LINK TL-WDR3600
ISP: Telstraclear NZ
Its probably not super brief, but I want to make sure I have everything you need.
Thanks!
This sounds like the problem that existed on early JB hboots prior to 1.36, if I recall. Don't know why you have the problem, it's very odd.
My advice : make a nandroid of the stock rom and flash a different rom ! The bootloader has already been unlocked so the state of warranty will not change if unlock it again. Worth the try ..... going back to the reseller is always an option after this !
I don't have this problem and i've updated to JB for some time now.I am not an expert on anything,but a friend of mine had similar problems with the wifi that you have,except that his wifi would randomly turn off and on from time to time in addition to your problems.After going to the HTC repair center they replaced his Wifi antena because it was faulty,and after that he didn't had any problems.The strangest thing is that he was using a custom rom(ARHD if i recall right) and HTC accepted to repair his phone,that simply amazed me because i tought that once you unlock your bootloader and install a custom rom,you're guarantee will be voided.Anyway,sorry for the long post and stories,but you can call or sent an email to HTC regarding this issue,you might have a faulty antena.
Yeah I thought it might be the faulty antennae halabaloo that people talked about for most One X phones, but the Wifi was fine before the JB update and I haven't dropped it around the same time (though almost threw it at the wall)
Also it looks like Ill have to wait a bit for a custom rom, as the stock kernal is the only one that plays nice with the new HBOOT. Touchscreen is not working in rom or recovery.
A bunch of other people with HTC_023 had this same problem.
I'm on _023 and Touch does not work with CWM (not really that big a deal), but works fine with the stock ROM. No issues with wifi, just an odd issue with the voice->text that seems to affect only my phone. Do yourself a favour and make a nandroid backup and store it on your computer so you don't have to poke around for one later.
I'm also on HTC__023 with JB update and have found since the update that it dosen't like 5ghz wifi yet 2.4ghz is fine
I am on the same ota and my wifi does not work at all. Hopefully HTC figures this out. This is my 2nd HOX the first one had the bad antenna.
don't let the cat lick the butter
Ok I think I fixed it, if youve got wifi problems on a 5ghz network, youll have to change the mode to 802.11a and channel to 36 on the router (at least, thats what I did) and it works again!
If I use a network that have other users on it, it will disconnect for everyone.
Click to expand...
Click to collapse
Isn't it an AP problem? With the new wireless module in JB the phone WiFi may talk a bit differently to the AP. I would suggest to check with different APs and to upgrade router/AP firmware.
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
DarkBlaidd said:
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
Click to expand...
Click to collapse
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
I will likely switch back as I have a new hands free stereo for my car that I would like to legally take advantage of
let us know if you run into issues you will need to do a few searches.
sbiricuda said:
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
Click to expand...
Click to collapse
I'm a poor boy, so I am probably going to try and save a few bucks by using this method, which requires root.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
Click to expand...
Click to collapse
What was the GPS issue? Can you link to the fix please?
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
Click to expand...
Click to collapse
Cool, thanks for giving your opinion. How good is your battery life?
yohan4ws said:
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
Click to expand...
Click to collapse
Sounds like a good idea, I will do that.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
Click to expand...
Click to collapse
Noted, I will stay away from fastgsm. I think I am going to do this or GalaxSim Unlock.
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
Click to expand...
Click to collapse
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out. There is also a chance that Samsung will update us to Jellybean, they just released an update for the Galaxy S2, so it's possible.
let us know if you run into issues you will need to do a few searches.
Click to expand...
Click to collapse
Thanks! I believe I have done enough research to do what I want, so hopefully I won't make any dumb mistakes.
DarkBlaidd said:
Update from 2.3.6 to 4.0.4
Click to expand...
Click to collapse
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
Click to expand...
Click to collapse
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
DarkBlaidd said:
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out.
Click to expand...
Click to collapse
I'm in same boat here I guess. Just ordered a Glide, looking forward to having a physical keyboard again since my TP2 days. I was checking out the ROM options, found the link for "Stock UCLJ3 Rom" and it looks like that is the way go, other than maybe just staying stock... I need Bluetooth, Camera, GPS, and Tethering to work, so I guess I won't be messing around with anything fancy.
So don't do any OTA upgrade at all when I first get it out of the box? Just back it up, then root, and install UCLJ3 via CWM? Is this the best choice?
roothorick said:
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Click to expand...
Click to collapse
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
idenlover said:
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
Click to expand...
Click to collapse
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
roothorick said:
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
Click to expand...
Click to collapse
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
idenlover said:
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
Click to expand...
Click to collapse
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
roothorick said:
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
Click to expand...
Click to collapse
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
idenlover said:
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
Click to expand...
Click to collapse
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
roothorick said:
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
Click to expand...
Click to collapse
Awesome, thanks for the help!:good:
roothorick said:
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
Click to expand...
Click to collapse
Damn it, that really sucks. Thank you so much for letting me know that, you saved me some headaches.
Edit: I did some digging around to get a technical explanation of this issue and stumbled across some unexpectedly good news, I can use HSPA+ on T-MO, well halfway at least, I'm going to make a new post as a public service.
Look i normally dont ask for to much help ive been around a bit know more then the average bear. I also fix hardware.
My problem is my data radio will not switch on from any attempt:
Attempted solutions:
Dialed
*#*#4636#*#*
Will not switch on from that screen
Did the obvious and switched on and off airplane mode
Replaced the entire build.prop file with a very stock build.prop after flashing stock jelly bean
Repeated steps for all stock firmware
Newest attempt wiped the entire system partition through recovery forcefully bricking the phone. I have now flashed the original stock e980 stock 10p tot file still no luck
My phone is completely unlocked fully rooted.
I've replaced the data permission files.
And I know its not the SIM card because the SIM card is in the phone I'm using right now which is an LG g2 unlocked which is for sale by the way.
And if it is a hardware problem I have not found any related video or thread to help me find an exchange where the radio is on this thing
Help me please if anybody has any idea?
Cool no help, hey moderator can u move this to thread that may get more help that would be awesome
i came looking around here because my g pros radio stopped working sometime last night while i was asleep and was about to make a thread asking for help, but seeing as how you haven't got much i doubt i would either. but ill give you a little info on mine, will it help you out at all? not sure. but i know it might make me feel a little better.
I flashed Vanir 4.4.4 last week coming from Beanstalk 4.4.4 cause beanstalk was getting buggy from all the ugly mods i subjected it to. so all was well with Vanir till i woke up this morning and had no service, no calls, no network, AND even if i connected to a wifi network it seemed that i couldn't get any data from it. I tried flashing madmacks modem cause who knows, maybe thatll help, but it diddnt. So then i flashed a different kernel and changed TCP protocols cause who ****ing knows, but it did nothing. THEN i restored my older Beanstalk 4.4.4 backup sure that it would work flawlessly but guess what, same problem. Now that im back on Beanstalk i went to the "Network Operators" option under "Mobile network settings" and selected ATT, which is my service provider, i can now make calls and texts but still no data, when i did this on Vanir it did not help. So i started messing with my "preferred network type" and realized i have data on 2G, but not 3G or LTE. Im gonna take a wild guess and say that maybe if you flash your phone back to 100% stock your radio should start working again, as much as i dont want to, i might end up doing that as well.
tl:dr
similar problem, i dont really know ****, easiest option = go back to stock, hope it works.
@Fant0m3 @alb-o
Have you guys checked if your rom shows your imei?
I have had this problem twice. My IMEI disappeared and I don't know how.
Your symptoms match.
If that's the case you could take it to a repair shop and they'll fix it in a minute or two. Or, you can check around xda.
thats a good point, when i was looking around XDA earlier i saw a few mentions of it but diddnt see anything very specific and was late for class so diddnt have time to look for too long. strangely enough mine actually started working normally again after i kept switching from 2G to 3G to LTE, which is great. but if i would've known that info earlier i could have checked if my IMEI disappeared while my radio still wasn't working, i assume it probably did.
after searching around more i found this thread that talks about it and how to prevent it:
http://forum.xda-developers.com/showthread.php?t=1857054
thanks for the help g0at1, hopefully this helps out the OP if he hasn't already fixed the problem, or anyone else that comes across this.
nope
I've flashed back stock numerous times even flashed other versions such as e988 and back again if u dint know how to do that just change your build number in your build prop file...I've tried everything I am downt to antenna cable SIM reader or cell radio.. If radio I might as well just give up cause I can't find one for sell anywhere...I'm not so pressed as I'm using the LG g2 and it's so fast stable and a bit slimmer I think I'm gonna keep it but I would like to fix it and sell it though...... My symptoms are mentioned and all tried fixes are there. Imei is read carrier is not WiFi is received but there is an X above the data bars phone is fully unlocked as well
This may help also but it does not read my imei when the SIM is not in hmm maybe I will rework the imei code and get back if that works. I will keep updated when fixed and with solution