Related
Hey so I had converted my M8 to GPe but am now selling it so I'm putting it back to Sense. Everything's working except for the wifi which I had issues with in the past from not flashing the Telus firmware.zip again from a 4.4.4 OTA file. At this link http://d-h.st/BfV the OTA file is there but there's only two fake looking download buttons that Chrome says both are malicious. One downloads an .exe and the other gets outright blocked. Can anyone help me out with finding the OTA file for Telus?
Thanks, I'm selling the phone in a few hours and am freaking as the wifi doesn't currently work! :/
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Hendrycks said:
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Click to expand...
Click to collapse
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Seanie280672 said:
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Click to expand...
Click to collapse
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Hendrycks said:
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Click to expand...
Click to collapse
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Seanie280672 said:
first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts.
Click to expand...
Click to collapse
Sometimes is a full package, sometimes its not. You're right, that sometimes if not all modules were updated (from the preceding OTA) typically its not a full package (only includes the parts that were updated).
Flashing firmware zips without knowing exactly what you are doing is really dangerous. I've seen folks flash a "partial" firmware, that didn't contain all the bootloader modules; only 2 of the 3, and the one that wasn't updated didn't correspond to the 2 that were. BRICK
Seanie280672 said:
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Click to expand...
Click to collapse
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Hendrycks said:
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Click to expand...
Click to collapse
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Seanie280672 said:
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Click to expand...
Click to collapse
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Hendrycks said:
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Click to expand...
Click to collapse
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Seanie280672 said:
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Click to expand...
Click to collapse
If the RUU was an .exe how can I edit it?
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Hendrycks said:
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Click to expand...
Click to collapse
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Seanie280672 said:
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Click to expand...
Click to collapse
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Hendrycks said:
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Click to expand...
Click to collapse
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Seanie280672 said:
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Click to expand...
Click to collapse
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Hendrycks said:
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Click to expand...
Click to collapse
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Seanie280672 said:
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Click to expand...
Click to collapse
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Hendrycks said:
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Click to expand...
Click to collapse
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Seanie280672 said:
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Click to expand...
Click to collapse
Sounds good thanks
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Bricked mine too!
RuminatorNZ said:
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Click to expand...
Click to collapse
I just joined this forum, so I don't know if I should be posting here or on a new thread, so let me know I can delete this, move it if I'm out of line.
I'm in the same boat. Just softbricked my girlfriend's Samsung Galaxy S5 (SM-G900a)
Her phone was unlocked AT&T and it auto updated to 5.0 Lollipop update OTA about a week ago.
It's been running like **** so I thought I'd downgrade it to 4.2.2 via ODIN
ODIN (failed) trying to install
G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.gz
I read in one of these forums that downgrading wouldn't work but they found a work around
http://forum.xda-developers.com/showthread.php?t=2785363
Oh yeah and then my phone bricked so there is that, my GF is being really understanding but I'm hoping I can recover this!!!!
Edit: My problem was resolved here
http://forum.xda-developers.com/att...-2-bricked-t3093826/post60397413#post60397413
RuminatorNZ said:
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Click to expand...
Click to collapse
your mistake is using CWM recovery, Sense custom roms require TWRP recovery, so you need to start by flashing the latest version of that.
once flashed, go in and do a full wipe. dont forget after wiping to reboot back into recovery for the changes to take effect, when you go to reboot it will say something like you have no OS installed, are you sure you want to reboot, just say yes, and select DO NOT INSTALL to SuperSU, the rom you falsh will be pre rooted.
TWRP latest version supports MTP, so when your in recovery main window, plug your phone into the computer and your sdcard and internal storage will open on your computer, just copy a rom to your sdcard, once copied, unplug your phone and install it.
use something like ARHD 41 or Maximus HD, they are close enough to stock for sunshine to work.
have a look here for a rom, dont download anything too modded or fancy as you'll be coming away from stock then http://forum.xda-developers.com/htc-one-m8/development
Seanie280672 said:
your mistake is using CWM recovery, Sense custom roms require TWRP recovery, so you need to start by flashing the latest version of that.
once flashed, go in and do a full wipe. dont forget after wiping to reboot back into recovery for the changes to take effect, when you go to reboot it will say something like you have no OS installed, are you sure you want to reboot, just say yes, and select DO NOT INSTALL to SuperSU, the rom you falsh will be pre rooted.
TWRP latest version supports MTP, so when your in recovery main window, plug your phone into the computer and your sdcard and internal storage will open on your computer, just copy a rom to your sdcard, once copied, unplug your phone and install it.
use something like ARHD 41 or Maximus HD, they are close enough to stock for sunshine to work.
have a look here for a rom, dont download anything too modded or fancy as you'll be coming away from stock then http://forum.xda-developers.com/htc-one-m8/development
Click to expand...
Click to collapse
Brilliant, thank you - I'll give this a whirl.
RuminatorNZ said:
Brilliant, thank you - I'll give this a whirl.
Click to expand...
Click to collapse
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Seanie280672 said:
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Click to expand...
Click to collapse
I sure can (thank you for your help):
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__039
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
RuminatorNZ said:
I sure can (thank you for your help):
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__039
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
your going to need s-off and convert your phone im sorry, doesnt seem to be anything about for your phone, firmware or RUU's.
You'll need to convert to get the latest firmware on your phone, unless you have it via an OTA or something like that ? convert to WWE 401 or Dev Edition 1540, currently your on 980 Austraillia Unbranded.
once you get s-off, convert is easy, all you need to do is change your CID number with a fastboot command, change your MID number, flash the firmware for Dev Ed or WWE, and then run the RUU.
Seanie280672 said:
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Click to expand...
Click to collapse
I've got a sneaking suspicion that the ARHD and Maximus ROMS I'm finding won't mesh with the firmware I've got. I think.
Seanie280672 said:
your going to need s-off and convert your phone im sorry, doesnt seem to be anything about for your phone, firmware or RUU's.
You'll need to convert to get the latest firmware on your phone, unless you have it via an OTA or something like that ? convert to WWE 401 or Dev Edition 1540, currently your on 980 Austraillia Unbranded.
once you get s-off, convert is easy, all you need to do is change your CID number with a fastboot command, change your MID number, flash the firmware for Dev Ed or WWE, and then run the RUU.
Click to expand...
Click to collapse
yeah it's getting S-Off that struggling with.
RuminatorNZ said:
I've got a sneaking suspicion that the ARHD and Maximus ROMS I'm finding won't mesh with the firmware I've got. I think.
Click to expand...
Click to collapse
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its stock for your firmware version, https://www.androidfilehost.com/?fid=95916177934516545
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Seanie280672 said:
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its an older version of ARHD http://www.androidrevolution.org/do...oid_Revolution_HD-One_M8_34.6.zip&hash=3703c7
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Click to expand...
Click to collapse
Right, off I go to download these files on New Zealand's rubbish internet. I'll report back in many many hours
Thank you for all your help so far. Really appreciate it.
RuminatorNZ said:
Right, off I go to download these files on New Zealand's rubbish internet. I'll report back in many many hours
Thank you for all your help so far. Really appreciate it.
Click to expand...
Click to collapse
use this rom instead: https://www.androidfilehost.com/?fid=95916177934516545 its full stock rom, flash in TWRP still, and closest matching to your firmware, its KitKat not Lollipop.
Seanie280672 said:
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its stock for your firmware version, https://www.androidfilehost.com/?fid=95916177934516545
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Click to expand...
Click to collapse
Just keeping you updated, finished dowloading the above rom, flashed it and it seems to be working (mind you, my wifi still ain't working with that ROM, but I can live with that). Sunshine is now S-Off-ing as we speak so this is as much progress as I've made in 2 days!!
What should my next step be after getting S-Off?
RuminatorNZ said:
Just keeping you updated, finished dowloading the above rom, flashed it and it seems to be working (mind you, my wifi still ain't working with that ROM, but I can live with that). Sunshine is now S-Off-ing as we speak so this is as much progress as I've made in 2 days!!
What should my next step be after getting S-Off?
Click to expand...
Click to collapse
easiest thing for you to do is change your cid first, change it to WWE HTC__001 the command is fastboot oem write cid HTC__001 (thats 2 underscores, CID number is always 8 characters long)
so with your phone in the bootloader fastboot usb mode and plugged into the computer, run these3 commands
fastboot oem write cid HTC__001
fastboot erase cache
fastboot reboot-bootloader
next is to change you mid, so enter recovery and put this file on your SDcard http://forum.xda-developers.com/showthread.php?t=2779524
install it like you would with a rom, and follow the instructions on screen, when given the options to select mid to change to, select the one for WWE international.
when you have finished those 2 things, post your fastboot getvar all again please, should be a new and updated one, again without imei and serial number
Seanie280672 said:
easiest thing for you to do is change your cid first, change it to WWE HTC__001 the command is fastboot oem write cid HTC__001 (thats 2 underscores, CID number is always 8 characters long)
so with your phone in the bootloader fastboot usb mode and plugged into the computer, run these3 commands
fastboot oem write cid HTC__001
fastboot erase cache
fastboot reboot-bootloader
next is to change you mid, so enter recovery and put this file on your SDcard http://forum.xda-developers.com/showthread.php?t=2779524
install it like you would with a rom, and follow the instructions on screen, when given the options to select mid to change to, select the one for WWE international.
when you have finished those 2 things, post your fastboot getvar all again please, should be a new and updated one, again without imei and serial number
Click to expand...
Click to collapse
Is what you've suggested better than the Super-CID - 11111111 ?
RuminatorNZ said:
Is what you've suggested better than the Super-CID - 11111111 ?
Click to expand...
Click to collapse
I never bother with superCID, always seems to cause me more headaches than good.
the 2 best cid's to go for in my books are HTC__001 WWE (world wide engish) or BS_US001 Dev edition, they get the fastest updates.
Seanie280672 said:
I never bother with superCID, always seems to cause me more headaches than good.
the 2 best cid's to go for in my books are HTC__001 WWE (world wide engish) or BS_US001 Dev edition, they get the fastest updates.
Click to expand...
Click to collapse
Brilliant. I'll take your advice. You've got it all right so far.
See this guiy here did the same thing, but he is complaining that he's not got the next update yet, it because he hasnt changed his cid number, he needs to be on HTC__001, everytrhing else is done right, this is from the Australlian thread: http://forum.xda-developers.com/showpost.php?p=60272806&postcount=662
your fastboot getvar all should look like his when your done, only yours should say HTC__001 for the cid.
---------- Post added at 11:50 AM ---------- Previous post was at 11:42 AM ----------
RuminatorNZ said:
Brilliant. I'll take your advice. You've got it all right so far.
Click to expand...
Click to collapse
sorry my bad, no space between wite and cid so the command is fastboot oem writecid HTC__001
Seanie280672 said:
See this guiy here did the same thing, but he is complaining that he's not got the next update yet, it because he hasnt changed his cid number, he needs to be on HTC__001, everytrhing else is done right, this is from the Australlian thread: http://forum.xda-developers.com/showpost.php?p=60272806&postcount=662
your fastboot getvar all should look like his when your done, only yours should say HTC__001 for the cid.
---------- Post added at 11:50 AM ---------- Previous post was at 11:42 AM ----------
sorry my bad, no space between wite and cid so the command is fastboot oem writecid HTC__001
Click to expand...
Click to collapse
Righto, so far so good ... I think:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
RuminatorNZ said:
Righto, so far so good ... I think:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
just MID to change, just wondering, have you flashed some firmware ??? how did you get on this 4.16.1540.8 ??? this is dev edition firmware.
Hi there I am new to HTC this is my firs HTC phone. I have HTC one m8 device with android 4.4.4 kit Kat and I want to update it to android 5 lollipop . when I go to settings and checking for updates it says (your phone is up to date there are no updates available for your phone ) I also tried HTC sync manger but with no luck so far .
So why there is no updates for my phone ?? ( I am not rooted or unlocked the boot loader)
Any way to download the Rom and install it via pc ?? (Program like Odin To install roms to htc ).
I am sorry for the bad English language because it's not my nature language .
kirkuk said:
Hi there I am new to HTC this is my firs HTC phone. I have HTC one m8 device with android 4.4.4 kit Kat and I want to update it to android 5 lollipop . when I go to settings and checking for updates it says (your phone is up to date there are no updates available for your phone ) I also tried HTC sync manger but with no luck so far .
So why there is no updates for my phone ?? ( I am not rooted or unlocked the boot loader)
Any way to download the Rom and install it via pc ?? (Program like Odin To install roms to htc ).
I am sorry for the bad English language because it's not my nature language .
Click to expand...
Click to collapse
Post the results of fastboot getvar all Delete the serial# and IMEI from the output. That is private information.
There may be an RUU that you could run to update, and your getvar will give the information that is needed to determine that.
xunholyx said:
Post the results of fastboot getvar all Delete the serial# and IMEI from the output. That is private information.
There may be an RUU that you could run to update, and your getvar will give the information that is needed to determine that.
Click to expand...
Click to collapse
thank you bro for replay i appreciate that ....
this the result of ( fastboot getvar all ) .
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.36.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
kirkuk said:
thank you bro for replay i appreciate that ....
this the result of ( fastboot getvar all ) .
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.36.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
I'm not sure that Lollipop is even available for the Middle East/Egyptian model. Your best bet would be to spend $25 for Sunshine S-Off, convert to superCID, and update with WWE/International firmware. You could also try to change your MID to 0P6B10000 and update that way, but there is a very real risk of bricking if you do that.
---------- Post added at 07:48 PM ---------- Previous post was at 07:22 PM ----------
You could also try this. No guarantees that it will work, but it might (your CID is listed as compatible, but the MID makes me wonder). You won't brick, you will just get error ouputs if it doesn't
Download this RUU.zip
Rename it to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your extSD.
Boot into bootloader and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash, power button to reboot)
That's it.
After you are done make sure to delete the renamed file from your SD card, otherwise every time you boot to bootloader it will try tro update again.
Good luck!
xunholyx said:
I'm not sure that Lollipop is even available for the Middle East/Egyptian model. Your best bet would be to spend $25 for Sunshine S-Off, convert to superCID, and update with WWE/International firmware. You could also try to change your MID to 0P6B10000 and update that way, but there is a very real risk of bricking if you do that.
---------- Post added at 07:48 PM ---------- Previous post was at 07:22 PM ----------
You could also try this. No guarantees that it will work, but it might (your CID is listed as compatible, but the MID makes me wonder). You won't brick, you will just get error ouputs if it doesn't
Download this RUU.zip
Rename it to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your extSD.
Boot into bootloader and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash, power button to reboot)
That's it.
After you are done make sure to delete the renamed file from your SD card, otherwise every time you boot to bootloader it will try tro update again.
Good luck!
Click to expand...
Click to collapse
thank you so much bro .
i will try that RUU and see if it worked and let you know. but i have a few questions .
1-do you think that update will effect on the radio or IMEI number ??
2-do i receive updates in the future ??
thanks again for helping me .
kirkuk said:
thank you so much bro .
i will try that RUU and see if it worked and let you know. but i have a few questions .
1-do you think that update will effect on the radio or IMEI number ??
2-do i receive updates in the future ??
thanks again for helping me .
Click to expand...
Click to collapse
Your radio version is the same as mine, and I'm on WWE so there is nothing to worry about there. You won't receive OTA updates MID. You can still update via RUU when the next version comes out, or you can get S-Off and just flash the firmware. I should have already let you know; and I am sorry that I forgot to mention it; but the RUU will wipe your phone so make sure you backup everything that is important to you. Make a backup to your extSD. That won't get wiped.
xunholyx said:
Your radio version is the same as mine, and I'm on WWE so there is nothing to worry about there. You won't receive OTA updates MID. You can still update via RUU when the next version comes out, or you can get S-Off and just flash the firmware. I should have already let you know; and I am sorry that I forgot to mention it; but the RUU will wipe your phone so make sure you backup everything that is important to you. Make a backup to your extSD. That won't get wiped.
Click to expand...
Click to collapse
a very big thanks to you bro i bothered you with my problem and questions and appreciate every word you wrote .it is ok that you didnot mentioned it will wipe my phone because i backed it up before .
xunholyx said:
Your radio version is the same as mine, and I'm on WWE so there is nothing to worry about there. You won't receive OTA updates MID. You can still update via RUU when the next version comes out, or you can get S-Off and just flash the firmware. I should have already let you know; and I am sorry that I forgot to mention it; but the RUU will wipe your phone so make sure you backup everything that is important to you. Make a backup to your extSD. That won't get wiped.
Click to expand...
Click to collapse
Hi. I don't mean to hijack this post or whatever but I have the same problem with the same MID and CID. I bought the phone from Riyadh and I am not receiving any OTA. I tried that RUU and it failed giving me the following error:
Code:
Model ID incorrect!
Update Fail!
Device halted due to Large Image update fail!
Press <POWER> to reboot.
EDIT: I did get the Stagefright fix by OTA if that helps somehow.
muftiazan said:
Hi. I don't mean to hijack this post or whatever but I have the same problem with the same MID and CID. I bought the phone from Riyadh and I am not receiving any OTA. I tried that RUU and it failed giving me the following error:
Code:
Model ID incorrect!
Update Fail!
Device halted due to Large Image update fail!
Press <POWER> to reboot.
EDIT: I did get the Stagefright fix by OTA if that helps somehow.
Click to expand...
Click to collapse
Yeah, I had a feeling that might happen.
xunholyx said:
Yeah, I had a feeling that might happen.
Click to expand...
Click to collapse
if i got same error did my phone will start as nothing happend and boots normal or i have to install new rom ??
kirkuk said:
if i got same error did my phone will start as nothing happend and boots normal or i have to install new rom ??
Click to expand...
Click to collapse
It'll boot up fine. Don't worry.
xunholyx said:
It'll boot up fine. Don't worry.
Click to expand...
Click to collapse
bro its failed and i got the same error as mentioned above . my device boot normal.thank you.
I hava the same problem. The Ruu you just provided was from the htc official rom downloads page right?
And, will this model effect the custom roms to be flashed?like would i be able to flash arhd on it (the same mid as OP and unlocked) without bricking it?
I thought samsung's variantd were insane but htc is driving me nuts ?
eatsleep said:
I hava the same problem. The Ruu you just provided was from the htc official rom downloads page right?
And, will this model effect the custom roms to be flashed?like would i be able to flash arhd on it (the same mid as OP and unlocked) without bricking it?
I thought samsung's variantd were insane but htc is driving me nuts ��
Click to expand...
Click to collapse
bro i am new to htc so i donot know much about htc and installing roms because i switched from samsung to htc . i think that RUU was official from htc but its failed to install on my htc one m8 because my device is made for middle east .i donot know if you can install it on your device or install custom roms on it .
eatsleep said:
I hava the same problem. The Ruu you just provided was from the htc official rom downloads page right?
And, will this model effect the custom roms to be flashed?like would i be able to flash arhd on it (the same mid as OP and unlocked) without bricking it?
I thought samsung's variantd were insane but htc is driving me nuts ��
Click to expand...
Click to collapse
It's a zip made from the official RUU.
It won't affect which ROMs you can flash.
If you have the same model as the OP, it won't work. You will need to get S-Off and change your MID first.
xunholyx said:
It'll boot up fine. Don't worry.
Click to expand...
Click to collapse
sorry bro for bothering you but is it safe to try this RUU
http://www.htc.com/us/support/htc-one-m8/news/
from htc website to update my phone ?? what happens if it fail to update ??
Hi there ...i have recived official OTA update android (5.0.2) in 11/26/2015 . Thanks to all of you .
kirkuk said:
sorry bro for bothering you but is it safe to try this RUU
http://www.htc.com/us/support/htc-one-m8/news/
from htc website to update my phone ?? what happens if it fail to update ??
Click to expand...
Click to collapse
I see you issue solved itself. But just FYI, the above RUU would not have worked on your phone. You can't just run any RUU, it needs to match your carrier ID (CID) and model ID (MID). You can change CID and MID, but only with s-off.
redpoint73 said:
I see you issue solved itself. But just FYI, the above RUU would not have worked on your phone. You can't just run any RUU, it needs to match your carrier ID (CID) and model ID (MID). You can change CID and MID, but only with s-off.
Click to expand...
Click to collapse
thank u for sharing us your experience .. the above RUU did not installed on my phone for the reasons that you wrote above ..i will try change the CID and MID to change my phone to GPE in the future if my phone not received the marshmallow update ...
i want 3.36.401.4 stock recovery my phone is rooted and i have the ota update so my phone is not updating
Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.
ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.
Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.
You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.
hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip
ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1
ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same
alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan
alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14