Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Hope you are on latest 4.4.4 firmware , link for the same should be in OP/FAQ of Viper.
fandam said:
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Click to expand...
Click to collapse
If you are only unlocked and not s-off you will need to manually flash the corresponding boot.img for each rom each time you flash a new rom. If you can get s-off you won't need to do this anymore.
Firmware needs to be updated. Confirmed on OP's other thread here: http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-bricked-t2989202/page2
Also its not necessary to manually extract and flash boot.img on the M8, even when s-on. Folks giving this advice may be carrying over knowledge from an older HTC device.
Related
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Xanion said:
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Click to expand...
Click to collapse
Kicking my own question. No-One who has an idea or thought? I've tried everything I could think off and would appreciate some fresh thoughts.
I have almost the same problem now. I was running CWM 10.2 with the TWRP recovery and reverted back to stock using a backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140
The installation went fine, but touch isn't working anymore. What could be wrong? I would like to have my phone back to stock and use the OTA from HTC.
I flashed Android Revolution HD to my HTC One M8 over the weekend (I was coming from Viperone). At first I was stuck in a bootloop so I tried to restore back to Viperone, but I had the same problem. I restored to rooted (stock) and was finally able to download and flash Android Revolution; however, no I can't get my wifi to turn on. I've tried wifi fixer and it hasn't helped.
I really like the look/feel of the ROM but I can't not have wifi.
Android version 4.3.3
Thanks!
For Sense 2.22 based ROMs (such as the current ARHD) its recommended to flash the updated firmware package. Broken WiFi is a known issue if you skip this step.
More info here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
If you aren't comfortable with this, you can flash one of the older 1.5X based ROMs. Or GPE may be okay, as well.
I had exactly the same problem on many 4.4.3 roms. Only using stock kernel helped, but the boot time of a device was about 4min instead of matter of seconds.
Everything works great on skydragon rom (with their kernel).
Sent from HTC One m8, or maybe not anymore
Firmware
I tried updating the firmware over the weekend, after following the link provided by redpoint73 (http://forum.xda-developers.com/show...postcount=9592) I installed the new firmware 2.22.401.4, it went smoothly up to the point where i rebooted and my cell radio wouldn't connect.
I had to install the original firmware and then reinstall TWRP. I'm rooted with Android 4.4.2. What firmware do I use when updating so that my verizon radio isn't impacted.
Thanks!
So I have the interesting problem with Google services. When I am on wifi I have no issues what so ever. When I am just on cell data Google search doesn't work, Gmail doesn't, ingress doesn't, contacts don't sync, play store won't open etc. All other internet works perfectly fine though. I am currently usinuslatest viper Rom. And am on the latest firmware and on AT&T. I have tried a couple other roms and same problem...except MIUI. Everything on MIUI worked perfectly fine no issues what so ever...Does anyone have any ideas on what the issue could be.
malac0da13 said:
So I have the interesting problem with Google services. When I am on wifi I have no issues what so ever. When I am just on cell data Google search doesn't work, Gmail doesn't, ingress doesn't, contacts don't sync, play store won't open etc. All other internet works perfectly fine though. I am currently usinuslatest viper Rom. And am on the latest firmware and on AT&T. I have tried a couple other roms and same problem...except MIUI. Everything on MIUI worked perfectly fine no issues what so ever...Does anyone have any ideas on what the issue could be.
Click to expand...
Click to collapse
Have you tried GPE roms? Did you make sure you did a full wipe when you hop around sense roms? What about AOSP roms, do they have the same issue? I never faced this issue on my M8 though
I have TWRP on my phone. I think it's the latest. I do a factory reset and then wipe the system partition then flash. I tried an aosp Rom and had the same problem not sure about GPE based Rom though. I think MIUI is GPE based though. I will try a GPE Rom though and see.
malac0da13 said:
I have TWRP on my phone. I think it's the latest. I do a factory reset and then wipe the system partition then flash. I tried an aosp Rom and had the same problem not sure about GPE based Rom though. I think MIUI is GPE based though. I will try a GPE Rom though and see.
Click to expand...
Click to collapse
All you need to do is a factory reset.No need for a system partition wipe.
malac0da13 said:
So I have the interesting problem with Google services. When I am on wifi I have no issues what so ever. When I am just on cell data Google search doesn't work, Gmail doesn't, ingress doesn't, contacts don't sync, play store won't open etc. All other internet works perfectly fine though. I am currently usinuslatest viper Rom. And am on the latest firmware and on AT&T. I have tried a couple other roms and same problem...except MIUI. Everything on MIUI worked perfectly fine no issues what so ever...Does anyone have any ideas on what the issue could be.
Click to expand...
Click to collapse
Known issue if you try to run some custom ROMs on AT&T. Something about build.prop on Euro ROMs breaks Google services on AT&T LTE.
Flashing the US Dev Edition firmware (3.28.1540) and the 4.4.4 Sense ROM by Wonders_Never_Cease should fix it:
http://forum.xda-developers.com/att-htc-one-m8/help/lte-connection-issues-3-28-401-7-t2913168
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
OK I flashed the firmware from that link you posted. I now have a problem. I had relocked my phone to flash firmware before and I am not sure how to unlock it again. I was able to reflash a recovery because the rom that was installed on it booted far enough for me to adb shell into it. I may not get so lucky next time though. I am not sure where my oem_unlock.bin file is though. Can I get another from HTC?
NVM I got it squared away. Just dedid the stuff for the htcdev site and got it sent again.
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.