Related
Hello guys, I need a asap help and will be very thankful for guidance.
I recently bought a used HTC one M8 Gold 32GB, it is in pristine condition, just weeks used, but when I came home and did a reset I realized that it was a rooted phone. But then I discovered that there were some apps like Sprint Worldwide and there were many instances where I found Sprint written, (I have no SIM installed and neither do we have Sprint in our country). So I ended up assuming that it was rooted by the original user solely to unlock the device? I am currently in 4.4.2 and unable to update as it keeps stucking on checking screen. Now I want to revert the device to its original condition and need help doing that. I heard that it can be done by installing RUU so I went to:
htc . com / us / support/rom-downloads
and downloaded: 4.25.651.18 (assuming it is a Sprint)
and then placed it in the sdcard but after HBOOT takes some loading time, it just says invalid image. I have also tried renaming it with no hope.
the bootloader is Locked/ M8_WHL PVT SHIP S-OFF.
redfaction95 said:
Hello guys, I need a asap help and will be very thankful for guidance.
I recently bought a used HTC one M8 Gold 32GB, it is in pristine condition, just weeks used, but when I came home and did a reset I realized that it was a rooted phone. But then I discovered that there were some apps like Sprint Worldwide and there were many instances where I found Sprint written, (I have no SIM installed and neither do we have Sprint in our country). So I ended up assuming that it was rooted by the original user solely to unlock the device? I am currently in 4.4.2 and unable to update as it keeps stucking on checking screen. Now I want to revert the device to its original condition and need help doing that. I heard that it can be done by installing RUU so I went to:
htc . com / us / support/rom-downloads
and downloaded: 4.25.651.18 (assuming it is a Sprint)
and then placed it in the sdcard but after HBOOT takes some loading time, it just says invalid image. I have also tried renaming it with no hope.
the bootloader is Locked/ M8_WHL PVT SHIP S-OFF.
Click to expand...
Click to collapse
First you need to post the results of fastboot getvar all. REMOVE your serial and IMEI numbers from the pasted info before posting. We need to see hopefully the firmware that is currently on the device.
If it is Sprint and you have downloaded the correct RUU file, you do NOT put it on the SD card, you leave it on your Windows PC, attach the device to the PC with USB cable and run the RUU as administrator in Windows. Before that, download HTC Sync Manager and let it install, then delete it. It will leave behind the HTC drivers which you need.
Einwod said:
First you need to post the results of fastboot getvar all. REMOVE your serial and IMEI numbers from the pasted info before posting. We need to see hopefully the firmware that is currently on the device.
If it is Sprint and you have downloaded the correct RUU file, you do NOT put it on the SD card, you leave it on your Windows PC, attach the device to the PC with USB cable and run the RUU as administrator in Windows. Before that, download HTC Sync Manager and let it install, then delete it. It will leave behind the HTC drivers which you need.
Click to expand...
Click to collapse
Thanks for the reply brother.
i.imgur . com / 2woLrs5.jpg
(Sorry, I have less than 10 posts )
And for your 2nd paragraph part, all done as you said, have installed everything and then uninstalled the htc sync as well, now jus waiting for you to confirm which version is my M8, if it is Sprint as you say, then I will flash it right away (I know risk is on me).
redfaction95 said:
Thanks for the reply brother.
i.imgur . com / 2woLrs5.jpg
(Sorry, I have less than 10 posts )
And for your 2nd paragraph part, all done as you said, have installed everything and then uninstalled the htc sync as well, now jus waiting for you to confirm which version is my M8, if it is Sprint as you say, then I will flash it right away (I know risk is on me).
Click to expand...
Click to collapse
It's definitely Sprint but the firmware is ancient. Run the RUU file and hopefully it will go thru. If not, we'll have to find a way to update your firmware one at a time, but as you are S-OFF it will be easy enough as long as we can find the firmwares.
Sprint RUU can be found Here, this is the latest Lollipop version.
Get your phone into fastboot mode and simply run the RUU .exe file while your phone is plugged into the computer via USB.
Einwod said:
It's definitely Sprint but the firmware is ancient. Run the RUU file and hopefully it will go thru. If not, we'll have to find a way to update your firmware one at a time, but as you are S-OFF it will be easy enough as long as we can find the firmwares.
Click to expand...
Click to collapse
Viper4713 said:
Sprint RUU can be found. this is the latest Lollipop version.
Get your phone into fastboot mode and simply run the RUU .exe file while your phone is plugged into the computer via USB.
Click to expand...
Click to collapse
Thanks a ton mates, done as you said, everything is up and running butter smooth, now i am updated to 5.0.2 with a full clean install + update option now works as well and recovery is also working now. Just one more question, i dont see 3G anywhere in settings, but 4G is there, does my particular device doesnot come with 3G support?
redfaction95 said:
Thanks a ton mates, done as you said, everything is up and running butter smooth, now i am updated to 5.0.2 with a full clean install. Just one more question, i dont see 3G anywhere in settings, but 4G is there, does my particular device doesnot come with 3G support?
Click to expand...
Click to collapse
It should all be there. When you connect to a data network, what symbol shows on the status bar?
Einwod said:
It should all be there. When you connect to a data network, what symbol shows on the status bar?
Click to expand...
Click to collapse
A gsm sign sorrounded with a dotted circle
redfaction95 said:
A gsm sign sorrounded with a dotted circle
Click to expand...
Click to collapse
I have no idea. I can change my symbol using Xposed modules, though normally mine chows 3G or H. Have you looked in settings/mobile data/network mode? Currently mine shows3G only, 2G/3G auto and 2G/3G/4G auto.
Einwod said:
I have no idea. I can change my symbol using Xposed modules, though normally mine chows 3G or H. Have you looked in settings/mobile data/network mode? Currently mine shows3G only, 2G/3G auto and 2G/3G/4G auto.
Click to expand...
Click to collapse
imgur.com / xcJHIVE
redfaction95 said:
imgur.com / xcJHIVE
Click to expand...
Click to collapse
Sprint phones are different from a lot of others. I forgot about CDMA. Mine is GSM. Sorry I can't help further.
Einwod said:
Sprint phones are different from a lot of others. I forgot about CDMA. Mine is GSM. Sorry I can't help further.
Click to expand...
Click to collapse
What if i flash it with the international/unlocked version of RUU like yours?
redfaction95 said:
What if i flash it with the international/unlocked version of RUU like yours?
Click to expand...
Click to collapse
It won't work. If your device is CDMA and mine is GSM, you could brick your device totally.
Einwod said:
It won't work. If your device is CDMA and mine is GSM, you could brick your device totally.
Click to expand...
Click to collapse
Are you sure mine is cdma? There is GSM written at many places too.
redfaction95 said:
Are you sure mine is cdma? There is GSM written at many places too.
Click to expand...
Click to collapse
Sprint is CDMA. No doubt about it. The CDMA version M8 supports CDMA, GSM and HSPA, but not as many HSPA bands as the "pure" GSM M8 (basically any version except Sprint and Verizon).
What bands does your carrier use for 3G (HSPA)? I'm guessing that your carrier uses bands not supported by the Sprint version. In which case, you are out of luck. The Sprint (or Verizon) version is not recommended for anyone outside the US, and not on the specific (Sprint or Verizon) carrier.
You can't flash RUU, radio, or firmware from other versions to Sprint (even with s-off). As mentioned, the flash will either fail or brick the phone.
Einwod said:
It won't work. If your device is CDMA and mine is GSM, you could brick your device totally.
Click to expand...
Click to collapse
redpoint73 said:
Sprint is CDMA. No doubt about it. The CDMA version M8 supports CDMA, GSM and HSPA, but not as many HSPA bands as the "pure" GSM M8 (basically any version except Sprint and Verizon).
What bands does your carrier use for 3G (HSPA)? I'm guessing that your carrier uses bands not supported by the Sprint version. In which case, you are out of luck. The Sprint (or Verizon) version is not recommended for anyone outside the US, and not on the specific (Sprint or Verizon) carrier.
You can't flash RUU, radio, or firmware from other versions to Sprint (even with s-off). As mentioned, the flash will either fail or brick the phone.
Click to expand...
Click to collapse
I have changed my CID and MID. And btw can any one of you tell why the International version + Developer/Unlocked are still on 5.0.1 unlike the (my) Sprint version's 5.0.2 ...? Due to this issue, currently I am unable to flash any other lower (but international for 3G support) version of RUU exe regardless of me being on compatible CID/MID.
redfaction95 said:
I have changed my CID and MID. And btw can any one of you tell why the International version + Developer/Unlocked are still on 5.0.1 unlike the (my) Sprint version's 5.0.2 ...? Due to this issue, currently I am unable to flash any other lower (but international for 3G support) version of RUU exe regardless of me being on compatible CID/MID.
Click to expand...
Click to collapse
Never ever install an intl version/dev edition to your sprint device. It may brick it.
Where is your region currently ? Which country ?
Maybe change of these helps :
http://forum.xda-developers.com/showthread.php?t=2594804
ckpv5 said:
Never ever install an intl version/dev edition to your sprint device. It may brick it.
Where is your region currently ? Which country ?
Maybe change of these helps :
http://forum.xda-developers.com/showthread.php?t=2594804
Click to expand...
Click to collapse
I guess, it will not brick because I have changed my CID and MID according to the RUU version. Correct me if I am wrong?
I live in Asia, Pakistan.
ckpv5 said:
Never ever install an intl version/dev edition to your sprint device. It may brick it.
Where is your region currently ? Which country ?
Maybe change of these helps :
http://forum.xda-developers.com/showthread.php?t=2594804
Click to expand...
Click to collapse
What about the European version instead 4.16.401.10
while setting:-
CID: HTC__001
MID: 0P6B10000
redfaction95 said:
What about the European version instead 4.16.401.10
while setting:-
CID: HTC__001
MID: 0P6B10000
Click to expand...
Click to collapse
God almighty man, READ WHAT HE SAYS. You cannot and should not flash WWE anything on a Sprint device. What part of that do you NOT UNDERSTAND?
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!
Hello guys, I flashed CM13 (himaul GSM) to Chinese M9W (this is my first htc phone), and i thought it will work welll, but it didn't go well than i except. Now It doesn't recognize SIM card, IMEI number anymore. After that I realized I deleted 2 days ago TWRP backups of my M9W.
It's board number is himauhl. Same version as European M9. But with different CID, HTCCN_701.
I can't found suitable RUU to my HTC M9W with HTCCN_701 CID. I found but it was in Chinese, I couldn't understand anything so I am not sure it's cid suitable to mine. Link: http://htcui.com/8812.html
If you guys know how to find suitable rom (RUU) to this CID, I will appreciate to you guys. Thanks for reading.
I think you must wait for the ruu for your device and region.
Beamed in by telepathy.
shivadow said:
I think you must wait for the ruu for your device and region.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did a lot of research, and I learned all phones shipped with hima_uhl has got same motherboard (doesn't matter the region), including same Modem in SoC. So, I did S-OFF on USB with a guy who has special toolkit (he doesn't let me the see toolkit), It costs something like 10 Euro. I changed CID to HTC_M27 (Turkish CID), Installed European lollipop RUU and flashed International (hima_uhl) Modem via TWRP. Now it Works like a charm.
I hope this tutorial helps other people who have M9W and cannot able to find solution, BTW thanks for your answer
SchaubLoren said:
I did a lot of research, and I learned all phones shipped with hima_uhl has got same motherboard (doesn't matter the region), including same Modem in SoC. So, I did S-OFF on USB with a guy who has special toolkit (he doesn't let me the see toolkit), It costs something like 10 Euro. I changed CID to HTC_M27 (Turkish CID), Installed European lollipop RUU and flashed International (hima_uhl) Modem via TWRP. Now it Works like a charm.
I hope this tutorial helps other people who have M9W and cannot able to find solution, BTW thanks for your answer
Click to expand...
Click to collapse
I have the exact same problem. What is the international Modem?
math01141 said:
I have the exact same problem. What is the international Modem?
Click to expand...
Click to collapse
After you installed latest European RUU available with compatible CID, you need to mount all partitions and flash this file to get RIL functions working. Also after doing this you can also install European device compatible AOSP Roms.
Link: https://www.androidfilehost.com/?fid=24438995911968592
In my opinion set CID to 11111111 to bypass any soft bricks. I flashed with Turkish CID because my friend wanted to. I prefer using 11111111.
SchaubLoren said:
After you installed latest European RUU available with compatible CID, you need to mount all partitions and flash this file to get RIL functions working. Also after doing this you can also install European device compatible AOSP Roms.
Link: https://www.androidfilehost.com/?fid=24438995911968592
In my opinion set CID to 11111111 to bypass any soft bricks. I flashed with Turkish CID because my friend wanted to. I prefer using 11111111.
Click to expand...
Click to collapse
I now got 1111111.
Next step is flashing the european ruu? Can you give me a link for it?
By the way my phone don't recognize sim card because its locked to sprint, this will override my problem? And the phone will no brick?
math01141 said:
I now got 1111111.
Next step is flashing the european ruu? Can you give me a link for it?
By the way my phone don't recognize sim card because its locked to sprint, this will override my problem? And the phone will no brick?
Click to expand...
Click to collapse
dude i really have no idea about sim locked one, i only know this is the guarantee solution for region problems.
http://forum.xda-developers.com/sprint-one-m9/general/nv-unlock-sim-t3314755 maybe try this=?
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
Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
Click to expand...
Click to collapse
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
computerslayer said:
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
Click to expand...
Click to collapse
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Access point names. Change it to what you carrier uses or get them to send it to your phone.
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Click to expand...
Click to collapse
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
shivadow said:
Access point names. Change it to what you carrier uses or get them to send it to your phone.
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
Click to expand...
Click to collapse
I've changed the apn but still the same. I will try flashing nougat based firmware and then give u my feedback. U have any link for the firmware?
abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100.
Click to expand...
Click to collapse
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition.
Click to expand...
Click to collapse
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
abdinsyakirin said:
U have any link for the firmware?
Click to expand...
Click to collapse
Did Verizon already release the android N update? I haven't heard of it, yet.
shivadow said:
If you flash a nougat based rom over marshmallow it wont boot.
Click to expand...
Click to collapse
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Yes i just know that my phone is an international version. Before this i thought it was verizon m9. Verizon did not release any nougat based firmware. But i think there is international version of nougat available
For the marshmallow to nougat question, i encountered some issues with the other rom. Some roms doesnt boot up and some others stuck on setup wizard since wifi cannot be enable.
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
abdinsyakirin said:
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
Click to expand...
Click to collapse
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Flippy498 said:
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Click to expand...
Click to collapse
My phone has SuperCID. Based on download mode, the OS- 3.37.605.13. Model ID 0PJA100 as stated before. I think the OS version is vzw not wwe since i flashed the vzw before. Actually, I bricked this device after i had my "mobile data disconnected" problem and asked somebody to help me fix it, and he flashed that firmware version (it is my fault since i thought this phone is verizon m9).
So, should I fully flash the wwe 3.35 firmware? Or what?
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Oh yes the MID changed to 0PJA30000, sorry for my last reply, that one i referred to the back engraving of m9. Im gonna change the CID and flash the firmware version u talked about. I will give you an update once I done it.
Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I dont get any mobile network, even worse than before. I flashed 3.35.401.12 like u told so. Do i need to flash it manually by extracting the folder and flash all the img inside it independently? If u have any suggestion let me know.
UPDATE: Actually i dont think the problem is with verizon firmware since I had the problem after I flashed ICE nougat rom (I came from SDreamTeam Sense8 rom). After that I bricked the device and told other person to help me flash vzw firmware because I thought it was verizon m9. This problem is very weird and i dont know how to relate the ICE rom with my current problem. OP of ICE rom said the rom not compatible with verizon m9 but since this phone is not verizon m9, i dont think there should be a problem right?
The RUU needs to get flashed via the SD card method that is described in the ReadMe thread.
As written there and in some of my posts in this thread, GSM devices and CDMA firmware (or vice versa) aren't compatible with each other due to the different partition layouts. Therefore, cross-flashing can lead to unrecoverable damages.
I can't tell you what happened while you've been using ICE and therefore I can't tell you whether your phone had been in a recoverable state at that time. However, chances are high that flashing a Verizon RUU instead of the correct GSM RUU was the nail in the coffin of your phone. Sorry, that I don't have better news.
Edit: Oh, and please remove the quote from your last post. It's not necessary to quote me every time you post here.
Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Exactly that, it's not worth the risk seeing as many people have reported that their phone won't boot after mismatching roms to base firmware. Updating to a nougat custom rom to a marshmallow firmware would be bad as the api's are completely different and would explain the non booting situation.
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Beamed in by telepathy.
shivadow said:
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Click to expand...
Click to collapse
Re-read what I posted. I never said that it would be "100% safe" *. Of course there'll be problems due to the mismatch. I was only asking whether there have been reports about bootloops. (Btw, Android n and Android m don't differ as much as Android m and Android l did.) And according to this post the brick didn't happen directly after flashing the nougat rom.
However, I searched through the dev section yesterday and according to the Viper thread and the 4.x TWRP Backup thread people have been able to boot nougat roms on Android m. A lot of them faced problems. E.g. I have read about many user who used the old firmware and faced overheating and/or battery drain problems in the backup thread. They all needed to root their rom for getting rid of the problems. (Altough I personally can't explain why SuperSU should be able to fix those problems...) It seems like users with the newer firmware on the other hand don't necessarily have to face these issues. Take my phone as an example. It's running just fine without any heat and/or battery problems.
* Although I think that the usage of "safe" might imply that flashing a rom might damage your phone and that's not the case. The worst things that can happen are a bootloop or if the rom is booting fine some lags/bugs. Only flashing an incompatible firmware (via a RUU or a firmware pack) leads to damages.
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Since u didn't reply, i assume my device now damaged unrecoverably right?
EDIT: SORRY, I DID NOT GET ANY NOTIFICATION AND DONT READ THIS FORUM. VERY SORRY MY BAD. I AM VERY NEWBIE IN THIS KIND OF THINK.
Flippy498 said:
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Again sorry for my previous quote just now. Yes i read that q&a section and i did not have any of the problem except no mobile internet data. I can receive and make a phone call. Only mobile internet data. I am from 3.35 firmware if i am not mistaken since there was no official update after I purchased the phone. But NOW, I faced the problem after flashed GSM RUU. I do it twice, through exe and sdcard method. I also changed my CID and MID as u told me to.
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
So if i can find my original firmware version, i can solve this problem (if the verizon does not damage it) by flashing that version on my phone right? The only thing that I remember on my phone after i bought it is, it does not have any bloatware such as kid mode app, and when i clicked on software update, it said "please connect to XXXX to check an update" or something like that. XXXX referred to service provider in usa but i dont remember what company it was. I think there are still hope to recover this device.
I don't think that we can recover the phone even if we knew it's original firmware. That's why they're called "unrecoverable" damages.
For a GSM M9 it doesn't matter which RUU you flash (as long as it isn't a CDMA RUU). So if one GSM RUU didn't fix the situation then a different one won't be able to do so, either. And that's the reason why the ReadMe thread warns everybody not to cross-flash firmware files.
That part of my last post you're referring to was an explanation why I think that you faced problems with ICE. It has nothing to do with your current situation.
Sent from my HTC One M9 using XDA Labs