Related
I'm having a problem being able to launch apps on my One M8 ATT... I Don't have any apps on my home page and ATT Ready2Go keeps crashing on me. Can someone give me a command line so I can launch SunShine on my device through ADB, that way I can S-Off and go back to a different ROM.
Why would you need s-off to install a different rom ?
Mr Hofs said:
Why would you need s-off to install a different rom ?
Click to expand...
Click to collapse
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
isutke1287 said:
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
Click to expand...
Click to collapse
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
xunholyx said:
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
Click to expand...
Click to collapse
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(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: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
isutke1287 said:
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(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: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
Click to expand...
Click to collapse
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
xunholyx said:
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
Click to expand...
Click to collapse
I can NOT appreciate and thank you for your assistance in this! I went ahead and locked the bootloader and restored the original image with the RUU you linked me to, yesterday. Couldn't wait to try, haha. I had to sweet talk the HTC Live Chat person to tell me if I could use the RUU for the same software version as I had. Phone has been working like a champ. I'm gonna give it another day or two to settle in, do a few backups just in-case the flash doesn't go well.
I will definitely unlock the bootloader again and flash TWRP and SuperSU. But I imagine going S-OFF is just off the table right now since I'm a bit stripped of funds. I can afford it, haha, but my funds are already allocated towards adulting and such.
Again, THANK you for the support! This has been a learning experience.:good::good::good::good::good:
I've stuffed something up along the way and now my M8 seems to refuse to load any ROM I've installed on it. What's the best way to go about fixing this? It's unlocked with S-Off.
Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers
Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?
shirreer said:
Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers
Click to expand...
Click to collapse
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
redpoint73 said:
Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?
Click to expand...
Click to collapse
My OS number is 4.16.1540.8, I've tried TWRP 2.7.0.1, 2.8.7.0 and 3.0.0.0, roms I've tried include CM13, SkyDragon and a stock TWRP backup I found in another thread here.
roseyhead said:
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
Click to expand...
Click to collapse
Your MID and firmware number don't jive; and it can indicate something pretty dangerous (and possibly a radio bricked phone).
Need more info on what you've done.
Do fastboot getvar all, and post the output (delete serial number and IMEI before posting).
Was the phone new and stock (unmodified) when you got it; or did it have a previous owner?
Please list all the mods you have applied (s-off, changed CID, changed MID? etc.).
Ok, here's what getvar all reports:
(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.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -snip-
(bootloader) imei: -snip-
(bootloader) imei2: Not Support
(bootloader) meid: 99000499014851
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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
all: Done!
finished. total time: 0.035s
I bought the phone second-hand, it was running a custom ROM (SkyDragon) with cid already set to 11111111 and I wanted to return it to stock. I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
I've also tried restoring assorted TWRP backups, installing new roms and so on, directly flashing boot.img, things seem to flash ok but the phone just boots direct into fastboot.
Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!
roseyhead said:
Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!
Click to expand...
Click to collapse
I'm glad you're all set. But for other users' benefit, here is a link to HTC's official Sprint RUU page, with instructions for flashing the RUU as well as a download link for Sprint M8 marshmallow RUU 6.20.651.3
Sprint RUU instructions page:
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Sprint M8 marshmallow RUU 6.20.651.3 Direct Link:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
Cheers
i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.16.654.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 99000499165808
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
roseyhead said:
I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
Click to expand...
Click to collapse
Happy to see your sorted it out.
I agree it appears to be the Sprint version, based on the the MID (0P6B70000) and product name (m8_whl). While the MID can be modified, the product name is typically not (never seen a mod method for that - so the product name is very reliable).
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------
mushfiq20 said:
i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version-main: 2.16.654.4
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
Click to expand...
Click to collapse
This is Sprint version, same as OP based on the model ID and product name. Although main version would indicate the Sprint Harmon Kardon version. RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
The M8x designation on the back cover can't be trusted in this case. The back cover has been replaced to remove the "Sprint" logo branding. We've seen several phones like this (back cover replaced to remove evidence of branding) on the forum. You have to go by the getvar data.
Also, be sure to remove your IMEI and serial number from the getvar output. These are personal data, and should never be posted online.
redpoint73 said:
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
Click to expand...
Click to collapse
Thanks a lot for the tip! I'll bear that in mind going forward.
Hi there I seem to be having similar issues. I purchased a refurbished M8. The case indicates 0P6B110 M8x however fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [REDACTED]
(bootloader) imei: [REDACTED]
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237658
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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
Going off the info in the thread I downloaded RUU 6.20.651.3.
While verifying I want to update the ROM version it states:
From:
Image Version: 1.54.651.8
To:
Image Version: 6.20.651.3
After clicking next and progressing I get Error 155.
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.
metalbassist33 said:
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3
ckpv5 said:
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3
Click to expand...
Click to collapse
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?
metalbassist33 said:
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?
Click to expand...
Click to collapse
No .. not needed, run Lollipop RUU then do OTA to Marshmallow
I've recently installed Firmware and another ROM (RUU) they went thru successfully but only updated to Lollipop 5.01 which i thought was strange.. well anyway, i flashed TWRP and now it says entering recovery for about a second then goes back to the Boatloader page (fastboot etc) tried to restart and try again and it does the same every time..tried re-flashing TWRP and still does the same.. any ideas please?
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44xxx xxx xxx
(bootloader) imei: 354 xxx xxx xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: HTC__032
(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: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
C:\adb>
Forgot to mention, i need recovery to change the MID ..have tried manually without success.
Thank you
Try wipe cache, and flash TWRP again.
Make sure its TWRP version 2.8.7.0 or 3.0.0.0. Some folks have been trying to flash older versions, some of which don't work on LP or later.
redpoint73 said:
Try wipe cache, and flash TWRP again.
Make sure its TWRP version 2.8.7.0 or 3.0.0.0. Some folks have been trying to flash older versions, some of which don't work on LP or later.
Click to expand...
Click to collapse
Thank you, tried fastboot erase cache and flashed 2.8.7.0 and it still does the same thing.. i already flashed 3.0.0.1 before - would you know how to change the MID without having to use recovery? once i have changed that i can get the European RUU installed on my device - i have changed the CID already .. the phone was US on T-Mobile but i'm wanting it on UK O2 now ..thank you again
Did you flash TWRP before booting up at least once?
RUU to marshmallow doesn't seem to exist yet. (aka I haven't found one)
So update to 4.25 firmware which is lollipop 5.0.2 - I think.
Then allow phone to boot (make sure to have stock recovery), go through with all the OTAs which will come.
Once OTAs are completed successfully feel free to flash TWRP back.
Kyuubi10 said:
Did you flash TWRP before booting up at least once?
RUU to marshmallow doesn't seem to exist yet. (aka I haven't found one)
So update to 4.25 firmware which is lollipop 5.0.2 - I think.
Then allow phone to boot (make sure to have stock recovery), go through with all the OTAs which will come.
Once OTAs are completed successfully feel free to flash TWRP back.
Click to expand...
Click to collapse
Hi and thanks again, to be honest i dont know what i've done.. i got the phone from eBay..new M8 but when i spoke to HTC they said the phone was US on T-Mobile.. i just wanted to change the CID & MID so i can install a European ROM maybe O2 or something ..i'm really quite new to this ..i had a M7 before which i did manage to flash and update to LP but with this M8 i'm struggling .. i just downloaded Firmware 4.25.651.18.zip ..which ROM would be best to use with this please? i'm sorry for my lack of knowledge here.. and should i wipe the phone completely? factory format as i cannot get into Recovery..
Thanks again
Sorry, i'm getting this when i try to flash that Firmware
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot flash zip 4.25.651.18.zip
target reported max download size of 1826418688 bytes
sending 'zip' (54607 KB)...
OKAY [ 3.122s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 5.542s
Fixed for now
hi again, the reason the original ROM did not instal was because i had changed the CID to a European one and was trying to instal a US TMOB ROM ..i changed the the CID back to a SuperCID 1st then installed the ROM and then changed the CID back to the original T-MOB010 CID so i could get all the OTA updates ..i will just leave it at this for now as i thought originally i had bricked my M8 - after the 1st flash the phone went into a boot loop :/ ...anyway, it's all sorted now and doing the many OTA updates but this particular one only updates to LP 5.01 .... i'm just wondering how i could get it to update to 5.02 or even 6.0? i will still try and change the CID & MID when i have enough information and am completely confident (and have a spare phone) then instal a European ROM and see if that get me the updates - thanks for the help
Craig_CFC said:
hi again, the reason the original ROM did not instal was because i had changed the CID to a European one and was trying to instal a US TMOB ROM ..i changed the the CID back to a SuperCID 1st then installed the ROM and then changed the CID back to the original T-MOB010 CID so i could get all the OTA updates ..i will just leave it at this for now as i thought originally i had bricked my M8 - after the 1st flash the phone went into a boot loop :/ ...anyway, it's all sorted now and doing the many OTA updates but this particular one only updates to LP 5.01 .... i'm just wondering how i could get it to update to 5.02 or even 6.0? i will still try and change the CID & MID when i have enough information and am completely confident (and have a spare phone) then instal a European ROM and see if that get me the updates - thanks for the help
Click to expand...
Click to collapse
Perfect, so you figured it out Well Done.
Yeh, the best way is by changing MID and CID then flashing what you wish.
I wouldn't know since I am S-on.
Kyuubi10 said:
Perfect, so you figured it out Well Done.
Yeh, the best way is by changing MID and CID then flashing what you wish.
I wouldn't know since I am S-on.
Click to expand...
Click to collapse
I used Sunshine S-Off to do that.. payed the $25 ..its really easy and don't take long.
As for the phone, i think i'm going to do some serious research before i attempt anything like that again - its all up and running again, i'm not even going to flash TWRP this time until i really need it .. it's currently updated to 5.01 which i can live with.. i just wanted to taste a bit of Marshmallow i suppose it's a waiting game now - thanks again
Craig_CFC said:
i just downloaded Firmware 4.25.651.18.zip
Sorry, i'm getting this when i try to flash that Firmware
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
How did you come about picking that firmware? Its not for T-Mobile US, its for Sprint.
In fact, its a good thing the firmware failed to install. If it succeeded, it may have bricked your phone due to partitioning differences between the Sprint version and most other M8 versions.
Be very careful about what firmware you flash. Don't flash any firmware you if you aren't 100% sure its the right one you should be using.
---------- Post added at 10:38 AM ---------- Previous post was at 10:17 AM ----------
Craig_CFC said:
would you know how to change the MID without having to use recovery?
Click to expand...
Click to collapse
I do, but I'm confused since you stated in the OP that you already tried to do it "manually"?
Craig_CFC said:
Forgot to mention, i need recovery to change the MID ..have tried manually without success.
Click to expand...
Click to collapse
Before we head in that direction, you need to understand a couple things about changes made requiring s-off. By definition s-off means that all (or at least most) security checks are off. So this means:
1) Changing the MID is a bit risky, in that you are manually editing/modifying memory blocks (not sure if "block" is technically the right term, but I think you understand what I'm getting at) using adb. Enter the command incorrectly (and modify the wrong memory block), and you can brick the phone! You have to be extremely careful about the process of changing the MID, and double check and triple check every single commands is correct (not a single typo) before pressing "Enter".
2) As mentioned above, flashing firmware also requires close attention and care. You need to be 100% of the firmware you are flashing. Once you've changed the MID, you are bypassing the very safety check that is designed to prevent bricks (from flashing the wrong firmware).
If you are prepared to use extreme caution and exercise the required care, then we can proceed with what you want to do (change MID, flash Euro RUU so that you can "convert" the phone to official Euro version, with full OTA updates).
Although another method (if you don't mind the lack of OTA updates) is to ensure you are on LP firmware (or flash T-Mobile US firmware or RUU to get to LP firmware). Then flash a MM custom ROM (which should work fine with LP firmware). This direction is much safer, as its nearly impossible to brick the phone flashing the firmware meant for your original CID/MID or from flashing a custom ROM.
Really, the lack of OTA is not a big deal, in my opinion. The custom (or near stock) ROMs get updated just as fast as the official OTAs (in fact, often faster depending on which CID you are talking about) so you can continue to keep updated by flashing custom ROMs. Honestly, this is my 3rd HTC phone, and the number of times I've installed official OTA updates is zero, due to the fact that the ROMs posted by devs here are just as good (or better) and just as timely.
Thank you for the advice & tips... the phone is S-Off (Sunshine) and bootloader Unlocked - all i'm wanting to do is go from T-Mobile US to a UK ROM like maybe O2 ..i'm on the giffgaff which run on the O2 network ... i have been searching for the correct Firmware without success - i have RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed
but just need to find the correct firmware to flash so i can instal this.. any ideas please? am very new to this and don't completely understand how to find the correct FW for a particular RUU
D:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
as you can see it is US T-MOB - how can i change this so i have O2 UK please?
Many many thanks
I discovered the reason TWRP was not flashing properly... i needed to update to Android 5.01 1st then flash TWRP custom recovery..that all works well now and i have recovery back but just put MID_Changer_03.07.14 on my phone and ran it in recovery - it all worked great but when i checked the MID it hadnt changed so ran again an still no change - i'm wanting to change that too 0P6B1000 (Europe) then the CID to HTC__032 ...then i will try to instal the above RUU - does this all sound like the right thing to do? i have been trying to find the right firmware for that RUU but cannot seem to find one or rather don't know what i am looking for - thanks again
Craig_CFC said:
I discovered the reason TWRP was not flashing properly... i needed to update to Android 5.01 1st then flash TWRP custom recovery..that all works well now and i have recovery back but just put MID_Changer_03.07.14 on my phone and ran it in recovery - it all worked great but when i checked the MID it hadnt changed so ran again an still no change - i'm wanting to change that too 0P6B1000 (Europe) then the CID to HTC__032 ...then i will try to instal the above RUU - does this all sound like the right thing to do? i have been trying to find the right firmware for that RUU but cannot seem to find one or rather don't know what i am looking for - thanks again
Click to expand...
Click to collapse
Are you s-off? If not, you need to be s-off to change the mid.
robocuff said:
Are you s-off? If not, you need to be s-off to change the mid.
Click to expand...
Click to collapse
Yes S-Off (sunshine) and unlocked bootloader .. it just won't let me change it for some reason
Craig_CFC said:
D:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I'm getting more and more confused. This doesn't match the getvar output in Post #1. Did you change something to get to this point?
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
Craig_CFC said:
i have recovery back but just put MID_Changer_03.07.14 on my phone and ran it in recovery - it all worked great but when i checked the MID it hadnt changed so ran again an still no change
Click to expand...
Click to collapse
Haven't heard of such a method. Can you link to where you got this from?
There is a proven method for changing MID on the M8, and that is not it.
redpoint73 said:
I'm getting more and more confused. This doesn't match the getvar output in Post #1. Did you change something to get to this point?
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
Haven't heard of such a method. Can you link to where you got this from?
There is a proven method for changing MID on the M8, and that is not it.
Click to expand...
Click to collapse
I flash differnt firmware from OP i think... i'm still none the wiser though.. my updates OTA to 5.01 but i'm sure i can get 6.0 with sense 7.0 if i use a UK ROM but i need the correct firmware for that particular ROM and i do not know what to look for - the MID Changer was here http://www.droidviews.com/change-cid-mid-htc-one-devices/ thanks
Craig_CFC said:
I flash differnt firmware from OP i think...
Click to expand...
Click to collapse
Looks like you flashed an older firmware (really old, as in Kitkat Android 4.4.2), based on Post #10 (versus what you had originally in Post #1).
Craig_CFC said:
i'm still none the wiser though.. my updates OTA to 5.01
Click to expand...
Click to collapse
So its updated back to Lollipop?
Do another fastboot getvar all, and post the current status.
Craig_CFC said:
the MID Changer was here http://www.droidviews.com/change-cid-mid-htc-one-devices/ thanks
Click to expand...
Click to collapse
That isn't for the M8. If you look at that webpage's "Source" it links to the XDA One M7 section. That mod is for the M7, not the M8.
You're lucky it didn't brick the phone. I've already stated above in Post #6 how dangerous MID changing can be, if not performed properly. But it seems that you've chosen to ignore that advice.
No offense intended, it seems you are going about things rather recklessly. Already you've flashed an incorrect old T-Mobile firmware, tried flashing the firmware for the wrong version (Verizon) and now tried changing the MID with a mod for the M7. There is a proper process to change the MID on the M8. But I'm hesitant to lead you to that (of course, you can find it yourself - but that's your own deal), as you haven't demonstrated you are capable of the proper carefulness. And frankly, I don't want you messing with things that can easily brick your phone.
My suggestion would be to flash back to 4.20.531.5 firmware (if its not the current firmware) then just leave it that way until T-Mobile releases Marshmallow. Alternately, install a custom recovery (unlocked bootloader required, if its not presently), and simply flash a MM ROM; which should work find with LP firmware. These options are relatively safe, and don't require you messing with the MID.
redpoint73 said:
Looks like you flashed an older firmware (really old, as in Kitkat Android 4.4.2), based on Post #10 (versus what you had originally in Post #1).
So its updated back to Lollipop?
Do another fastboot getvar all, and post the current status.
That isn't for the M8. If you look at that webpage's "Source" it links to the XDA One M7 section. That mod is for the M7, not the M8.
You're lucky it didn't brick the phone. I've already stated above in Post #6 how dangerous MID changing can be, if not performed properly. But it seems that you've chosen to ignore that advice.
No offense intended, it seems you are going about things rather recklessly. Already you've flashed an incorrect old T-Mobile firmware, tried flashing the firmware for the wrong version (Verizon) and now tried changing the MID with a mod for the M7. There is a proper process to change the MID on the M8. But I'm hesitant to lead you to that (of course, you can find it yourself - but that's your own deal), as you haven't demonstrated you are capable of the proper carefulness. And frankly, I don't want you messing with things that can easily brick your phone.
My suggestion would be to flash back to 4.20.531.5 firmware (if its not the current firmware) then just leave it that way until T-Mobile releases Marshmallow. Alternately, install a custom recovery (unlocked bootloader required, if its not presently), and simply flash a MM ROM; which should work find with LP firmware. These options are relatively safe, and don't require you messing with the MID.
Click to expand...
Click to collapse
Thank you ..i'm really no good at this as you clearly can tell .... as requested, here is my phone info:
D:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.5
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Thanks again
Long story short, I forgot my screen lock and wiped as a last resort. Realizing too late that a factory reset wouldn't complete, I was left with a paperweight. I was able to get a rooted stock ROM from XDA, flashed it and it seems to be working. I want to get back to viper ROM, preferably marshmallow (I'm currently on lollipop) but I am having a lot of trouble. Attempts to get s-off have been thwarted, and flashing viper (5.0.2) has failed. Any help would be appreciated. I can answer any questions.
What stock ROM did you flash, exactly?
How exactly are you trying to s-off, and what step did you get stuck (error messages, or other results?)?
When the ROM failed, did it give you an error message (or list any other outputs or results)?
Your statements on these last 2 points if far too vague, for us to help properly.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Lmy470.h6 is the ROM I flashed. I've been trying to push firewater via adb to get s off. I can't/won't pay for a sunshine. When flashing other stock Roms, the error is no error. It just says install aborted. When trying to flash viper, it says there's a permission error. When trying to run firewater, it gives me the PIE error. Getvar coming later.
Firewater won't work, Period. It had an online component (had to connec to a server), which the devs stopped supporting in Dec 2014. Nothing you do will make it work, and is a complete waste of time.
That said, you don't need s-off to flash ROMs. And whatever is wrong with flashing ROM, s-off is probably not going to fix.
The fact that multiple ROMs work, indicates user error, and you're incorrectly trying to blame the ROMs ("poop ROM").
What TWRP version? Need that info, and getvar data. But I'm guessing you just have an old version of TWRP (or try another slightly different build TWRP).
I'm actually using philz touch recovery. I only call it a poop ROM because I don't like what it came with and how it looks. Also. The ROM I'm using is the only ROM that works thus far. Most other Roms simply abort. Viper ROM tells me it doesn't have to permissions necessary which indicates the need for s off. I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
One last thing. Flashing the ROM I'm currently using created new 0 directories. I now have 0/0/0. Any safe way to fix that?
enviouss said:
I'm actually using philz touch recovery.
Click to expand...
Click to collapse
That's the problem right there. Philz hasn't been updated in a long time, maybe 2 years. Its almost certainly the cause for the ROM flashes failing.
Use TWRP, but exact version depends on your current firmware version, indicated in getvar. But probably TWRP 2.8.7 since you indicated you were using Lollipop ROMs okay.
enviouss said:
I only call it a poop ROM because I don't like what it came with and how it looks.
Click to expand...
Click to collapse
So its your personal opinion and preference, and I would recommend you not insulting the work of devs that work so hard (usually for no compensation) to post their work here.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
enviouss said:
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
Click to expand...
Click to collapse
Sideload adb still needs the proper recovery, adb can't flash a ROM by itself. Sideload just adds move points of failure, not less. I don't recommend it, as I've seen it cause more problems than it solves (fails when simply flashing in recovery works).
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
enviouss said:
I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when issuing the command?
If so, try another cable, another USB port, or re-install HTC drivers.
I haven't been I boot loader mode. Will try shortly. Also. Will change to twrp. And yes, I'm on lollipop 5.1. I will change recoveries and attempt getvar. Results will be posted.
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
enviouss said:
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
enviouss said:
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
Click to expand...
Click to collapse
I'm glad I asked for the getvar data. Your firmware (hboot, radio, etc.)is woefully outdated as its still on kitkat firmware, which I can tell from the radio number and version-main 3.28.1540.5. This alone will prevent LP and MM ROMs from working (no boot or broken WiFi).
There are various ways to update the firmware:
- Restore stock TWRP backup for 3.28.1540.5, and corresponding stock recovery, and perform OTA updates which will also update the firmware.
- Relock bootloader, and flash full stock 6.12.1540.4 firmware following the Method 2 here. After flashing firmware, you can then unlock bootloader again, flash TWRP and flash the desire ROM.
I would greatly prefer not to relock my boot loader,as it requires HTC correspondence to unlock. That could take a while. Can you walk me through your first method? Possibly with links to other threads and downloads?
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image. Now whenever I try to boot, or enter recovery mode, i get the red triangle of death. Please help! I tried reflashing twrp via adb, but adb doesnt recognize my device anymore! I dont know what to do...
update: performed a factory reset. Was able to get device up and running again. Impatiently awaiting further instruction.
enviouss said:
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image.
Click to expand...
Click to collapse
What did you download, and from where? Its not clear what you were trying to do here, exactly. You don't need root to flash ROMs or TWRP backups; and I personally dislike using apps like Flashify, for things that are easily accomplished with fastboot, TWRP, etc.
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
enviouss said:
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
Click to expand...
Click to collapse
He did give you expert advice, and you didn't follow it. Don't use Flashify. Any instructions you get from anyone here will tell you to use ADB/fastboot.
Also, you are going ahead without proper instructions and you can go ahead and do that, but go to where you got those other instructions from to ask for help.
Actually, in reference to the nandroid backup, he (we are assuming here) never said exactly how to use the files. Just what to do. I need precise instructions with links to fix this issue. This is one I've never dealt with before.
Htc one m8
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: HT46PWM03644
(bootloader) imei: 3578710********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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!
finished. total time: 0.158s
Is there a solution without s-off
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
with bootloader locked/unlocked state;
with s-on:
Failed
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
Tried nandroid backup
M8_UL_TWRP_Nandroid_6.12.401.4.zip
succefully flashed backup but stuck on htc logo
Failed
Please help
What is the problem? Is it not booting into the ROM?
when there was boot.the phone at the startup gave (unfortunately------- has stopped)error and also no back key home key visible.
wiped the device. it was all same.
tried RUU it was the same
unlocked the boot loader
and flashed
stock recovery
twrp recovery
then tried nandroid backup restore
the restore was succefull but the phone wont reach startup (tried 1Hour max)
one peculiar thing i notice.earlier when it was booting to startup i was unable to copy anything to internal or external memory as it would say device not ready or disconnected.but i was able to browse the folders.
My opinion partition problem.Need others help to sort out
Note all the files i have mentioned is checked with md5
My comments below in red font:
raffazila said:
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
None of these will ever work on your device, in the s-on configuration. The RUUs containing "BrightstarUS" are for the US Developer's Edition. They won't run on your phone, as they will fail CID and MID checks (your device has CID and MID - can't change these with s-on).
The one labeled "Europe" is for an older version (Lollipop) than what is installed on the phone (Marshmallow). This will fail version check. By definition, you can't "downgrade" by RUU with s-on
with bootloader locked/unlocked state;
with s-on:
Failed
with s-on, its absolutely mandatory to have a locked or relocked bootloader to flash RUU. Unlocked bootloader will make it fail
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
This is the correct RUU for your version, and should run with s-on. Saying it "Failed" with no other info, is not enough. Were their any error messages, other outputs, etc.? What commands did you use to run it? Were you in fastbootRUU mode?
I would suggest trying to run this again, with the bootloader RELOCKED, and you also need to use htc_fastboot, as the "generic" fastboot will not work with RUU.
Click to expand...
Click to collapse
Firstly it is good someone with good knowledge is answering my doubts.
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Finaly to say you have found the nearest problem which i was thinking too.
I will check and post.
@redpoint73 Problem soilved.Silly mistake.Thanks.
raffazila said:
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Click to expand...
Click to collapse
I can't tell what you are referring too, as the statement is really vague. Can you give more details?
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
raffazila said:
Problem soilved.Silly mistake.Thanks.
Click to expand...
Click to collapse
Its best if you posted the solution, and what the mistake was. Useful for those helping (to see whether we sent you on the right path), as well as anyone else reading which may have the same or similar issue.
No mistake is that silly when it comes to these devices. Its often just specific knowledge that was missing, or a detail you didn't catch before (which is an honest mistake, either way).