I had problems (even before rooting) where my wifi would simply not work. If I go into settings and try to switch it from On to Off, it would simply say there was an "Error". Earlier in 2013, I had rooted and installed a Cyanogenmod Rom on my phone (I forget which one exactly, but it was JB). After a while, I went back to stock. A week or so later, the problem happened again. I did a factory reset. It fixed the problem for a day. Then it happened again and not even a factory reset would fix it.
I got a Nexus 5 for Christmas, so I'm looking to sell this phone but want to fix the wifi before I do so. I've seen a couple of people with a similar problem but no fixes. Does anyone know what is the cause of this problem and how to fix it?
Thanks.
Um, how did you return to stock? Ruu or a backup?
Sent from my One Xl using xda premium
If it was happening while your phone was completely stock I don't think there's anything you can do that's going to be worth it. It'll likely have to go to a repair centre and the cost would be more than you can sell the phone for. You could list the phone on Swappa, there may be people who require only the display, motherboard etc.
You could try running an RUU as a last attempt saving though.
Sent from my Evita
magnetboard said:
Um, how did you return to stock? Ruu or a backup?
Click to expand...
Click to collapse
A nandroid is only going to put you back on the stock ROM, not stock recovery, etc. You may also have s-off, unlocked bootloader, SuperCID, etc. that would make the phone "not stock", but you have given zero details for us to answer your question.
Going back to stock should only be necessary for selling the device or returning for warranty (not necessary for AT&T).
Well, a nandroid, as stated by Tim, only gibes you the stock ROM. An ruu wipes anything that might have messed with anything.
Sent from my One Xl using xda premium
I used an RUU to go back to stock.
The details for my phone are:
S-Off
CID-11111111
HBoot-2.14.0000
If there is any other information that would be helpful, let me know and I can try to provide it. I'm planning on selling it on Swappa...my hope was to fix the wifi before doing so.
If you've done an RUU and still no WiFi then you've run out of options.
Sent from my Evita
Thanks. That's what I was expecting...just wanted to make sure.
Related
My dad came home from work today and his stock Inspire 4G has stopped working. Nothing has been done to it. It simply hard locked and turned itself off. Since then I can't get it to boot past the boot loader. Once it's in the bootloader it checks for the PG98IMG.zip and then doesn't respond to anything else. I have tried numerous battery pulls, connecting to the phone with ADB and so forth but no response from the phone. Any ideas? AT&T has shipped him a refurb, but I figured I would take a crack at it until then since his phone would probably be better than some random refurb.
Sad, seems like it's boot looping: on stock rom, no less. My options will void the warranty, though, as it entails installing custom roms:
1. Push a cooked rom by rooting it. The cooked rom should be clean, but it will be rooted, thus, warranty void.
2. Try looking for stock rom for the HTC Inspire, push that using ADB and have the bootloader use it. Hopefully, it should restore stock settings to your inspire and still be replaced through warranty (i wouldn't know, I haven't sent a rooted phone in to warranty yet)
If that fails, might as well call AT&T and say it's a dud.
Truculent said:
My dad came home from work today and his stock Inspire 4G has stopped working. Nothing has been done to it. It simply hard locked and turned itself off. Since then I can't get it to boot past the boot loader. Once it's in the bootloader it checks for the PG98IMG.zip and then doesn't respond to anything else. I have tried numerous battery pulls, connecting to the phone with ADB and so forth but no response from the phone. Any ideas? AT&T has shipped him a refurb, but I figured I would take a crack at it until then since his phone would probably be better than some random refurb.
Click to expand...
Click to collapse
You could take the pd98img.zip from the ruu and it would do a clean install and more then likely boot the phone up, unless it is a hardware issue. I don't see the need to root it if all he wants is the stock rom.
Btw you can find the pd98img.zip in the guide stickied in the general section.
Sent from my Inspire 4G using XDA Premium App
Wait, how did you get into the bootloader if you dad's phone is stock?
same way you do on a rooted phone power plus volume down..I think you are confusing the bootloader with recovery.
mudknot2005 said:
same way you do on a rooted phone power plus volume down..I think you are confusing the bootloader with recovery.
Click to expand...
Click to collapse
No, I just didn't know you could do that on stock.
mudknot2005 said:
You could take the pd98img.zip from the ruu and it would do a clean install and more then likely boot the phone up, unless it is a hardware issue. I don't see the need to root it if all he wants is the stock rom.
Btw you can find the pd98img.zip in the guide stickied in the general section.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
I think I'll try this. I'm wondering if it's a hardware problem though. My dad just told me that yesterday it was losing signal and then he would reboot it and it would regain signal for a little while and drop it again. May be a radio problem.
LEAVE IT BE. There is no reason to monkey with it if you already got the refurb, just send it away. Just because you want to poke around like bill nye or something might end up costing your dad $450.
I Agree Leave it be
Sent from my Inspire 4G using XDA App
Truculent said:
I think I'll try this. I'm wondering if it's a hardware problem though. My dad just told me that yesterday it was losing signal and then he would reboot it and it would regain signal for a little while and drop it again. May be a radio problem.
Click to expand...
Click to collapse
hi, friends my problem is ike that too. I swithed on to Hboot and pushed to recovery. after that my phone can not read PD98IMG.zip, I wanna install stock rom by sd card but it can not read it. when I stand in it sd card with PD98Img, its "checking" then again staying on Hboot system. please help me how to do it?
Why not just take the stock ruu which installs from the pc?
Sent from my Inspire 4G using XDA Premium App
So I have a problem, my HOS is constantly disconnecting from the network. It'll only stay connected as long as I'm not browsing using the 4G network, on Wifi works fine, never disconnects.
At first I heard it was a problem with the TMO network and they were working on updates, so I waited; then I heard it was a problem with the HOS and the TMOB RUU version, and loading a HTC EU ROM would solve the problem; then I heard that it was a problem with the radio, but no one has a consistent method of flashing an updated radio with S-ON (some say OK to flash with Clockwork, others not so much luck, seen reports of soft bricks).
I havent seen anyone really find a solution for this problem. Seen folks say the build.prop needs to be updated (which I haven't tried), others have fixed with different ROMs, everyone has a different solution that only appears to work for them.
FWIW
HBOOT-1.09.0000
RADIO-0.16.31501S.16_2
Running TrickDroid 7.1.0
So my thought is that it's a problem with my device (I got it the first day it came out) so I assume it has to be a manufacturing defect that hopefully a warranty exchange would resolve.
I'm down for reloading stock, but as I recall the minute the bootloader is unlocked the disclaimer appeared. Anyone know how to lock the bootloader?
My other question is, has anyone done a warranty exchange or know if they care if the device is rooted since more than likely they'll just reflash it to stock and put it in the refurb stock. I've done warranty exchanges with G1, N1 and MT4G while rooted and no one seemed to care. But now that the bootloader has the disclaimer on boot, I fear I'll be on the hook for the device since it's rooted.
You can flash radio zips cuz you hboot is 1.09
Sent from my HTC One S using xda premium
randomnoob83 said:
You can flash radio zips cuz you hboot is 1.09
Click to expand...
Click to collapse
With clockwork or another method?
With TWRP. I had those disconnect issues with T-Mobile stock everything, but unlike you, I ran the RUU, so yes I got an update HBOOT but those issues are gone.
T-MobileUS HTC One S running Stock Rooted 2.21.
I flashed my radio with clockwork.
Sent from my HTC VLE_U using xda premium
thanks guys. very excited to hear that the new radio solved the issue. I was waffling between ditching the HOS for a GNexus but the camera on the HOS and the overall form factor kept keeping me near.
I'll try it as soon as I get back in town.
Please let us know if this works for you.
My girlfriend just bought a T-Mobile one s after seeing how nice my one x was, and she has been plagued with radio problems the entire time. I've ran the latest T-Mobile US RUU hoping it would fix the issues but it has not.
Obviously, I'd like to hold out as long as possible with rooting her phone incase she needs to return it. Anyway, let us know how it goes.
I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
ctennenh said:
I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
Click to expand...
Click to collapse
When you reboot the phone, does the boot image (Default HTC Screen) also have no backlight? Or in recovery is there a backlight? If not, it's a hardware failure. Screen would need to be replaced. If the backlight comes on when in recovery or during first boot image, then it's something software related which is easier to fix.
There's no backlight anywhere. I know it's not kernel since I was able to fastboot flash the default kernel for ViperXL over USB.
If I bought this through AT&T less than a year ago does anyone know if it's under warranty? I'd hate to pay to get the screen replaced. I'd rather try to get it back to stock and take it in.
That's assuming, of course, someone can point me to instructions for getting back to stock! I've looked but haven't seen any in the forum.
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Sent from my HTC One X using xda app-developers app
exad said:
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Click to expand...
Click to collapse
Thanks a ton. I'm already S-Off. I spoke with customer service and they're going to send me a replacement device (same model, though I asked if it was possible to change). Should I be using the one labeled [ruu] [stock] att 2.20 ota? There are a few whose names look like what I might want.
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Sent from my HTC One X using xda app-developers app
exad said:
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Click to expand...
Click to collapse
Ok, so like [STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 ? And the RUU will wipe anything that's not stock, right? Thanks.
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Sent from my HTC One X using xda app-developers app
exad said:
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Click to expand...
Click to collapse
I see. So you don't think they'd bother digging too deeply to notice it's s-off and unlocked? I'll run the RUU tonight and check in later.
I really appreciate your help this evening.
Since it's a hardware issue, I doubt they'll care to dig That far into it. From what I see on here AT&T is pretty lenient about unlocked phones, especially when it's a hardware issue.
Sent from my Sony Tablet S using xda app-developers app
I'm having difficulty running the RUU. I've rebooted and connected my device to my computer and run the RUU utility. It says it can't find the device and to check the connection. I can't see the screen well enough to turn debug mode on or off on the device. What can I do to run the RUU?
Try running while in bootloader/fastboot?
Sent from my Sony Tablet S using xda app-developers app
That did it, thanks. Now to wait until the sun is bright enough out today to wipe the SD card through settings.
I'm going to miss being rooted.
So I have used TMOUS rom for ALONG time and recently decided to switch to use Cyanogen being a fan of it form other platforms.
While on the TMOUS rom I had 4g connectivity in my area about 90% of the time with the occasional drop into 3g here and there. It always displayed a 4g image in the top.
When I switched to Cyanogen that pretty much stoped. It always says 3g and is slow as hell. every once in awhile it will say H+ but not for long. MOST of the time it is constantly switching between 3g/4g/edge then shutting off.
Now im not sure if its a rom problem or not, but its making me want to switch back to a TMOUS rom.
Any suggestions would be great!
Edit: Just for clairification, I am S-On
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
cp101 said:
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
Click to expand...
Click to collapse
Damn, this scares me.... any solution anyone?
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
cp101 said:
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be a hardware problem
I have been trolling the net for weeks but have not found a solution yet.
I've posted in threads here but no solution.....
My issues started when I went to CM ROM - I used to have great 4g all the time before I went to custom rom (I was on stock TMO US) .. Now no matter what I do, I am not able to get 4G again.... it's really irritating...
I've tried a bunch of custom ROMS.. I am on 1.13 HBOOT and S-ON .. .. CID = HTC__001 (originally my CID was stock TMO US CID whatever that is but now its not that.. I don't wan to run RUU because I don't have TMO US CID and dont want to brick my phone)
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
cp101 said:
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
Click to expand...
Click to collapse
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
bnd10706 said:
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
Click to expand...
Click to collapse
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
cp101 said:
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
Click to expand...
Click to collapse
my phone is still under warrenty. Im wondering if i am able to revert back to stock without them knowing if I can get a phone replacement.
From what I've read, it's doable; even with an unlocked phone. But I'd really like to know what in the dev's source code made this happen... it's a bit ridiculous.
jenenser83 said:
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
Click to expand...
Click to collapse
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
bnd10706 said:
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
Click to expand...
Click to collapse
Can you take me through the steps you took to achieve all of this? Thanks.
cp101 said:
Can you take me through the steps you took to achieve all of this? Thanks.
Click to expand...
Click to collapse
So what I did first was go into TWRP and selected wipe. Inside wipe i selected EVERYTHING, every little box. Then Wiped it.
This left nothing on the phone but the recovery. I then loaded on SuperSU from TWRP. I download the stock TMOUS rom that was posted earlier in this post.
In TWRP I mounted it and hooked it to computer and transfered the rom over.
Once the rom was on I did the install of the rom.
I rebooted the rom into bootloader.
Once in bootloader i put it into fastboot.
I had previous extracted the boot.img from the rom.
I sent the boot.img over via fastboot which restarted the phone.
Once it got all started up. No issues. I am on 4g 99% of the time now.
Im thinking the issue was definatly based in the CM rom.
Since this worked I wanted to test things out since my phone was pretty much stripped of everything.
I tried out Viper rom and a couple of other non CM based roms, and I have had no issues.
IM back on teh TMOUS rom though. Wifi calling will win over when i go overseas.
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
cp101 said:
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
Click to expand...
Click to collapse
Must be.
I did find something out though doing all my research. Did you ever at any point update the radio? TMobile uses some frequencies that some companies dont use.
It is my understanding that some of these roms are packed with radios that are generic and thus ment for multi carriers.
Not sure if thats your issue, but might want to look into.
Its nice being back on 4g though.
Im rooted, s-on, hboot 1.09 and on viper 2. Im selling my one s on ebay since i bought a nexus 5 and wanted to know the steps to getting the phone back to the stock rom so when sold, the buyer wont have any issues or stability problems.
Thanks!
andrewt328 said:
Im rooted, s-on, hboot 1.09 and on viper 2. Im selling my one s on ebay since i bought a nexus 5 and wanted to know the steps to getting the phone back to the stock rom so when sold, the buyer wont have any issues or stability problems.
Thanks!
Click to expand...
Click to collapse
Here is a post I wrote to someone else, assuming you need t-mobile RUU.exe otherwise use a different RUU.
http://forum.xda-developers.com/showpost.php?p=46260606&postcount=2
Then perform a factory reset from either the settings or through the bootloader.
http://www.htc.com/us/support/howto.aspx?p_id=463&id=315367&p_name=htc-one-s-t-mobile