couldnt connect to wifi - AT&T HTC One (M8)

my at&t variant of htc m8 doesnt connect to wifi.
i bought it from a friend.
it searches and scans the wifi networks but doesnt connect to it and it seems the range is low too coz i have another m8 and it catches 3 bars in the room while this one catces only 1.
mobile data wasnt working before as well. i installed new viper rom and the data started working without any effort but wifi is the same. i couldnt connect.
this problem was before i even flashed a custom rom.

All I can think, is RUU back to stock (or update, as the case may be) and see if the issue persists.

okay ill try..

can someone plz guide me? link to a thread? where i can find ruu?
also, i have now bootloader unlocked and custom softwre.. can i still flash ruu?

can someone plz guide me?
i m now on custom rom with s-off and bootloader unlocked
i have a backup of stock at&t stock rom (wifi wasnt working ....nor mobile data) which i had backed up before flashing custom rom (after which mobile data started working but wifi problem still persists)... soo after restoring the stock rom how should i update it? and of course i couldnt update via phone coz wifi wasnt working... so if i find a stock update flashable file on xda should i flash it straight away? what about the radios? and should i relock the bootlaodeR?

dragonflame8712 said:
can someone plz guide me?
i m now on custom rom with s-off and bootloader unlocked
i have a backup of stock at&t stock rom (wifi wasnt working ....nor mobile data) which i had backed up before flashing custom rom (after which mobile data started working but wifi problem still persists)... soo after restoring the stock rom how should i update it? and of course i couldnt update via phone coz wifi wasnt working... so if i find a stock update flashable file on xda should i flash it straight away? what about the radios? and should i relock the bootlaodeR?
Click to expand...
Click to collapse
That's a lot of questions, most of which aren't relevant to my previous recommendation (RUU - which is not the same as a stock ROM backup).
You can find links (and more info on RUU) to AT&T RUUs on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Latest RUU for AT&T is 4.28.502.2, and you fill find the download and instructions on how to run it near the bottom of the HTC support page linked for RUU 4.28.502.2 on the Index.
You'll need to relock the bootloader in order to RUU with the command: fastboot oem lock
RUU 4.28.502.2 will return you to a full stock image, and the latest official software available for the AT&T M8. Hopefully, this will help your WiFi issue as well.

Make sure you don't have any apps installed that would mess with it. I had one app that no matter how many times I tried to turn off my wifi it kept. It back on

Related

Radio Guide for HTC Amaze

Hey y'all. There should be two radios now. The T-Mobile and the Tellus. Wind should have another radio altogether. Could the powers that be please pull radio.img files and start up a quick guide on how to unlock the boot loader and flash radios. I am happy to contribute, but I'm new to HTC. I am running a T mobile phone on a Canadian network - I assume that a radio designed for here would work better (wrong or right).
My Baseband is 1.07.550L.04DC_20.64.550L.07D
Thanks.
Correct me if I'm wrong, but don't you have to have s-off to be able to flash a radio?
I flashed radios on my 3g slide and didn't have s - off
correct me if im wrong but if its an official radio, ex- signed update - s-off is there to check if its got official signature, it should be allowed to flash
I don't know much about HTC. I owned a nexus S and flashed a few radios with fastboot and adb. It helped alot through the search bug issue.
I see this full roms availble now
http://forum.xda-developers.com/showthread.php?t=1335703
The question is what will happen if I flash another providers ROM on top of my fully stock T-Mobile. The guide suggests that you just copy it onto an SD card on a fully locked phone and Voila. There doesn't seem to be an indication of someone switching ROM's ie. Tmobile to Wind. There are a few that tried the Telus Rom but no indication that it's worked for anyone yet.
FSean said:
I don't know much about HTC. I owned a nexus S and flashed a few radios with fastboot and adb. It helped alot through the search bug issue.
I see this full roms availble now
http://forum.xda-developers.com/showthread.php?t=1335703
The question is what will happen if I flash another providers ROM on top of my fully stock T-Mobile. The guide suggests that you just copy it onto an SD card on a fully locked phone and Voila. There doesn't seem to be an indication of someone switching ROM's ie. Tmobile to Wind. There are a few that tried the Telus Rom but no indication that it's worked for anyone yet.
Click to expand...
Click to collapse
I'm pretty sure you have to have SuperCID to flash another carrier's ROM, and you can't get that without full radio S-Off. The current HTC unlock method doesn't allow us to flash radio images, as well as other little things like splash screens. Until full S-Off is achieved, I don't think we'll be able to do any radio switching.
So would a carrier be able flash their ROM onto a phone - ie. walk into my provider and have them flash their software and CID information onto the phone - or better yet - could HTC theoretically change my CID information directly?

[Q] How to get Stock Rom back ???

