Wireless stopped working - Droid Incredible Q&A, Help & Troubleshooting

A couple of months ago I decided I was going to enable wireless N on my Dinc. I've been rooted for a while and I followed the directions on a Youtube (by mejdam) video I found and failed miserably. Since then I have been unable to turn on the wireless and only get Error when attempting to turn on the wireless. If I restore the phone back to factory with latest updates it works fine. Once I put my nandroid backup back though I get the same error.
Please help!!

Sounds like you hosed the rom you were running. Try reflashing that rom from scratch and see if it happens.
Sent from HTC Incredible

well.. if a different rom works, and your nandroid doesn't, you probably screwed something up when you were running that rom and made a backup, or your nandroid got corrupted. reflash the same rom, or flash a different one.

Related

[Q] 3G Not Working after Downgrade?

Hey all, long time lurker, first time poster....unfortunately....
So after sitting on MIUI for a good while, and having a blast with it, I decided to try out some other ROMs. I was interested in seeing Cyanogen 6, and so I went about attempting to get the latest stable, non RC ROM onto my EVO. I read into it seeing that I needed to downgrade my hboot, and found the image without a problem (running the .76 right now, had the 9something one before...)
Well, I downgraded my hboot without an issue, flashed the Cyanogen, and got into a splashloop. I figured out it was becaue I hadn't wiped my cache or data before flashing the rom, so I went into the Clockwork Recovery and wiped those, flashed once more, and it booted into Cyanogen perfectly!
Well, almost. I don't have 3G now.
For some reason, I am unable to connect to 3G no matter what I try. My nandroid's broke due to the hboot downgrading, rewiping the cache/data and reflashing cyanogen did nothing, and now for some reason, when I attempt to go back to MIUI, it still will not allow me to connect to 3G. I can send and receive texts, and make and receive calls, but alas, no data connection.
Should I get a fresh RUU and stock hboot, upgrade and restart from scratch? I just want to get back to MIUI at this point with a working, data enabled phone.....
If that's the case, that I do need to start over, where can I find a new hboot for the EVO that isn't .76? I'm pretty saavy when it comes to this stuff, but for some reason right now I just can't figure it out....
HTC EVO running MIUI v0.11 stable
.76 hboot w/ Clockwork recovery
Broken nand backup
whatdo?
Thanks in advance for the help
Sorry for the double post, but I resolved my issue.
I am unsure of what exactly went wrong, but I figured it was somewhere between downgrading my hboot, and flashing the CM 6 stable ROM that my 3G data got scrambled....
So! Using ROM Manager, I made a backup of my working (non 3G) MIUI image, and flashed the Odyxed version of the RUU found here (http://forum.xda-developers.com/showthread.php?t=836728). After flashing in Recovery, it booted into SenseUI, and worked like a charm!
My 3G hath returned, and issues have been solved. It's nice when you're able to fix things on your own, though I couldn't have done it without the help of that handy dandy search button, and the RUU keyword
Oh, yeah, and I guess xxbabiboi228xx as well.....maybe....^_~

[Q] I am absolutely stumped, please help

Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though

[Q] Broken Wifi

I recently unrooted my EVO to exchange for credit for an upgrade. I decided to keep it as a backup. I was on Hboot 2.18.001 and I rerooted through HTCDev, then PC36IMG to 2.2 to get S-OFF, ending up with Hboot 2.10.001. Somewhere during this rooting process I lost Wifi. When attempting to turn Wifi on, it flickers off and on and reports back that it is unable to scan for networks. In CM7, it causes more problems like force quits and lag. I am using this as a wifi only device as a backup music and game device.
I tried downgrading and upgrading the radios, I tried changing to hboot 2.15.001, I tried different ROMs (AOSP, ICS, Sense, 2.2, 2.3), I tried redoing a PC36IMG, I tried combinations of all of the above. I also tried nandroid restore. Still no Wifi. I am using Smelkusmod recovery.
Currently I am at a stock latest OTA ROM with root.
Any suggestions?
just wondering, did u ever drop it? thats what happened to my evo shift and i couldnt do anything on it other than install roms. i dont remember the version of the firmware but there was one that made wifi useless, meaning like it would turn on and find signals but wouldnt connect. my suggestion is to start from scratch, get the 2.2 ruu stock, before rerooting check to make sure wifi works, if it does then another suggestion would be to follow zedomax's rooting with revolutionary (witch i currently have now). if none of that works then eather sell it for parts or take it to sprint to get a refurbished one.
Good luck!

[Q] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

[Q] Moble data works with stock rom, but not custom

I'm having a lot of trouble with my S2 right now. I've been running CM10 since I got it with no trouble at all. I updated to 11 when it came out, again with no problems. Basically what happened is I flashed the stock ROM so I could use the video camera, then just restored back to CM through recovery when I was done. I did that two or three times, then suddenly I have no mobile data on any custom ROM, OR on the stock ROM I made a backup for. Voice and text works fine, just no data, either 3G or 4G.
I eventually un-rooted and went completely back to stock, and that got data working. I rooted and got recovery installed, and everything's still working fine. But, no matter if I try to install Cyanogen fresh, or try to restore a backup, I don't get mobile data. If I restore a backup of the last stock ROM, data works fine. From inside the stock rom, I did a master reset and updated PRL and profile.
Does anyone have a clue as to what I'm doing wrong?
Okay, I noticed that my MEID and some other parameters were 'unknown', which according to Google can mean a bad modem. So I flashed a new one, and all is well.

Categories

Resources