OK, so last weekend I managed to get my HTC One X (Evita) rooted, but not S-OFF. I made it once successfully through the entire Facepalm process, but the phone remained S-ON for some unknown reason. It was said to me that I may try to flash a custom ROM and then try again, so I flashed to the most recent CleanROM. Since that time, I've had great problems getting my cell service to stay active, and all further attempts to use the Facepalm/S-OFF method have proven useless because I simply can not ever under any circumstance get past the dreaded "device not found" from the command prompt. I should further note that I read about a LOT of people needing to add a few layers of tape to their SIM in order for their service to stay on with this particular phone...so I've already successfully done this and it did not resolve my dropped service issue.
At this point, I don't know which direction to go. Could the ROM be why my service is dropping? I've not done any sort of "radio" update on this phone yet...can that be an issue? I see RUU's listed on the index thread...would flashing to one of those help? If so, is the procedure same as flashing a custom ROM? And how in the world can I get passed the "device not found" error so that maybe, someday, possibly, I can have my S-OFF?
Any help would be greatly appreciated...
OK, so I've done a couple MORE hours of reading, and I've learned this:
1. The signal drops (as well as the occasional reboots which I didn't mention earlier) are consistent with people whose kernel or radio need to be updated to something that appropriately matches the ROM they're running.
2. I'm not imagining things...rooting/updating THIS particular HTC phone is indeed trickier than the other 3 I've rooted in the past...in the sense that following the directions won't always yield you the same results as the next guy. I'm seeing this sentiment in forum posts (even from ROM developers/etc.) quite a bit today, so, if nothing else, I know I haven't lost my mind lol.
So anyways, it seems as though I need to figure out which "kernel" to flash. I've not flashed ANY kernels on this phone so far, and it came stock running Android 4.0. I ultimately want to be running the latest stable version of Android with Sense on this phone. It appeared the answer for me would be the latest CleanROM, which is 4.2.2. and Sense 5. It's been running on my phone for almost a week now and I like it, except for the signal dropping/rebooting.
I don't know if I've added ANY info that will help someone give me good advice, but....anyone?
...and even MORE reading led me to the xda thread for the latest CleanROM, which is littered with folks having the exact same problem as me.
So yeah, I was here thinking all these problems were brought on by me just not "getting it"...but it just so happens that the first ROM I flashed had these issues for folks with not-so-current radios.
I've got several threads pulled up now that will supposedly get me fixed up, but I can't flash a kernel without S-OFF, so I'm back trying to figure out how to get past this stupid "device not found" issue.
Flash a different ROM to get s-off, Android 4.0 or 4.1 will be best. Once you have s-off you can either upgrade to the 2.15 firmware or flash the Beastmode kernel, either of these methods will stop the signal loss issues you've experienced on Cleanrom. Also, please search before posting, the signal loss issue is plastered all over the Cleanrom thread, you can't read more than two or three pages without seeing it mentioned along with the fix.
Sent from my Evita
Related
Quick question:
I've been having wifi issues which I've searched for the solution, but haven't found it. I don't want to downgrade hboot because I see my limitations laying in there somewhere and don't want to mess everything up. Wifi is the the only issue I'm having.
I flashed the Fusion Ultimate v.4 kernel hoping it would help, but it hasn't, although my phone seems to run faster and smoother.
So I'm wondering... will a kernel even really help a wifi issue and, if so, is there one better suited than the Fusion Ultimate?
My phone:
HTC One S (S4) S-On
hboot: 1.14
kernel flashed via Flash Image GIU
It seems many have wifi issues with custom roms and hboot 1.14. Kernels doesnt help.
The only solution Ive seen around the forum is, downgrading the hboot.
In terms of kernel, you are one of the lucky ones who managed to get v4 to boot, welcome to the club Theres a giant bug somewhere in it which causes it to not boot for the majority of the users.
You could try Fusion v3.1 instead - but I doubt that will help your issue.
Surprisingly, it seems to have worked. At least, I assume it did since I made no other changes tonight and Wi-Fi is working. Even when I leave the house, it connects when I get back. Whatever happened, I hope it keeps up.
Thanks for the reply.
Sent from my HTC One S using Tapatalk 2
I'd like to get the feedback from XDA masters on this issue I had.
Here's the steps that led to the problem.
Flashed ROM(Dr No V2), Decide i didn't like it after a day, the wifi was orking.
Entered 4ext recovery did a full wipe.
Used restore to flash my previous fully functioning ROM (EnergyROM-RCMIX)
Rebooted.
After reboot received the message in settings>...>Wifi "error"
I went through a bunch of steps, lots of reboots.
Try restore of an earlier backup - no fix
Reflashed from Zip the original RCMIX ROM, and fastboot flashed boot.img - no fix
Went into recovery and factory reset only. - no fix
Restored the last working ROM (RCMIX) and just fastboot reflashed boot.img
Still not fixed
More reading tried rename of the wpa_supplicant file. nope
One more fastboot flash of boot.img --
Then... turned on "Airplane Mode" for a few minutes. After turning it off Wi-fi "error" was gone and was able to turn it on.
The error changed to "unable to scan for networks"
Rebooted
Went back in and renamed wpa_supplicant.conf 1 more time.
reboot
When I enable wifi this time it scanned and connected.
I left some steps out, but they were just repeats of the ones I listed.
My question after all that is what went wrong?
Lots of threads about the problem but solutions seem to vary.
Is there something in there that I did incorrectly?
Aren't the drivers for the hardware located in the boot.img (as it contains kernel)?
Is there a better way to do this?
trying to get better at this; Insights, advice, comments appreciated.
I do need to get familiar with logcat.
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
bananagranola said:
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
Click to expand...
Click to collapse
Wifi seems to be stable now. Running the restored RCmix. Rebooted a couple times and no issues. I'm interested in gaining some insight into the source and solution of the problem. My next step was to run a stock RUU I have, but your suggesting something close to stock might have worked?
Why didn't a re-flash of the previously functioning ROM (RCmix, zip on sdcard & fastboot boot.img) fix the issue? I did full wipes each and every time. Even full wipes before doing Restores from recovery. Restore should be a straight forward process from recovery, right?
The problem started right after a restore, and I'm not sure what step it was that fixed it. The last thing was renaming the wpa_supplicant.conf file. I left out the part where my restored ROM got stuck in the boot animation. There was something going on with the boot loader. Re-flashing boot.img fixed it.
But the wifi...? Any thoughts.
I'm a little hesitant to flash another ROM for fear of losing wifi again. I use it a lot.
Cremnomaniac said:
I'm looking for some intelligent feedback. Any thoughts on my OP?
Click to expand...
Click to collapse
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
bananagranola said:
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
Click to expand...
Click to collapse
Thanks, but your first comment offered a possible solution, and solutions are important, but as indicated in the title it had been solved. There aren't any comments on the questions I specifically asked. At the least, I was hoping that someone with greater experience could provide insight into the possible causes of loss of wifi (steps, incompatibility of ROM, freak thing, etc.) so I can avoid it in the future.
The renaming of wpa_supplicant.conf came from threads in the XDA forums where similar wifi problems had been encountered. It was a solution with zero risk.
Here: http://forum.xda-developers.com/showthread.php?t=1965812&page=3
Here: http://forum.xda-developers.com/showthread.php?t=1662805
Here: http://forum.xda-developers.com/showthread.php?t=1988190&highlight=wifi+error
Here: http://forum.xda-developers.com/showthread.php?t=703105
If I made any other changes I would mention it. I can see that you may be the only one monitoring this forum, which is unfortunate. You exhibit a lot of patience, but unlike some of the questions posted, I do the research and read directions carefully. The reason I ask questions is to learn, not to have my hand held. And someone posting "ddpo" is a waist of bandwidth. If no one has any comments to my questions, we'll leave it at that.
Because stock is most stable, flashing a stock-ish ROM will reveal whether the problem is a hardware one or a software one. If the problem still exists on stock, your hardware is probably messed up. If the problem doesn't exist on stock, something is up with your ROM. That is why flashing stock is still relevant: for the first step in diagnosis. Other than that, you can look into getting S-Off and flashing an updated radio, but that's up to you.
And I already reported the "ddpo."
crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help
Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion
From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly
talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.
When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita
Recovery: Custom TWRP 2.6.3.0 w/selinux support
And what errors did it give you when trying to install Gummy?
Sent from my Evita
The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.
timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.