Hey Guys I've bought a HTC one x+ in Germany which I rooted time ago. Now I just want to unroot my device to get the original HTC Sense 5 Android 4.2.2 update. My problem is I dont have a any backups nor find any RUU with the following CID version: 1.17.206.1
My HBOOT Version is 1.35 , I also tried some RUU's which was canceled during the update progress since I did not have the right CID version needed.
However I'm going crazy and loosing my hope, please help me how to install the original HTC Rom.:crying::crying:
Thanks
jackson7000 said:
Hey Guys I've bought a HTC one x+ in Germany which I rooted time ago. Now I just want to unroot my device to get the original HTC Sense 5 Android 4.2.2 update. My problem is I dont have a any backups nor find any RUU with the following CID version: 1.17.206.1
My HBOOT Version is 1.35 , I also tried some RUU's which was canceled during the update progress since I did not have the right CID version needed.
However I'm going crazy and loosing my hope, please help me how to install the original HTC Rom.:crying::crying:
Thanks
Click to expand...
Click to collapse
seems like you have a phone with o2 cid, so your out of luck, there's no ruu that worsk with that version.
but there's a german forum i recently found, where you can find stock backups (including boot.img) and stock recoveries.
http://www.android-hilfe.de/root-cu...04-one-x-plus-ruu-s-fuer-htc-o2-vodafone.html
just put the backup into the right folder on your phone, make sure CWM/TWRP recognizes this backup, then flash stock boot.img in fastboot, restore stock backup in your recovery, flash stock recovery in fastboot and finally relock bootloader.
then your phone should be back to stock software.
thank you so far. another problem is I somewhere I have to delete Superuser and relock my bootloader to flash the stock rom. Thats why I deleted Superuser and locked my bootloader again. My question is now can I still flash to stock rom or do I have unlock bootloader again ?
jackson7000 said:
thank you so far. another problem is I somewhere I have to delete Superuser and relock my bootloader to flash the stock rom. Thats why I deleted Superuser and locked my bootloader again. My question is now can I still flash to stock rom or do I have unlock bootloader again ?
Click to expand...
Click to collapse
you probably need to unlock your phone again.
as soon as you restored the stock backup, everything you had on your phone except internal storage will be replaced by stock software, all settings will be reset, all userdata will be wiped!!!
so better backup/copy everything you need to your computer before you restore that backup.

[Q] help wih stock backup pre-root

I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app

[Q] RUU Failed

I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.

[Q] Help!! Wifi Issues after installing Viper on AT&T HTC M8

This are all steps that I have tried and nothing works:
1. Install twrp 2.7.0.2 succesfully, then viper. (no wifi)
2. flash ruu for att, install twrp 2.7.0.2 succesfully, the viper. (no wifi)
3. flash ruu for att, install twrp 2.8.6.0, twrp recovery won't load, stuck on screen
I've read in some threads that wifi issues are because of old firmware, but I installed latest rue and didn't solve anything, and for some reason twrp 2.6.8.0 which says is for all carriers won't work in my phone. Also tried installing ARHD rom and it doesn't work either. Is there any file I need to flash for wifi to work or what are the specific steps I need to follow for it to work correctly. I did this in another HTC M8 for Sprint and had no issues at all. I appreciate your help.
*** I managed to flash 4.4.2 custom kitkat rom. Wifi works in this one. How do I go from this one to Viper M8 without messing the wifi up? In the page it says to upgrade to 5.0.1 before but how do I even do that? Not sure what I'm supposed to flash before installing Viper or where to find it. Do I also need to update TWRP before? Thanks.
Did you try the Viper thread?
Haven't found detailed instructions yet. I managed to flash a stock rom for 4.4.2 for at&t. But when I searched on the phone for an ota update to 5.0.1 it didn't find any. Then I flashed viper again but wifi didn't work. I guess I have to install stock 4.4.2 again, the install a stock update to 5.0.1 and then flash viper. I'll try this option later to see if it finally works. Have been working on this for the past 3 days.
What RUU did you run?
Did you relock the bootloader to run the RUU (required since you are s-on)?
Your hboot indicates you are still on 4.4.2 firmware, which is why WiFi is broken on 5.0 (Lollipop) ROMs. You either ran the wrong RUU, or the RUU failed to install due to unlocked bootloader.
Easiest way to update the firmware is to relock the bootloader and run the AT&T Lollipop RUU.
I downloaded ann RUU zip file for version 4.4.2 and just placed it in sdcard and asked for uptade automaticaly. I don't have the AT&T sim card, which I guess is the reason why I press software update and it says that the phone is up to date. The two ruu I found for lollipop, one says european version and the other is .exe which won't work on a mac. I really don't know if a lollipop ruu zip file of the US version even exists or if installing the European version is the same thing or if my only option is OTA update with a sim card
Finally got it to work. Long process but I'll explain what I did for anyone with the same problem. Thanks for the help everyone.
* I downloaded RUU.exe from one of the threads
* Used parallels on mac ( download free trial of software and windows 7)
* First enabled show hidden files on windows
* went to C> users> (USERNAME)> APP DATA> LOCAL > temp> (open folder just created, one with a really long list of letters)> copy rom.zip from there to mac 1.6gb file
*rename to OP6bimg.zip
* copy to sd card root
* open bootloader > hboot
* it should automatically ask to complete update, just press volume up button and it should work just fine
* now you should be in stock lollipop.
(I havrn't rooted yet, but I guess now I won't have any wifi issues when flashing custom rom)
dannygarced said:
I downloaded ann RUU zip file for version 4.4.2 and just placed it in sdcard and asked for uptade automaticaly.
Click to expand...
Click to collapse
That means you are on 4.4.2 firmware. So you if you try to run any more recent version based ROMs (4.4.3, 4.4.4, 5.0, etc.) you will have broken WiFi. You need to run the 5.0 RUU to fix this.
dannygarced said:
I don't have the AT&T sim card, which I guess is the reason why I press software update and it says that the phone is up to date. d
Click to expand...
Click to collapse
That is correct. AT&T is unique compared to most other versions of the M8 in that you need to be connected to AT&T's network to get the OTA updates.
dannygarced said:
I really don't know if a lollipop ruu zip file of the US version even exists or if installing the European version is the same thing
Click to expand...
Click to collapse
Running the Euro RUU zip is definitely not the same thing as the AT&T RUU. The RUU checks the CID and MID of the phone. Since the CID and MID on the phone will not match what the RUU is looking for, the RUU will fail.
I haven't seen a Lollipop zip version of the RUU for AT&T.

Categories

Resources