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
Related
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.
I have Htc one m8 unlocked bootloader 3.19, was rooted but doesn't seem to be anymore. firmware is 4.16.401.10, supercid (was roger001). I'm not sure what I am doing wrong, I tried to flash a RUU after flashing the firmware first and i get an error 32-header error. Phone just reboots onto white HTC screen then gives me the red exclamation mark. Booting into recovery gives red exclamation mark. Not sure what else I can try, any suggestioins would be greatly appreciated. (note: tried to flash the RUU here I could be way off but I am stuck.)
Anyone have any assistance? I tried changed the mid so I could flash a RUU but still got the 32-header error. There has to be a simpler way to do this, I just want to get back to stock.
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong. I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work. I'll post that info in one sec
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Kevinj17 said:
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong.
Click to expand...
Click to collapse
Yes, that is incorrect. CID and MID need to match what the RUU is looking for. SuperCID will pass the CID check. But the MID check will still fail if you try to run the Euro RUU (MID = 06PB10000) on a Rogers version M8 (MID = 06PB16000).
Also, are you actually using the phone on Rogers' network? If so, I do not think that returning to stock Euro WWE version by RUU is what you want. From this webpage, it looks like Rogers uses Bands 4,7, and 17 for LTE. The Euro RUU will install a full stock image, including radio firmware, and according to these specs, the Euro version (EMEA) is missing 2 of the 3 bands (Bands 4 and 17) needed for LTE to work on Rogers network.
Kevinj17 said:
I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work.
Click to expand...
Click to collapse
What zip did you try to flash exactly?
---------- Post added at 09:41 AM ---------- Previous post was at 09:23 AM ----------
Kevinj17 said:
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Click to expand...
Click to collapse
That would just be the actual stock recovery program that installs of OTA updates, etc.
Its not the actual stock OS or firmware, if that is what you are thinking.
The red exclamation indicates you are already on a stock recovery. Flashing this won't help you at all.
Yeah haha I figured that out right after posting. Thanks though. I re-flashed TWRP now and gonna try restoring from a nandrod backup i found then flash the matching firmware. see how that goes. The similiar names is what throws me off sometimes, so many different recoverys n sh*t lol
I was tryign to use a sixaxis controller to play games but kept getting and error about 'position executable variables' when loading the sixaxis app so i downloaded something called 'bypass pie' and flashed it. Clearly i should have backed up first. It was just inpatient, but it unrooted my phone and stuff so i tried to restore from a backuop like 2 weeks ago and it was corrupt so it messed things up
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
pauluthupm said:
I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Click to expand...
Click to collapse
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Solved : Unbrick HTC M* - Revert to Stock
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
Thank you for the help. fortunately i did find the solution. just the way u said only. I was in office and dint have access to xda in office. Let me also put what i have done.
pauluthupm said:
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
Click to expand...
Click to collapse
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Make sure u download the htc fastboot files: Google is ur friend.
Place the image in the same folder as the htc fastboot files are.
rename the file to 0P6BIMG.zip( remember not to add two zips at the end.,windows generally hides the extension
Now open ur command prompt.
naviagate to the htc fastboot folder , i my case, i put in c drive
so it would like c:\htc_fastboot_files
Now Voulme Down Button and then press the power button.
In my case i had to use Power+Volume up to reboot the phone . And the moment it rebooted i pressed just the vol down button.
So we would be in Bootloader. Now switch phone to fastboot mode.
Navigate using volume buttons and power button to enter.
in fast boot mode
bring up ur command prompt:
We are already in the fastboot file folder. like i mentioned before: c:\htc_fastboot_files
type fastboot get var all
look for this info: (bootloader) version-main: 6.12.401.4 ( This might be different case to case, according to this you can search for relevant ruu, just google with the version number firmware)
Now htc_fastboot oem lock ( To relock the bootloader)
htc_fastboot oem rebootRUU
htc_fastboot flash zip Firmware_xx.zip ( in my case its 0P6BIMG.zip)
Once the flash completes, you will have a window which says Flash complete. OKAY. Mind you it takes some time.
After this,
htc_fastboot reboot . Thats it. Phone will take quite some time to reboot and complete the process.
My phone was up and running from here. But in case of errors. You might want look down.
IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (don’t use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot (below this section you find CRITICAL errors, please observe):
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 24 android-info fail (means something wrong with android-info.txt in the zip)
- 32 header error (means the zip couldn't be read and unzipped properly)
- 41 Wrong Model ID (means it's not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap CID first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot in-between).
- 99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues.
- 130 wrong model ID (seems it's the same like 41, just that it shows in the FUU as 130.
- 155 seems to indicate different things. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match.
- 170 Check USB - FUU won’t run because of not working ADB.
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 24 "android-info fail" do:
- check that your ZIP isn’t some HTC OTA or anything thats got no android-info.txt - those cannot be flashed with fastboot flash zip nameof.zip command.
- check that your zip has a good MD5 and is not broken, check android-info.txt etc...
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn't help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
htc_fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
htc_fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn't brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definitely this means the ZIP is not signed - get an unmodified zip!
For “Error 130 wrong model ID" do:
- Please refer to Error Code 41/42.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn't work well currently.
NOT safe to reboot / Flash (partly) happened Errors (if you encounter one of them, DON’T reboot:
- 152 Image Error - Phone Screen shows a little triangle beside a full green bar
For “Error 152 Image Error" do:
- Error 152 is quite rare, have seen it only once with a friend’s phone and it aborted the flash nearly at the end. The flash was started by the FUU. We could resolve the matter by NOT rebooting the phone and flashing the zip again through a manual fastboot flash as outlined further up.
pauluthupm said:
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
redpoint73 said:
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
Click to expand...
Click to collapse
Yep. That's straight up stolen (copy/pasted) from @Sneakyghost's threads.
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
xunholyx said:
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
Click to expand...
Click to collapse
Yeah, hard to tell what OP is talking about, if they don't even get the name right.
Also completely unnecessary of him to clutter up the board by copy and pasting huge amounts of text when a link can be provided (or refer to a thread, if he can't link).
NEW HTC m8 on custom recovery
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
--------------------------------------------------------------
Hi redpoint, need your help.
i want to revert my htc m8 to stock marshmallow. i am currently running ,mi ui with twrp recovery.
i am posting getvar results below. i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? can u help me with which firm ware i should download and which stock recovery should i install ?
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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
pauluthupm said:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
What's going on here, is this a different phone than what you listed in the first post?
pauluthupm said:
i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Click to expand...
Click to collapse
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
pauluthupm said:
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? 0
Click to expand...
Click to collapse
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
m8 revert to stock
redpoint73 said:
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
Click to expand...
Click to collapse
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
My device id belongs to India when i googled hence i m searching for these ruu. I wanted to try sunshine s off so that change the mid and cid to eu version and then try different ruu. Sunshine keeps giving me an error while running the initial tests it requires an non debuggable boot.img. So that doesnt help either.
do you require anymore info ? i can give u remote access if it requires.
PS: MIUI Rom is still working if i want to use my phone
pauluthupm said:
do you require anymore info ? i can give u remote access if it requires.
Click to expand...
Click to collapse
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
I had answered to your questions right below it. Did u mean i dint answer with details?
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
i have No clue how i found it. I googled lot of pages and somehow i found this this link. butyes i downloaded it from http://forum.gsmhosting.com/vbb/f48...-ruu-4-x-x-6-x-x-updated-19-3-2016-a-1940130/
I am not sure its signed or not. to be honest i have no clue.
answers to what you had asked?
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
Originally Posted by redpoint73
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
pauluthupm said:
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery.
Click to expand...
Click to collapse
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
pauluthupm said:
Now i tried flashing that ruu downloaded from gsm developers. but i failed with it.
Click to expand...
Click to collapse
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
How big is the file (MB)?
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
pauluthupm said:
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
Click to expand...
Click to collapse
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.720.xx specifically refer to your version M8 (CID and MID).
EDIT: fixed a typo, the number in red in the last line should read 720.
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
redpoint73 said:
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
HTML:
[QUOTE]Yes i renamed it to 0P6BIMG.zip
[/QUOTE]
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
remote: 12 signature verify fail)
Execution time is 115(s)
Click to expand...
Click to collapse
How big is the file (MB)?
1.66 GB
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.709.xx specifically refer to your version M8 (CID and MID).
Click to expand...
Click to collapse
Can you help me with the link i should download ? the correct ruu for my m8 ?
i can post the getvar values here if its of any help.
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
pauluthupm said:
Yes i renamed it to 0P6BIMG.zip
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
Click to expand...
Click to collapse
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
redpoint73 said:
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Bootloader is currently unlocked. Since you said i can run ruu in custom recovery also. I went and reinstalled custom recovery twrp 2.7 from Hasoons All in one Kit.
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
Click to expand...
Click to collapse
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
Click to expand...
Click to collapse
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
htc_fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
Click to expand...
Click to collapse
pauluthupm said:
Being very honest, i have very little knowledge, its a new learning for me.
Click to expand...
Click to collapse
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
pauluthupm said:
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Click to expand...
Click to collapse
It won't work. You need version numbers with 720, not 709.
I see in my last post, I said you needed 720 (which is correct) then a typo which implies you need 709 (not correct). So there may have been some confusion or conflicting info there.
Also, that version is too old (software number 1.54). You can only run RUU with equal or greater version than the firmware on the phone, which in your case is 4.xx.
pauluthupm said:
]
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
Click to expand...
Click to collapse
RELOCKED is the important part. Not sure why you got in error , but it looks to be properly relocked to run RUU.
Was it RELOCKED or UNLOCKED when you tried the RUU 6.20.709.2 and got Error 12: Signature Error?
redpoint73 said:
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
I should have. Now i regret for messing up the phone
Click to expand...
Click to collapse
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Absolutely learned it. I wouldnt want mod any phones anymore. Too much of headache, since am i am noob.
Click to expand...
Click to collapse
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
Click to expand...
Click to collapse
In fact i did have twrp back up. bt i had kept this sd card in my wallet. I broke the sd card by mistake. thats how i lost it.
OP cannot install RUU 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2 on his current firmware version.
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038He needs to install the signed 6.15.720.2 firmware first before install the RUU zip
Easier method is - install RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe
Download from : http://androidruu.com/?developer=M8
then OTA to 4.18.720.10 then later to 6.15.720.2
Or restore 4.18.720.10 backup & install 4.18.720.10 stock recovery (yeah .. skip a version) then OTA to 6.15.720.2
Download from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck
Hello everyone,
I just bought this used HTC M8. It has android version 4.3.3 and software version 2.22.401.5
If I use "Get Var All" function I get that my mobile Model Id is PB0613000 and CID is 1111111
I cannot update OTA. I cannot install Rom manually cause it gives error 155.
My bootloader is locked and S-OFF too.
I have no idea how to install ROM in it and what Rom. I have used unlocked official rom and also the one T-Mobile released officially, Both gave error 155.
Please help me.
Thank you.
If you want to install either Dev Ed or T-Mob 6.xx RUU, you need to flash its firmware first.
e.g. to install 6.20.531.5 RUU, you must flash 6.20.531.5 firmware.zip first.
ckpv5 said:
If you want to install either Dev Ed or T-Mob 6.xx RUU, you need to flash its firmware first.
e.g. to install 6.20.531.5 RUU, you must flash 6.20.531.5 firmware.zip first.
Click to expand...
Click to collapse
Hey thanks for letting me know. I am trying to install 6.12.1540.14 on my HTC DEVed.
I changed my MID and CID and installed a stock recovery.
Now I downloaded this file from HTC's website, RUU 6.12.1540.14. Can you tell me where can I download its firmware?
Post #5 in backup thread linked in my signature.
ckpv5 said:
Post #5 in backup thread linked in my signature.
Click to expand...
Click to collapse
So I flashed my firmware.zip now all I need to do is just launch the RUU file from my computer? Just like HTC website instructions?
I don't need custom recovery for it right?
It fails after 5 minutes on "sending.........." :/
Yes.. just right click the RUU and select run as administrator.
Make sure you run it on Windows PC with usb 2.0
and latest htc usb drivers are installed.
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
ckpv5 said:
Yes.. just right click the RUU and select run as administrator.
Make sure you run it on Windows PC with usb 2.0
and latest htc usb drivers are installed.
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Click to expand...
Click to collapse
I am doing exactly like this.
I don't know what is wrong.
My MID is 0P6B12000
CID is BS_US002
Software Version 2.22.401.5
Android Version 4.4.3
Stock Recovery is 4.16.1540.8
Then I flashed firmware of 6.12.1540.4
And I am installing RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
When I check for updates it says your phone is up to date (been checking from past 1 and a half week)
It either gets stuck on "0% Sending........" at RUU menu.
Or it fails giving the error[155] Make sure you are using the correct Rom.
Mobile screen is stuck at HTC Logo.
When I unplug the mobile it opens fastboot saying "Fail zip info" I have to restart mobile to make it work.
My Bootloader was unlocked, I Locked it using Echo Su command.
Then I unrooted Mobile by going to super su > complete unroot.
What is possibly wrong with my mobile? ALL I want to do is update my mobile to marshmallow either by OTA or Manual.
P.s. I'm new to android so I don't know a lot of stuff about it. Sorry.
Can you post fastboot getvar all (without serial & imei no.)
When your MID is changed to 0P6B12000, CID is better as BS_US001
Are you in US ? Maybe convert it to EU is better for you.
Let's see the getvar all result first.
Here...
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
And I live in Asia.
Since you're in Asia .. I suggest to convert it to EU.
You already know how to change CID/MID, change it to CID 11111111 or HTC__001 and MID 0P6B10000
then you can follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seems that you have USB connection issue when it stuck on "0% Sending........" when using RUU exe, so a RUU zip could be better for you.
Anyway .. if you still want to update it to 6.12.1540.4 instead of convert it to EU .. what you can do is run the RUU exe, no need to connect M8 to PC, open your windows "temp" folder (in "run" type %temp%), you should see 2 new folders. One of them has rom.zip
Copy this rom.zip to your desktop, then you can follow the same guide on how to install it with htc_fastboot
Or you can rename this rom.zip to 0P6BIMG.zip and place it on your microSD. Boot to bootloader then select hboot, it will scan the file and ask whether you want to update. Volume up to update. After successfully update, remove/delete this 0P6BIMG.zip from the microSD
Edit : the easiest for you now is (since the firmware is already updated), install latest TWRP and restore 6.12.1540.4 backup that you can find in my backup thread .. after restore .. done.
So .. I can say you have 3 options here
ckpv5 said:
Since you're in Asia .. I suggest to convert it to EU.
You already know how to change CID/MID, change it to CID 11111111 or HTC__001 and MID 0P6B10000
then you can follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seems that you have USB connection issue when it stuck on "0% Sending........" when using RUU exe, so a RUU zip could be better for you.
Anyway .. if you still want to update it to 6.12.1540.4 instead of convert it to EU .. what you can do is run the RUU exe, no need to connect M8 to PC, open your windows "temp" folder (in "run" type %temp%), you should see 2 new folders. One of them has rom.zip
Copy this rom.zip to your desktop, then you can follow the same guide on how to install it with htc_fastboot
Or you can rename this rom.zip to 0P6BIMG.zip and place it on your microSD. Boot to bootloader then select hboot, it will scan the file and ask whether you want to update. Volume up to update. After successfully update, remove/delete this 0P6BIMG.zip from the microSD
Edit : the easiest for you now is (since the firmware is already updated), install latest TWRP and restore 6.12.1540.4 backup that you can find in my backup thread .. after restore .. done.
So .. I can say you have 3 options here
Click to expand...
Click to collapse
Thank you so much!
I did something else, But it worked.
What I did was put my mobile in Fastboot USB mode, And then run the RUU. I also used another USB port you were right about that too.
It worked fine.
I tried doing it before but it didn't work I think it was because of the firmware.zip thing you told me. So thanks a lot again!
Just tell me that I will get OTA updates from now on right?
husnaintariq01 said:
Just tell me that I will get OTA updates from now on right?
Click to expand...
Click to collapse
Great that you fixed it.
Yeah .. you will get OTA if there is one in the future.
But I don't think there will be any as M8 is already 2 years old and HTC stop support after 18 months.
ckpv5 said:
Great that you fixed it.
Yeah .. you will get OTA if there is one in the future.
But I don't think there will be any as M8 is already 2 years old and HTC stop support after 18 months.
Click to expand...
Click to collapse
Thanks Again.
How to mark my post as Solved?
Edit post #1 - select Go advance, then you can edit the title
HI all, I am having problems trying to flash an RUU. I can't seem to find the Marshmallow RUU.zip file 6.20.502.5 I was on Lollipop and flashed Frimware to my HTC One M8 AT&T Version. everything went good, green back went all the way. then i rebooted via "fastboot"
Now i am getting an HTC Logo screen, I can boot into bootloader, and get into fastboot. but seems the file i am trying to flash tells me it failed. i have attempted same file a few times, weather firmware, boot.img and still no luck.
can someone point me in the right direction where i can download the correct RUU File. Since i already flashed the MM Firmware. Sound to me like the Boot.img may have been corrupted ?
here is the info i have from Command "fastboot getvar all"
C:\Users\PRIVATE\Desktop\platform-tools Files>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4BLWM00489
(bootloader) imei: *************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
C:\Users\PRIVATE\Desktop\platform-tools Files>
Please direct me to correct RUU.zip file version for my HTC One M8 AT&T Version, if that is what i need to do or if i need a Boot.img please direct me to it.
Thanks for your help in advance
Download it from htc: http://www.htc.com/us/support/rom-downloads.html
I don't know how you flashed a firmware since your phone is S-ON but this RUU should work, just put the phone in fastboot and run the exe.
lucyr03 said:
Download it from htc: http://www.htc.com/us/support/rom-downloads.html
I don't know how you flashed a firmware since your phone is S-ON but this RUU should work, just put the phone in fastboot and run the exe.
Click to expand...
Click to collapse
I had bootloader locked and then had to relock it since i can't get any kind of updates from AT&T because i am on Cricket wireless. I downloaded this yesterday and triend it, 45 mins later, still nothing, I think i know why nothing happend I had the phone in RUU Boot via fastboot command "fastboot oem rebootRUU"
I re opned the EXE RUU from HTC and everything worked fine. went smooth. Now apps are updating. When I used this EXE File from HTC I needed to have phone in fastboot usb mode not RUU Mode. Fastboot and EXE file , That did the trick.
Thanks for the tip. I appreciate it. as i have been going at this for days . sometimes you need to give things a break, walk away and come back.
Now i will give lineage 15.1 and Gapp's 8.1 unofficial. This is the reason i wanted this phone on Marshmallow. I want to get rid of this AT&T bloated software and be able tether with my phone as well. Thanks alot. 'Thumbs Up"
ELEVO said:
HI all, I am having problems trying to flash an RUU. I can't seem to find the Marshmallow RUU.zip file 6.20.502.5 I was on Lollipop and flashed Frimware to my HTC One M8 AT&T Version. everything went good, green back went all the way. then i rebooted via "fastboot"
Now i am getting an HTC Logo screen, I can boot into bootloader, and get into fastboot. but seems the file i am trying to flash tells me it failed. i have attempted same file a few times, weather firmware, boot.img and still no luck.
Click to expand...
Click to collapse
Your issue is that you flashed the firmware.zip, but never flashed the RUU. No boot after flashing firmware is normal and expected, as it expects the RUU to be flashed immediately after.
I've explained a little more about the difference between firmware and RUU here: https://forum.xda-developers.com/att-htc-one-m8/help/upgrading-software-issue-t3546243
For this device, you should refrain from thinking about "firmware" and RUU/ROM being the same thing, as you can now see, they are very different things.
In addition to the link lucr05 provided, you can also find the A&T M8 RUU (EXE format) on my Index thread. I don't know if you will find the zip format RUU anywhere. But as you now see, the EXE version works fine.
lucyr03 said:
I don't know how you flashed a firmware since your phone is S-ON.
Click to expand...
Click to collapse
A signed firmware zip can be flashed (with fastboot) with s-on (FastbootRUU mode).
In fact, for US variants, flashing MM firmware is mandatory before a MM RUU will install properly (a peculiar requirement for US carrier variants).
ELEVO said:
Now i am getting an HTC Logo screen, I can boot into bootloader, and get into fastboot. but seems the file i am trying to flash tells me it failed. i have attempted same file a few times, weather firmware, boot.img and still no luck.
Sound to me like the Boot.img may have been corrupted ?
Please direct me to correct RUU.zip file version for my HTC One M8 AT&T Version, if that is what i need to do or if i need a Boot.img please direct me to it.
Click to expand...
Click to collapse
Your comments about boot.img seem like a wild guess, and not the correct answer, at that.
I'm also suspect the notion is based on past HTC devices, which had the requirement to flash boot.img separately from the ROM, which don't apply (and never applied) to the M8. Flashing boot.img also doesn't apply to firmware and/or RUU. boot.img is included in both the firmware and the RUU.