Related
I converted my AT&T HTC One M8 to GPE a month or two ago. It has been working great, until yesterday when I applied the 4.4.3 OTA update straight from Google. Now the camara doesn't work "Can't connect to camera", and WIFI won't turn on.
Has anyone else had this problem? Should I have never done the OTA update? I thought once I converted to GPE it was the same as a GPE phone.
Thank you in advance for any help.
apoptosis66 said:
I converted my AT&T HTC One M8 to GPE a month or two ago. It has been working great, until yesterday when I applied the 4.4.3 OTA update straight from Google. Now the camara doesn't work "Can't connect to camera", and WIFI won't turn on.
Has anyone else had this problem? Should I have never done the OTA update? I thought once I converted to GPE it was the same as a GPE phone.
Thank you in advance for any help.
Click to expand...
Click to collapse
This thread discusses GPE update + issues Might want to check out that thread it discussed some of the camera issues there.
By the looks of things it seems it doesn't properly update/install if your CID isn't right. Though you might want to check out the GPE threads that's quite easy to find here and discuss more with them. I don't have the GPE conversion myself so.
BerndM14 said:
This thread discusses GPE update + issues Might want to check out that thread it discussed some of the camera issues there.
By the looks of things it seems it doesn't properly update/install if your CID isn't right. Though you might want to check out the GPE threads that's quite easy to find here and discuss more with them. I don't have the GPE conversion myself so.
Click to expand...
Click to collapse
Thank you, I will definitely check into CID. I forget which one I used when installing there were like 5 available. Its possible I chose the wrong one didn't know there was a right one.
apoptosis66 said:
I converted my AT&T HTC One M8 to GPE a month or two ago. It has been working great, until yesterday when I applied the 4.4.3 OTA update straight from Google. Now the camara doesn't work "Can't connect to camera", and WIFI won't turn on.
Has anyone else had this problem? Should I have never done the OTA update? I thought once I converted to GPE it was the same as a GPE phone.
Thank you in advance for any help.
Click to expand...
Click to collapse
Hi Same happened to me, I reflashed the GPE RUU in fastboot (after backing up data of course) then reboot phone into fastboot and type fastboot writecid GOOGL001 then fastboot reboot then I downloaded OTA and camera and phone is working fine also no lag when rebooting. Not sure if changing the cid after you have updated will work.
Success
StillADefyOwner said:
Hi Same happened to me, I reflashed the GPE RUU in fastboot (after backing up data of course) then reboot phone into fastboot and type fastboot writecid GOOGL001 then fastboot reboot then I downloaded OTA and camera and phone is working fine also no lag when rebooting. Not sure if changing the cid after you have updated will work.
Click to expand...
Click to collapse
I changed me CID to GOOGL001 and then flashed the new 4.4.3 RUU and everything is fine. Thank you guys!
apoptosis66 said:
I changed me CID to GOOGL001 and then flashed the new 4.4.3 RUU and everything is fine. Thank you guys!
Click to expand...
Click to collapse
Good to hear then :good:
It works
apoptosis66 said:
I changed me CID to GOOGL001 and then flashed the new 4.4.3 RUU and everything is fine. Thank you guys!
Click to expand...
Click to collapse
I also changed my CID to GOOGL001 and then reflashed the 4.4.3 RUU. Everything is running fine. Just remember re flashing the RUU erases all data, so backup first!
Hey guys,
I've been searching but couldn't find anything that really helps with my problem. I bought an HTC One M8 last year, it was supposed to be unlocked from factory but when it arrived it turned out it was an unlocked AT&T model. Anyways so I tried to root the phone but it was already rooted and running a TWRP (I don't know how this happened as the phone was sealed when I got it) I have no problem with this but as the phone is rooted and doesn't have the stock recovery I can't get any OTA and I'm still in 4.4.2. I was wondering if any of you guys could help me update my device to stock 5.0.1 without flashing a custom ROM.
Thanks
rj.camargo said:
I've been searching but couldn't find anything that really helps with my problem. I bought an HTC One M8 last year, it was supposed to be unlocked from factory but when it arrived it turned out it was an unlocked AT&T model. Anyways so I tried to root the phone but it was already rooted and running a TWRP (I don't know how this happened as the phone was sealed when I got it) I have no problem with this but as the phone is rooted and doesn't have the stock recovery I can't get any OTA and I'm still in 4.4.2. I was wondering if any of you guys could help me update my device to stock 5.0.1 without flashing a custom ROM.
Click to expand...
Click to collapse
First off, there is no stock 5.0.1 for the AT&T version yet. There isn't even a 4.4.4 released yes (although it might be anytime soon).
Further, you aren't going to receive any OTAs since you aren't connected to the AT&T network. Some folks not specifically familiar with AT&T will disagree, saying the OTAs will come over WiFi even if not connected to the specific carrier. But AT&T is pretty unique in this regard (well, maybe other carriers in the US do it too, but not WWE versions).
You can download an official RUU to upgrade to 4.4.3. Then wait for RUUs to be posted for 4.4.4 and/or 5.0.1. That is all you can do at this time without s-off. With s-off, you can convert to any version you want, and get official OTAs that way (such as convert to WWE version), or run the US Developer's Edition 5.0 RUU.
redpoint73 said:
First off, there is no stock 5.0.1 for the AT&T version yet. There isn't even a 4.4.4 released yes (although it might be anytime soon).
Further, you aren't going to receive any OTAs since you aren't connected to the AT&T network. Some folks not specifically familiar with AT&T will disagree, saying the OTAs will come over WiFi even if not connected to the specific carrier. But AT&T is pretty unique in this regard (well, maybe other carriers in the US do it too, but not WWE versions).
You can download an official RUU to upgrade to 4.4.3. Then wait for RUUs to be posted for 4.4.4 and/or 5.0.1. That is all you can do at this time without s-off. With s-off, you can convert to any version you want, and get official OTAs that way (such as convert to WWE version), or run the US Developer's Edition 5.0 RUU.
Click to expand...
Click to collapse
Excuse me but what is WWE exactly? Ok so my two options are use sunshine to make my htc s-off and convert to another version or flash a custom rom with 5.0.1?
Thanks for your help.
rj.camargo said:
Excuse me but what is WWE exactly?
Click to expand...
Click to collapse
World Wide English. Which doesn't really say much. Its the "international" version sold in Europe and other places.
rj.camargo said:
Ok so my two options are use sunshine to make my htc s-off and convert to another version or flash a custom rom with 5.0.1?
Click to expand...
Click to collapse
Nope, your second option won't work. You need firmware on your phone that is compatible with 5.0.1, otherwise WiFi will be broken, and.or extreme long boot times (>10 minutes). And the only way to update your firmware is with s-off (until AT&T releases more updates).
So really, if you want to update now, your only option is s-off.
Ok dude, thanks for your help. I guess I'll have to s-off
rj.camargo said:
Ok dude, thanks for your help. I guess I'll have to s-off
Click to expand...
Click to collapse
If you want to update now, that is what I suggest. I don't see LP coming to AT&T for another month at least, and it might be even longer than that (months). We're still waiting for 4.4.4.
Be sure to check bootloader and confirm if its s-on or s-off (says one or the other near the top of the hboot screen). Since it was already rooted and bootloader unlocked, who knows, you might have lucked out and gotten a phone that is already s-off as well.
Yeah and like you said if I'm not connected to the AT&T network I might never get the update so it is the only option. BTW I checked and it's S-On =(
Thanks for your help.
When will the Dev edition get updated to 5.1? I thought the dev edition gets updated faster than the carrier editions.
http://forum.xda-developers.com/showpost.php?p=61670999&postcount=879
SWEEET!
SO after updating the Dev Edtion, i can be on the latest ARHD and Maximus ROMS with no issues with reboots and stuff?
Quadrider10 said:
When will the Dev edition get updated to 5.1? I thought the dev edition gets updated faster than the carrier editions.
Click to expand...
Click to collapse
New update now in the process. Almost 800mb. Software 2.6.651.11
I'm downloading the new OTA update now on my Dev. Edition 2.6.651.11
Sent from my HTC One M9 using Tapatalk
scoot0073 said:
I'm downloading the new OTA update now on my Dev. Edition 2.6.651.11
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Do you have to unroot to allow OTA´s on DevEd? Thanks in advance.
It's not up on the HTC website....
Quadrider10 said:
It's not up on the HTC website....
Click to expand...
Click to collapse
No the RUU is not up yet
Just flash the 1.32 RUU and check for updates. It worked fine today
Sent from my HTC One M9 using Tapatalk
I did same, flashed the most recent RUU and did the OTA.
Is there any reason to not accept this update? I haven't modified mine yet, but I want to root and go to CM later on.
Slusho said:
Is there any reason to not accept this update? I haven't modified mine yet, but I want to root and go to CM later on.
Click to expand...
Click to collapse
I would S-off before updating just to be sure you have it
Sent from my HTC One M9 using Tapatalk
rickylambert said:
Do you have to unroot to allow OTA´s on DevEd? Thanks in advance.
Click to expand...
Click to collapse
Yea you need to flash to stock to update via OTA
---------- Post added at 06:16 AM ---------- Previous post was at 06:15 AM ----------
Slusho said:
Is there any reason to not accept this update? I haven't modified mine yet, but I want to root and go to CM later on.
Click to expand...
Click to collapse
i would say yes update ur phone, camera improvement is kinda big tho in low light its still crappy. overall its getting better
I'm not noticing camera improvements but I am noticing a big increase in performance. However, here's a fun bug: I keep waking up to it charging to only 78% or so. When I unplug and plug it back in, it starts charging higher. I've never seen a bug like this before, and it could make this unusable for me.
Also, I thought s-off just unlocked the bootloader, which is the whole point of the Dev Edition. So shouldn't that be unnecessary?
Slusho said:
I'm not noticing camera improvements but I am noticing a big increase in performance. However, here's a fun bug: I keep waking up to it charging to only 78% or so. When I unplug and plug it back in, it starts charging higher. I've never seen a bug like this before, and it could make this unusable for me.
Click to expand...
Click to collapse
What charger are you using? I found that with an older charger that worked fine on my M8, I had weird charging issues since upgrading to 1.40 firmware. Updating to 2.7, and now 2.8, firmware fixed these for the most part, but still don't get a good full charge on that old charger. On the charger that came with the M9 seems to work just fine.
Slusho said:
Also, I thought s-off just unlocked the bootloader, which is the whole point of the Dev Edition. So shouldn't that be unnecessary?
Click to expand...
Click to collapse
Those are two separate things...unlocked bootloader lets you flash custom recovery (TWRP) and therefore root and install custom ROMs, provided they work with your device's current firmware.
S-Off lets you flash new firmware as soon as it's released rather than wait for your specific carrier to release an OTA. S-Off also lets you change your device's CID and MID, so you can convert your device to developer edition, international, etc. Also with S-Off you can do other things like change your software status in bootloader back to "Official" after it gets changed to "Modified".
jollywhitefoot said:
What charger are you using?
Click to expand...
Click to collapse
I'm using the iClever charger from here: http://amazon.com/gp/product/B00J94OAG8
jollywhitefoot said:
S-Off lets you flash new firmware as soon as it's released rather than wait for your specific carrier to release an OTA. S-Off also lets you change your device's CID and MID, so you can convert your device to developer edition, international, etc. Also with S-Off you can do other things like change your software status in bootloader back to "Official" after it gets changed to "Modified".
Click to expand...
Click to collapse
It sounds like there's no reason to get S-Off on the Dev Edition then, since I'm not going to want to flash a a carrier-specific firmware, and I don't need to change the status since HTC isn't going to deny warranty service because of modified software.
Slusho said:
I'm using the iClever charger from here: http://amazon.com/gp/product/B00J94OAG8
It sounds like there's no reason to get S-Off on the Dev Edition then, since I'm not going to want to flash a a carrier-specific firmware, and I don't need to change the status since HTC isn't going to deny warranty service because of modified software.
Click to expand...
Click to collapse
When I had the issue changing to the stock charger worked for me.
With S-Off you could have flashed the leaked 2.7 firmware a couple of weeks before the official 2.8 was released. You can also change your device status in bootloader back to "Official" from "Modified".
Other than that, if you're capable of returning your device to stock system image so that you can get OTA updates, there's not much of an advantage.
Other advantages of S-Off include the ability to return the device to 100% stock and the ability to use this method (http://forum.xda-developers.com/one-m9/general/sim-unlock-method-t3143333) to sim unlock.
So what's easier: getting S-Off or returning to the stock system image?
Slusho said:
So what's easier: getting S-Off or returning to the stock system image?
Click to expand...
Click to collapse
I've never returned to to stock using the system image. I always just run an RUU because i don't keep much data on my internal storage.
S-Off is pretty simple. Just root, download the sunshine apk and run it. after a few reboots, you're good to go.
So, having said that, I would tend to think they're about the same degree of difficulty.
The latest HTC updates arrived this morning (Connect, Dot View, Lock Screen, Mail, MirrorLink), and my phone prompted me to restart to update the lock screen. I did, and now my wifi won't turn on.
I've tried restarting and turning on/off airplane mode, to no avail.
(Stock HTC One M8 running Android 6.0, Sense 7.0, software 6.12.111.4)
Any ideas, and/or is anyone else having this problem?
Edit: I tried Bluetooth in the meantime, and it's turning on but won't find devices/connect to existing ones, so it looks like that's shot too.
do you have telephone network working?
leecavturbo said:
do you have telephone network working?
Click to expand...
Click to collapse
Yeah, mobile data/calls work fine.
I was on to HTC Support earlier on and they suggested doing a hard reset, which I just did, and no luck.
It did say "Failed to load driver", so I'm wondering if I just got a bad driver in the update... Is there a way to check/fix it?
Kanhir said:
It did say "Failed to load driver", so I'm wondering if I just got a bad driver in the update... Is there a way to check/fix it?
Click to expand...
Click to collapse
If there is an RUU for 6.12.111.4, that is probably your best bet at this point.
redpoint73 said:
If there is an RUU for 6.12.111.4, that is probably your best bet at this point.
Click to expand...
Click to collapse
This is the bit where I admit my ignorance of what an RUU is.
I followed the instructions here to load a nandroid backup of 6.12.111.4, and it didn't fix the issue. Is this different to an RUU?
Edit: I did some internet hunting and found that RUUs for my SKU only go up as far as 4.19.111.2. Is it possible to use that RUU to install an older firmware, then search for OTAs on the phone and re-upgrade that way?
Kanhir said:
I followed the instructions here to load a nandroid backup of 6.12.111.4, and it didn't fix the issue. Is this different to an RUU?
Click to expand...
Click to collapse
A stock nandroid is just the system and boot partitions, where an RUU is a full re-write of all partitions. That's the main difference.
But restoring the stock nandroid was not a bad idea, to at least try. Of course, since it didn't fix the issue we'll have to keep looking for a fix.
Kanhir said:
Edit: I did some internet hunting and found that RUUs for my SKU only go up as far as 4.19.111.2. Is it possible to use that RUU to install an older firmware, then search for OTAs on the phone and re-upgrade that way?
Click to expand...
Click to collapse
You can't "downgrade" by RUU (run an older RUU) unless you have s-off.
Now, if you restored a 6.12.111.4 nandroid didn't fix the issue, and no corresponding RUU is available (did you do an XDA search, not just around the web via Google? - sometimes folks post the RUUs direct to this forum) that leaves us in a tough spot; and you may well have to resort to s-off ($25 by sunshine app).
Have you found a fix yet?
Im having the exact same issue, i've searched everywhere and cannot find a fix have you found one yet?
also having this issue, can't find a suitable RUU for S-ON.
wouldn't it be possible to do a 4.something stock nandroid restore and then use a RUU?
dx125 said:
also having this issue, can't find a suitable RUU for S-ON.
wouldn't it be possible to do a 4.something stock nandroid restore and then use a RUU?
Click to expand...
Click to collapse
I'm not clear what you are suggesting: RUU for your version, but older version 4.xx; or another versions (CID) RUU.
Either way, you can't do those with s-on.
redpoint73 said:
I'm not clear what you are suggesting: RUU for your version, but older version 4.xx; or another versions (CID) RUU.
Either way, you can't do those with s-on.
Click to expand...
Click to collapse
i was referencing the downgrading issue. if there is a RUU available for 4.9.111.2, you could do a stock restore to that version before.
doesn't help me though, can't find any suitable RUU for my CID.
dx125 said:
i was referencing the downgrading issue. if there is a RUU available for 4.9.111.2, you could do a stock restore to that version before.
doesn't help me though, can't find any suitable RUU for my CID.
Click to expand...
Click to collapse
As I already stated, you can't do it with s-on, even if there was a Lollipop RUU for your version.
You can't run a previous version RUU (downgrade) unless you have s-off.
ok i solved it for my case. the problem i had was an outdated firmware, as mentioned here: http://forum.xda-developers.com/htc-one-m8/help/wi-fi-wont-flashing-custom-rom-t3349613
so basically what i did was flashing the latest firmware i could find (4.19) an then installing a custom rom. i guess after flashing the firmware one could also just restore a nandroid backup
dx125 said:
ok i solved it for my case. the problem i had was an outdated firmware, as mentioned here: http://forum.xda-developers.com/htc-one-m8/help/wi-fi-wont-flashing-custom-rom-t3349613
so basically what i did was flashing the latest firmware i could find (4.19) an then installing a custom rom. i guess after flashing the firmware one could also just restore a nandroid backup
Click to expand...
Click to collapse
So you didn't have the same issue as the OP of this thread. Theirs was a completely different issue: official OTA caused WiFi broken vs. your case of a custom ROM with outdated firmware.
Its much easier to help folks when they describe the problem properly instead of saying "I have the same problem". Which from my experience its almost never the case where its exactly the same problem (and better to give specific details).
Next time, please provide more details in order for us to help you properly.
redpoint73 said:
So you didn't have the same issue as the OP of this thread. Theirs was a completely different issue: official OTA caused WiFi broken vs. your case of a custom ROM with outdated firmware.
Its much easier to help folks when they describe the problem properly instead of saying "I have the same problem". Which from my experience its almost never the case where its exactly the same problem (and better to give specific details).
Next time, please provide more details in order for us to help you properly.
Click to expand...
Click to collapse
i've had the issue after restoring a nandroid stock backup, which was also tried by others in this thread. but yes, maybe my problem was different.
Hi just bought a 32gb international version HTC One M8 that was converted into GPe. Then I reverted back using RUU and this firmware (1.54.401.5-W_Splash). Now that I've flashed a S-rom. Wifi isn't working. I asked the guy what was the original CID No. but he forgotten. So the question here is how do I find the right firmware?
pyrohalo90 said:
Hi just bought a 32gb international version HTC One M8 that was converted into GPe. Then I reverted back using RUU and this firmware (1.54.401.5-W_Splash). Now that I've flashed a S-rom. Wifi isn't working. I asked the guy what was the original CID No. but he forgotten. So the question here is how do I find the right firmware?
Click to expand...
Click to collapse
If "401" RUU worked before (Euro version), than another 401 (x.xx.401) RUU is what you want.
Try this RUU (6.12.401): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
redpoint73 said:
If "401" RUU worked before (Euro version), than another 401 (x.xx.401) RUU is what you want.
Try this RUU (6.12.401): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I just solved my issue by finding out that my M8 is Dev Edition. So I flashed the latest firmware fw_6.12.1540.4 for the BS_US002, 0P6B12000. Wifi works like a charm now. Anyways thnks for your reply!
Back in August, I got a HTC One M9 from Bluegrass Cellular. (The phone came with Android 5.1) I decided to root it and try a custom ROM. I downloaded a snapshot for CM13 himawl. (Since that's the variant according to Download mode) I flashed it in TWRP only to get an error about sbl1. I since found an unofficial nightly of cm12.1 himawl built on November 17, 2015. It flashed and works fine to this day, but I'd like to have newer features and better security. How would I go about doing this? I can't seem to find the correct RUU. I tried the unlocked RUU to see if it would work, but it was to no avail. I'm S-on if that helps.
purplekid97 said:
Back in August, I got a HTC One M9 from Bluegrass Cellular. (The phone came with Android 5.1) I decided to root it and try a custom ROM. I downloaded a snapshot for CM13 himawl. (Since that's the variant according to Download mode) I flashed it in TWRP only to get an error about sbl1. I since found an unofficial nightly of cm12.1 himawl built on November 17, 2015. It flashed and works fine to this day, but I'd like to have newer features and better security. How would I go about doing this? I can't seem to find the correct RUU. I tried the unlocked RUU to see if it would work, but it was to no avail. I'm S-on if that helps.
Click to expand...
Click to collapse
I'm pretty sure that in order to use a Marshmallow-based ROM (ie, CM 13), you need the Marshmallow firmware first. I imagine the same will be true for Nougat ROMs....though I don't think we've got anything beyond stock just yet.
I imagine that if you were able to achieve S-OFF on your phone, you could apply the appropriate RUU to get you up to the latest available firmware for your phone. To be clear, I don't know what that is (I'm not familiar with the himawl models) - but it should be possible.
computerslayer said:
I'm pretty sure that in order to use a Marshmallow-based ROM (ie, CM 13), you need the Marshmallow firmware first. I imagine the same will be true for Nougat ROMs....though I don't think we've got anything beyond stock just yet.
I imagine that if you were able to achieve S-OFF on your phone, you could apply the appropriate RUU to get you up to the latest available firmware for your phone. To be clear, I don't know what that is (I'm not familiar with the himawl models) - but it should be possible.
Click to expand...
Click to collapse
I believe that's what's going on here. I'm just trying to see if there are any alternatives or RUU's known to work with my s-on phone before I resort to the $25 investment of Sunshine.
purplekid97 said:
I believe that's what's going on here. I'm just trying to see if there are any alternatives or RUU's known to work with my s-on phone before I resort to the $25 investment of Sunshine.
Click to expand...
Click to collapse
Just for the fact you get an extra chance to unbrick if it goes wrong is worth the $25. IMO S-OFF is a necessity for htc phones.
Beamed in by telepathy.
I tried the test in the Sunshine app, but it said to flash stock or near stock rom. I mistakenly didn't backup my stock ROM before flashing cm12.1. Anyone know a ROM I could flash to s off?
purplekid97 said:
I tried the test in the Sunshine app, but it said to flash stock or near stock rom. I mistakenly didn't backup my stock ROM before flashing cm12.1. Anyone know a ROM I could flash to s off?
Click to expand...
Click to collapse
You're on Android 5, right? Android Revolution HD 14, which is built off of stock Android 5.1.0, should do the trick.
Very important sidenote: Don't change the MID/CID or the firmware of this device! It's a CDMA one and therefore not compatible with the GSM firmwares like the dev edition or the WWE one. Otherwise you'll end up with a fancy new paperweight. Just stay with the SKU (the three numbers between the second and the third dot in the firmware version) it is currently using since not even the different CDMA firmwares/devices are compatible with each other.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Very important sidenote: Don't change the MID/CID or the firmware of this device! It's a CDMA one and therefore not compatible with the GSM firmwares like the dev edition or the WWE one. Otherwise you'll end up with a fancy new paperweight. Just stay with the SKU (the three numbers between the second and the third dot in the firmware version) it is currently using since not even the different CDMA firmwares/devices are compatible with each other.
Click to expand...
Click to collapse
In my case, the SKU is 605. Is there a newer 605 I can update to access Marshmallow? I recall when I was stock, I tried to update to MM through OTA in settings, but apparently my carrier never approved the update. 5.1 appeared to be the "latest."
605 is the verizon-branded firmware. There definitely is an android m update for your phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
605 is the verizon-branded firmware. There definitely is an android m update for your phone.
Click to expand...
Click to collapse
Awesome! With my CID being LRA__001 would I be able to flash this?
0PJAIMG_HIMA_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_3.3 [email protected]_CNV_1.26_002 _release_469809_signed_1 zip
The problem is it looks like it's WWE which you said wouldn't work.
purplekid97 said:
Awesome! With my CID being LRA__001 would I be able to flash this?
0PJAIMG_HIMA_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_3.3 [email protected]_CNV_1.26_002 _release_469809_signed_1 zip
The problem is it looks like it's WWE which you said wouldn't work.
Click to expand...
Click to collapse
It's Verizon WWE. That's not the same as sku 401 (WWE).
Either you try that one or you download the exe from the HTC US website.
I can't say for sure whether it'll work. According to the sku the RUU should be flashable. You'll need to try by yourself. An alternative would be contacting llabtoofer's RUU service. However that one isn't for free. (Either search for it via google or use the direct link in my google sheet if you want to use that service.)
Sent from my HTC One M9 using XDA Labs
here's your RUU
KhurshidAbbas said:
I mistakenly flashed verizon firmware and now I've lost the network signals, My phone is currently in boot loop, restarting at it's own, I can't use open Mobile Networks App, My networks are not working at all, Some expert told me it's because I flashed wrong Radio.img along with rest of firmware.
Please provide me with stock firmware for Bluegrass Cellular.
I've lost every hope.
Click to expand...
Click to collapse
Source:
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Download:
https://www.androidfilehost.com/?fid=24591023225177985
Flippy498 did all the work. I just did some searching
rename to 0PJAIMG.zip place on sd card and reboot should fix it
Again its Flippy498's work