Related
Hello
Here are the "stats" of my brand new HTC M8, I say brand new in that I broke the cellophane seal, and took off the protectors but I'm starting to think it has been tampered with....
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(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: 11111111
(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
I opened up a log file on phone whilst browsing the Android Recovery and spotted these attributes within a very large log file
Code:
CID = CWS__001
MID = 0P6B1200
aa.cid = BS_US001
sku = Brightstar US WWE
project = M8_UL_L50_SENSE60_MR 411207
buildline = M8UL_BrightstarUS_WWE_L50_CRC_Sense60_stable_mr
First thing you'll notice is the SUPERCID of 11111111, the log seems to imply it was once at CWS__001, but who knows.
You'll also notice it's an M8_UL_CA variant, which Google tells me is the AT&T variant, but that it has the M8_UL Brightstart WWE ROM installed. [I don't want AT&T updates]
So with all these changes, it's understandable that when I ran the OTA stagefright update, HTC would not allow the install saying I have a "Variant System Update" error, saying that I need to restore to stock or call HTC for support.
My question: How do I go about updating this phone with stock images as and when they get released without tampering too much with unlocked this and that?
What I've tried: I downloaded the latest RUU from the US site, tried to run it, but it closes before it even starts [even after I installed all the VCRedists, and tried on 3 computers]. So I unpacked the .exe and took out the rom.zip and tried to flash it in fastboot... I got an
Code:
FAILED (remote: 12 signature verify fail)
error. Google tells me this is because one or more of the checks on CID MID etc does not match the ROM. Android.txt in the .exe has the right MID but not the right CID.
I think my last hope is to Unlock the bootloader, S-OFF and Install TWRP and install Stock ROMS that way, but theres two problems with this approach, One - I don't why if I need S-OFF and Bootloader unlocked to install a ROM, do you need both, or just one or something else? and Two - I can't find the latest ROM. I can only find the one I'm on now, which will still probably bug me for an OTA update for stagefright. Plus it's a mine field to work out which ROM is what, with CIDs and MIDs and Models and Carriers etc.
Any help would be great, as I want to migrate to this phone from my S5, but I wont until I know its stable and working.
Thanks in advance.
Vyker said:
You'll also notice it's an M8_UL_CA variant, which Google tells me is the AT&T variant, but that it has the M8_UL Brightstart WWE ROM installed. [I don't want AT&T updates]
Click to expand...
Click to collapse
I think you are mostly correct, in that it was an AT&T variant, but "fully converted" (no just ROM, but all firmware - likely by RUU) to Developer's Edition (Brightstar) which happens to share the same MID (12000).
Does it have the AT&T "globe/deathstar" logo on the back cover? It only means much if the answer is "yes". If "no", its possible the back cover was replaced (with an "unbranded" cover).
Also, I agree SuperCID is an indication that phone was modded. I've never seen a phone come from the factory with SuperCID.
Vyker said:
What I've tried: I downloaded the latest RUU from the US site, tried to run it, but it closes before it even starts [even after I installed all the VCRedists, and tried on 3 computers]. So I unpacked the .exe and took out the rom.zip and tried to flash it in fastboot... I got an
Code:
FAILED (remote: 12 signature verify fail)
error. Google tells me this is because one or more of the checks on CID MID etc does not match the ROM. Android.txt in the .exe has the right MID but not the right CID.
Click to expand...
Click to collapse
What is the exact file name of the RUU.exe?
Vyker said:
I think my last hope is to Unlock the bootloader, S-OFF and Install TWRP and install Stock ROMS that way, but theres two problems with this approach, One - I don't why if I need S-OFF and Bootloader unlocked to install a ROM, do you need both, or just one or something else? and Two - I can't find the latest ROM. I can only find the one I'm on now, which will still probably bug me for an OTA update for stagefright. Plus it's a mine field to work out which ROM is what, with CIDs and MIDs and Models and Carriers etc.
Click to expand...
Click to collapse
You don't need s-off to flash a ROM or stock nandroid.
If you want to take this path, what you want is the Developer's Edition ROM which matches 4.16.1540.8 listed as your "main version".
But I'm confident we can get the proper RUU working.
Thanks for a thorough reply redpoint - was really worried I'd get a "just flash CM on it" one liner that won't really help me....
redpoint73 said:
Does it have the AT&T "globe/deathstar" logo on the back cover? It only means much if the answer is "yes". If "no", its possible the back cover was replaced (with an "unbranded" cover).
Click to expand...
Click to collapse
No, nothing on it hints to AT&T, not the box, not the phone and not the OS. If you look at it, you'd think its a brand new HTC branded device.
redpoint73 said:
What is the exact file name of the RUU.exe?
Click to expand...
Click to collapse
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
I got it from here..
http://www.htc.com/us/support/htc-one-m8/news/
And here is what was in the android-info.txt file
Code:
modelid: 0P6B12000
modelid: 0P6B13000
cidnum: BS_US001
cidnum: BS_US002
cidnum: HTC__017
mainver: 4.17.1540.9
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
redpoint73 said:
You don't need s-off to flash a ROM or stock nandroid.
Click to expand...
Click to collapse
So just need to unlock the bootloader with htcdev.com and then flash a custom recovery - then straight onto nandroid backups of the correct version, right?
redpoint73 said:
If you want to take this path, what you want is the Developer's Edition ROM which matches 4.16.1540.8 listed as your "main version".
But I'm confident we can get the proper RUU working.
Click to expand...
Click to collapse
I would love to get it going with just an RUU. As I feel once the first RUU works, then it'll be plain sailing from there for all future ones including Marshmallow.
Looking forward to your reply and thanks again.
Vyker said:
No, nothing on it hints to AT&T, not the box, not the phone and not the OS. If you look at it, you'd think its a brand new HTC branded device.
Click to expand...
Click to collapse
Does it have a model number in tiny print, at the bottom of the back cover? If so, what model number is it?
Vyker said:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
Click to expand...
Click to collapse
This should work for your MID and main version. Is your bootloader UNLOCKED, RELOCKED, or LOCKED?
redpoint73 said:
Does it have a model number in tiny print, at the bottom of the back cover? If so, what model number is it?
Click to expand...
Click to collapse
I'll get another reply after this, need to get back home and check.
redpoint73 said:
This should work for your MID and main version. Is your bootloader UNLOCKED, RELOCKED, or LOCKED?
Click to expand...
Click to collapse
Bootloader is LOCKED.
Does it just check for MID, or will it also look for the CID? as you know the CID is 1111111, when I tried to change my CID I got the error below
Code:
fastboot oem writecid BS_US002
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(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))
finished. total time: 1.141s
Vyker said:
Bootloader is LOCKED.
Does it just check for MID, or will it also look for the CID? as you know the CID is 1111111
Click to expand...
Click to collapse
It checks both MID and CID. But SuperCID (11111111) should work, as SuperCID by definition will "pass" any CID checks.
But CID is the only remaining thing I can think of that would prevent the RUU from being run. The RUU is okay for your main version (1540, and the RUU is a equal or higher version), MID, and bootloader is LOCKED (as it should be to RUU).
Vyker said:
when I tried to change my CID I got the error below
Click to expand...
Click to collapse
You need s-off to change CID. It would be a last resort, as s-off costs $25 and might not even solve the issue.
One thing you can try, is load sunshine app to see if the phone was already s-off previously by sunshine. If so, you may be able to s-off for free; as the $25 license fee is per phone, and it should let you s-off again, if sunshine was used previously on this phone.
http://theroot.ninja/
I suspect the phone was s-off at some point, then SuperCID, then made s-on again.
The only other way it would be SuperCID, is from the factory. And as I've mentioned, I've never heard of an HTC device with SuperCID from the factory. Although there is a first time for everything!
redpoint73 said:
Does it have a model number in tiny print, at the bottom of the back cover? If so, what model number is it?
Click to expand...
Click to collapse
In very small print, the following is written on the bottom back.
Model: 0P6B100 and after the FCC ID it says "M8n"
redpoint73 said:
One thing you can try, is load sunshine app to see if the phone was already s-off previously by sunshine. If so, you may be able to s-off for free; as the $25 license fee is per phone, and it should let you s-off again, if sunshine was used previously on this phone.
http://theroot.ninja/
I suspect the phone was s-off at some point, then SuperCID, then made s-on again.
The only other way it would be SuperCID, is from the factory. And as I've mentioned, I've never heard of an HTC device with SuperCID from the factory. Although there is a first time for everything!
Click to expand...
Click to collapse
Interesting thought.
I installed SunShine, and had it run through its pre-tests - it says the phone passed and then goes ahead to attempt to temp-root it and then fails. The phone is not rooted.
Does this pre-test pass mean anything? is that what you were looking for?
Vyker said:
In very small print, the following is written on the bottom back.
Model: 0P6B100 and after the FCC ID it says "M8n"
Click to expand...
Click to collapse
Odder and odder. Of course, this doesn't match the MID given in getvar. So either the MID was hacked in software, or there was a "hardware hack" of replacing the back cover.
Vyker said:
Interesting thought.
I installed SunShine, and had it run through its pre-tests - it says the phone passed and then goes ahead to attempt to temp-root it and then fails. The phone is not rooted.
Does this pre-test pass mean anything? is that what you were looking for?
Click to expand...
Click to collapse
I think pre-test just means you have a stock system (not a custom ROM), which is pretty much required for sunshine to work.
Unfortunately, I can't help too much with sunshine, beyond what I've already stated. I actually did s-off long before sunshine using another (obsolete) method, and can only pass on sunshine knowledge that I've read on these forums!
I'm hesitant to go any further with sunshine, as it may just end up with you paying $25 and not even solve the RUU issue anyway.
I have a feeling I'm missing something here, but I can't imagine what.
redpoint73 said:
Odder and odder. Of course, this doesn't match the MID given in getvar. So either the MID was hacked in software, or there was a "hardware hack" of replacing the back cover.
Click to expand...
Click to collapse
Unmatched indeed - here's another dynamic, the part number on the back of the box, which has a sticker with the correct IMEI and Serial number tells me the part number is 99HJY001-00 - which a quick Google shows it as the Amber Gold variant - I'm holding a Red phone. :/
redpoint73 said:
I think pre-test just means you have a stock system (not a custom ROM), which is pretty much required for sunshine to work.
Unfortunately, I can't help too much with sunshine, beyond what I've already stated. I actually did s-off long before sunshine using another (obsolete) method, and can only pass on sunshine knowledge that I've read on these forums!
I'm hesitant to go any further with sunshine, as it may just end up with you paying $25 and not even solve the RUU issue anyway.
I have a feeling I'm missing something here, but I can't imagine what.
Click to expand...
Click to collapse
When I spoke to HTC support a week or so ago, they told me it's a GroupO Inc device, they are a large supply chain company in the US. M8_UL_CA tells us it's an AT&T model, HTC M8n is the international variant model number, and the part number says it should be Gold. The CID used to be CWS we think, but has SUPERCID now, yet its LOCKED and not RELOCKED or TAMPERED in the bootloader, which means how was it unlocked, changed and then relocked but still showing as LOCKED.
Does that sum up where we're so far? #confused.
I'm starting to think the only real option here is to go rouge, and unlock the lot, bootloader and S-OFF, then start with a fresh stock ROM that can be rooted. But I can only bring myself to go down this route knowing that I can get stock 6.0 update.
Vyker said:
I'm holding a Red phone. :/
Click to expand...
Click to collapse
Hubba-whaaat??? Its RED???
Holy plot twist! I did not see that coming. There was never any AT&T red version, and I'm pretty sure there was never a red Dev Edition (Brightstar) either.
The only red variants know of are Verizon (which would have the VZN logo, I believe) and UK O2, which might match the "100" model number.
So the front bezels are red also?
Where did you buy this from, anyway?
Vyker said:
I'm holding a Red phone. :/
The CID used to be CWS we think, but has SUPERCID now, yet its LOCKED and not RELOCKED or TAMPERED in the bootloader, which means how was it unlocked, changed and then relocked but still showing as LOCKED.
Click to expand...
Click to collapse
Once s-off (which would be required to make it SuperCID), it easy to mod the bootloader flag to say LOCKED. There is a guide for that in the Development section.
Vyker said:
I'm starting to think the only real option here is to go rouge, and unlock the lot, bootloader and S-OFF, then start with a fresh stock ROM that can be rooted. But I can only bring myself to go down this route knowing that I can get stock 6.0 update.
Click to expand...
Click to collapse
If we can't get an RUU to work, that may be your best bet.
If the RUU is failing, an OTA would probably fail also. But I'm confidant there will be Marshmallow custom Sense ROMs to flash. There is already a MM GPE ROM.
redpoint73 said:
Hubba-whaaat??? Its RED???
Holy plot twist! I did not see that coming. There was never any AT&T red version, and I'm pretty sure there was never a red Dev Edition (Brightstar) either.
The only red variants know of are Verizon (which would have the VZN logo, I believe) and UK O2, which might match the "100" model number.
So the front bezels are red also?
Where did you buy this from, anyway?
Click to expand...
Click to collapse
Hahaha, yes, it's red, its a lovely Red too, even the box has a red photo on the front.
Yes, all the parts are Red, front speaker grills and even the bits that come out, the sim tray and sd card holder etc.
I got it off eBay as a Brand new device from Hong Kong
redpoint73 said:
Once s-off (which would be required to make it SuperCID), it easy to mod the bootloader flag to say LOCKED. There is a guide for that in the Development section.
Click to expand...
Click to collapse
yes, I did spot this Googling around... so it may be what he has done
redpoint73 said:
If we can't get an RUU to work, that may be your best bet.
If the RUU is failing, an OTA would probably fail also. But I'm confidant there will be Marshmallow custom Sense ROMs to flash. There is already a MM GPE ROM.
Click to expand...
Click to collapse
What can we try next to get the RUU to run? I want to try and exhaust all avenues with this approach before giving in to unlocking and ROM'ing.
Thanks for your time and help so far mate, appreciate it.
I just received HTC one m8 and i want to install the right RUU for my device from HTC support site
can you please help, my fastboot vars :
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(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-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: 11111111
(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
all: Done!
finished. total time: 0.050s
4.16.1540.8 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
then you can do OTA to Marshmallow 6.12.1540.4
Thanks,
even if I have cid = 11111111 ?
Yes - 11111111 or SuperCID is a universal CID, RUU/OTA will accept that.
You need to relock bootloader before you run RUU because your device now is S-On
and you need a Windows PC with USB2.0 and latest HTC USB driver installed.
If you're not sure about HTC USB driver - download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install then after uninstall HTC Sync Manager but leave the HTC USB driver
ckpv5 said:
Yes - 11111111 or SuperCID is a universal CID, RUU/OTA will accept that.
Click to expand...
Click to collapse
Thanks
and another questions to be sure:
1) I get the device with 4.16.1540.8 installed , why i need to install it again ?
2) my device is s-on , does it affects on updates with supercid ?
1. I don't know why - you asked for the RUU so I gave you the link. You should know better whether you need it or not.
2. No .. as long as the ROM in your system now is non-rooted (never rooted) and stock recovery is installed .. should be fine.
If you're not sure then run the RUU then do OTA. Before that you can try to update and see whether it will success or fail.
Settings - about - software update.
ckpv5 said:
1. I don't know why - you asked for the RUU so I gave you the link. You should know better whether you need it or not.
2. No .. as long as the ROM in your system now is non-rooted (never rooted) and stock recovery is installed .. should be fine.
If you're not sure then run the RUU then do OTA. Before that you can try to update and see whether it will success or fail.
Settings - about - software update.
Click to expand...
Click to collapse
when I try to update from Settings the device found new version 4.17.1540.9 but get the following message :
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at wwwhtccom"
Your getvar doesn't show any irregularity.
I updated my M8 also on same CID 11111111 and MID 0P6B12000
So I have no idea .. I first helped because you asked for RUU.
Lets wait if anyone else will come to help for other problem
@redpoint73 - if you are around .. maybe you can help to confirm whether this device is AT&T or Developer Edition.
I have a feeling this is an AT&T converted to DEV ED and re S-On
@tapuz12ewq
Another possibility is your device is a AT&T originally .. you also can install RUU for AT&T, only thing is there is no Marshmallow update yet for AT&T - you can get the RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
ckpv5 said:
Your getvar doesn't show any irregularity.
I updated my M8 also on same CID 11111111 and MID 0P6B12000
So I have no idea .. I first helped because you asked for RUU.
Lets wait if anyone else will come to help for other problem
@redpoint73 - if you are around .. maybe you can help to confirm whether this device is AT&T or Developer Edition.
I have a feeling this is an AT&T converted to DEV ED and re S-On
@tapuz12ewq
Another possibility is your device is a AT&T originally .. you also can install RUU for AT&T, only thing is there is no Marshmallow update yet for AT&T - you can get the RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Thanks,
so I little bit confused , to fix it , which RUU are safe to install , 4.28.502.2 or 6.12.1540.4 ?
6.12.1540.4 definitely won't work, you'll get error 155 unless HTC already fix the RUU.
You can only try either 4.16.1540.8 or 4.28.502.2 and I'm not so sure whether installing 4.28.502.2 will success or not because your current version is 4.16.1540.8
another RUU that you can try is 4.17.1540.9 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_446501_signed_2.exe
Or ... S-Off the device with SunShine app (USD25) then you can fix it with any RUU.
I got to rest now ... it's 3 AM here ... good luck
ckpv5 said:
6.12.1540.4 definitely won't work, you'll get error 155 unless HTC already fix the RUU.
You can only try either 4.16.1540.8 or 4.28.502.2 and I'm not so sure whether installing 4.28.502.2 will success or not because your current version is 4.16.1540.8
another RUU that you can try is 4.17.1540.9 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_446501_signed_2.exe
Or ... S-Off the device with SunShine app (USD25) then you can fix it with any RUU.
I got to rest now ... it's 3 AM here ... good luck
Click to expand...
Click to collapse
I try to enter to stock recovery menu and find on the top screen "android stock recovery LRX22C"
do you familiar with this id LRX22C ? can it cause to not get the OTA ?
Thanks
tapuz12ewq said:
I try to enter to stock recovery menu and find on the top screen "android stock recovery LRX22C"
do you familiar with this id LRX22C ? can it cause to not get the OTA ?
Thanks
Click to expand...
Click to collapse
That's stock recovery for lollipop.
LRX22C - Android 5.0.1
LRX22G - Android 5.0.2
So which of the RUU that your tried ? I have a feeling that both will fail unless the device is S-Off again. The previous owner shouldn't change the S-Off status unless he put all the correct CID/MID to the device.
Maybe it needs the actual CID BS_US001 instead of 11111111 to get the OTA, personally I never have any problem with 11111111
ckpv5 said:
That's stock recovery for lollipop.
LRX22C - Android 5.0.1
LRX22G - Android 5.0.2
So which of the RUU that your tried ? I have a feeling that both will fail unless the device is S-Off again. The previous owner shouldn't change the S-Off status unless he put all the correct CID/MID to the device.
Maybe it needs the actual CID BS_US001 instead of 11111111 to get the OTA, personally I never have any problem with 11111111
Click to expand...
Click to collapse
yes, installed successfully 4.17.1540.9
thank you very much
i will try to OTA later to marshmallow
tapuz12ewq said:
yes, installed successfully 4.17.1540.9
thank you very much
i will try to OTA later to marshmallow
Click to expand...
Click to collapse
after I successfully installed 4.17.1540.9 from RUU
I tried to install the marshmallow update from by OTA but it failed with the same error :
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www.htc.com"
how can I install the next update ?
It's weird that the RUU can be successfully installed but not OTA.
So .. you can try this to install next RUU 6.12.1540.4
1. Download the 6.12.1540.4 firmware - https://drive.google.com/file/d/0B4jGj3SfskzMbzBtd1R1VHlmbVU/view?usp=sharing
2. Download the 6.12.1540.4 RUU if you still don't have it - http://www.htc.com/us/support/htc-one-m8/news/
3. place the firmware.zip that you downloaded in your fastboot folder then open command prompt from your fastboot folder
4.Put your device to bootloader/fastboot mode
Run below commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot-bootloader
5. Run 6.14.1540.4 RUU
6. Done
ckpv5 said:
It's weird that the RUU can be successfully installed but not OTA.
So .. you can try this to install next RUU 6.12.1540.4
1. Download the 6.12.1540.4 firmware - https://drive.google.com/file/d/0B4jGj3SfskzMbzBtd1R1VHlmbVU/view?usp=sharing
2. Download the 6.12.1540.4 RUU if you still don't have it - http://www.htc.com/us/support/htc-one-m8/news/
3. place the firmware.zip that you downloaded in your fastboot folder then open command prompt from your fastboot folder
4.Put your device to bootloader/fastboot mode
Run below commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot-bootloader
5. Run 6.14.1540.4 RUU
6. Done
Click to expand...
Click to collapse
can I instead move from s-on to s - off with the sunshine app, maybe after that i will get the OTA ?
Yes .. that's a wise move to S-Off then you can change the CID to BS_US001 then you should be able to install OTA whenever it is available.
Also note, this 6.12.1540.4 maybe the last major update as the HTC support for major update end by March or April 2016.
ckpv5 said:
Yes .. that's a wise move to S-Off then you can change the CID to BS_US001 then you should be able to install OTA whenever it is available.
Also note, this 6.12.1540.4 maybe the last major update as the HTC support for major update end by March or April 2016.
Click to expand...
Click to collapse
BS_US001 also will keep my phone sim free ?
what about MID ?
Your phone is already SIM unlocked.
Change of CID has no effect on it.
No need to change MID as that's the Developer Ed MID
ckpv5 said:
Your phone is already SIM unlocked.
Change of CID has no effect on it.
No need to change MID as that's the Developer Ed MID
Click to expand...
Click to collapse
I not sure that it seem unlock originally , why the seller change to super cid ?
and you suspect it was at&t ?
here is my device's info can anyone help me for the damn correct ruu.exe
my device is S-OFF and have unlocked bootloader
C:\Users\5G-BiLiiSiM\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.016s
With that version number and cid it looks like your on the HTC m9 developer ruu. I'm on my phone but you can find the exe on HTC website near the bottom of the page.
http://www.htc.com/us/support/rom-downloads.html
BrownEye02 said:
With that version number and cid it looks like your on the HTC m9 developer ruu. I'm on my phone but you can find the exe on HTC website near the bottom of the page.
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
i downloaded the unlocked/developer edition RUU but it's seems like wrong because at least it's gives image error on exe
i flashed it but there is just HTC on white screen phone is on button are working but nothing else i can't using it just HTC sign on white screen
You have the super cid. My bad. I've read you should be able to run most ruu's with this but I never had any luck. I'm using team venoms cheer sheet here
https://docs.google.com/spreadsheets/d/10H7RftecZZKb5tT2zpShfYNFAfSe-imhhqtVfeMPVDA/edit#gid=0
Go to the second tab to see a key for all cids.
I still believe your on the developer version but since your s-off you can set the cid for the ruu you want to run. I
The developer cid would be BS_US001.
But someone might have a better option for you.
Your phone isnt a developer version. U can use internation ruu.
https://www.androidfilehost.com/?fid=24415232478675953
Download this. Copy it to sdcard which is formatted to fat32. Rename it to 0PJAIMG.zip. (it is zero, not O) boot it into download mode it will ask to install. Press vol up and contiune
BrownEye02 said:
You have the super cid. My bad. I've read you should be able to run most ruu's with this but I never had any luck. I'm using team venoms cheer sheet here
https://docs.google.com/spreadsheets/d/10H7RftecZZKb5tT2zpShfYNFAfSe-imhhqtVfeMPVDA/edit#gid=0
Go to the second tab to see a key for all cids.
I still believe your on the developer version but since your s-off you can set the cid for the ruu you want to run. I
The developer cid would be BS_US001.
But someone might have a better option for you.
Click to expand...
Click to collapse
i successfully opened my device but i think my efs has broken there is no signal and imei can i repair that i don't have any backups
I would believe the RUU would flashed this. You can try the international RUU per degrli43.
If you modified the CID you will need to change it back to flash that RUU.
solved thanks for all replies especially @degerli43
Hi all, my first post.
I need a little clarification on what is going on with my HTC 10 at the moment.
2 weeks ago I was running version:
Code:
(bootloader) version-main: 1.80.708.6
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__622
And I decided to check for updates after hearing about the new Android release.
To my surprise received the following error:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance
I quickly found a tutorial how to fix this. Basically I needed to flash it with stock RUU. At the same time I decided to change CID to superCID.
So here is what I did:
1. Unlocked bootloader with token file from HTCDEV. Status UNLOCKED
2. Rooted the phone using TWRP and ADB.
3. Used Sunshine to set S-OFF (as it turned out later this step was unnecessary)
4. Wrote new CID with fastboot
5. Downloaded signed RUU 2PS6IMG_PERFU[email protected]60331_39.13_F_release_478389_signed_2_4.zip and flashed it.
6. Phone was back to 1.53.708.4
7. OTA now works and pushing updates.
8. Right now phone is on 2.41.708.3
Code:
INFOmax-download-size: 1579200000
INFOcurrent-slot:*
INFOversion-main: 2.41.708.3
INFOboot-mode: download
INFOversion-baseband: [email protected]
INFOversion-bootloader: 1.0.0.0000
INFOmid: 2PS620000
INFOcid: 11111111
And here is my problem. At the moment phone is in:
Code:
*** UNLOCKED ***
*** S-OFF ***
When I run fastboot oem lock I get the following:
Code:
/fastboot-mac oem lock
... INFO[KillSwitch] : /dev/block/bootdevice/by-name/frp
INFO[KillSwitch] Last Byte is 0X00, disable unlock
INFO[KillSwitch] oem unlock Turn Off!
OKAY
The bootloader seems to be unlocked
Also, I was under impression that if I flash it with stock firmware the S-OFF will change into S-ON but it has not. How do I change it without wiping? Would you recommend to leave it S-OFF? Are there any risks? Despite the fact it's unlocked and S-OFF it runs very smooth on the latest update.
Thanks in advance.
You will always have to wipe. Nothing you can do about that.
payero3491 said:
Hi all, my first post.
I need a little clarification on what is going on with my HTC 10 at the moment.
2 weeks ago I was running version:
And I decided to check for updates after hearing about the new Android release.
To my surprise received the following error:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance
I quickly found a tutorial how to fix this. Basically I needed to flash it with stock RUU. At the same time I decided to change CID to superCID.
So here is what I did:
1. Unlocked bootloader with token file from HTCDEV. Status UNLOCKED
2. Rooted the phone using TWRP and ADB.
3. Used Sunshine to set S-OFF (as it turned out later this step was unnecessary)
4. Wrote new CID with fastboot
5. Downloaded signed RUU 2PS6IMG_PERFU[email protected]60331_39.13_F_release_478389_signed_2_4.zip and flashed it.
6. Phone was back to 1.53.708.4
7. OTA now works and pushing updates.
8. Right now phone is on 2.41.708.3
And here is my problem. At the moment phone is in:
When I run fastboot oem lock I get the following:
The bootloader seems to be unlocked
Also, I was under impression that if I flash it with stock firmware the S-OFF will change into S-ON but it has not. How do I change it without wiping? Would you recommend to leave it S-OFF? Are there any risks? Despite the fact it's unlocked and S-OFF it runs very smooth on the latest update.
Thanks in advance.
Click to expand...
Click to collapse
Not sure about the bootloader lock, but you paid for s-off, no need to go back to s-on unless you want to send the phone in for warranty. Keep it as is, no risk if you just keep it to basics like flashing Roms and kernels. If you don't trust yourself and still need to go back to S-ON, it's done using a fastboot command. Look here:
https://forum.xda-developers.com/htc-10/how-to/guide-safely-set-bootloader-to-locked-t3386456
The above link will also show you how to lock your bootloader with Sunshine. The phone will not s-on itself just from flashing a stock rom.
Also I'm not sure why you even had to change your CID.
And you don't need to ruu each time to take an Ota. You just need to be in an untouched state, meaning restore system image + recovery, and not have superCID. Ruu is a sure way, but is not necessary if the above works for you.
payero3491 said:
Hi all, my first post.
I need a little clarification on what is going on with my HTC 10 at the moment.
2 weeks ago I was running version:
Code:
(bootloader) version-main: 1.80.708.6
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__622
And I decided to check for updates after hearing about the new Android release.
To my surprise received the following error:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance
I quickly found a tutorial how to fix this. Basically I needed to flash it with stock RUU. At the same time I decided to change CID to superCID.
So here is what I did:
1. Unlocked bootloader with token file from HTCDEV. Status UNLOCKED
2. Rooted the phone using TWRP and ADB.
3. Used Sunshine to set S-OFF (as it turned out later this step was unnecessary)
4. Wrote new CID with fastboot
5. Downloaded signed RUU 2PS6IMG_PERFU[email protected]60331_39.13_F_release_478389_signed_2_4.zip and flashed it.
6. Phone was back to 1.53.708.4
7. OTA now works and pushing updates.
8. Right now phone is on 2.41.708.3
Code:
INFOmax-download-size: 1579200000
INFOcurrent-slot:*
INFOversion-main: 2.41.708.3
INFOboot-mode: download
INFOversion-baseband: [email protected]
INFOversion-bootloader: 1.0.0.0000
INFOmid: 2PS620000
INFOcid: 11111111
And here is my problem. At the moment phone is in:
Code:
*** UNLOCKED ***
*** S-OFF ***
When I run fastboot oem lock I get the following:
Code:
/fastboot-mac oem lock
... INFO[KillSwitch] : /dev/block/bootdevice/by-name/frp
INFO[KillSwitch] Last Byte is 0X00, disable unlock
INFO[KillSwitch] oem unlock Turn Off!
OKAY
The bootloader seems to be unlocked
Also, I was under impression that if I flash it with stock firmware the S-OFF will change into S-ON but it has not. How do I change it without wiping? Would you recommend to leave it S-OFF? Are there any risks? Despite the fact it's unlocked and S-OFF it runs very smooth on the latest update.
Thanks in advance.
Click to expand...
Click to collapse
Hello!
Could you share the link you downloaded RUU 1.53.708.4? Really appreciate that!
Thank you.
lilrice said:
Hello!
Could you share the link you downloaded RUU 1.53.708.4? Really appreciate that!
Thank you.
Click to expand...
Click to collapse
**Previously posted link deleted**
xunholyx said:
https://forum.halabtech.com/vb/show...0013-60331_39-13_F_release_4-78389_signed_2_4
Click to expand...
Click to collapse
Hello,
I registered an account on this website, but it says that this file is "featured" and free account cannot download it.
Appreciate your help any way.
If someone could re-upload it somewhere else, it would be nice.
Best regards
lilrice said:
Hello,
I registered an account on this website, but it says that this file is "featured" and free account cannot download it.
Appreciate your help any way.
If someone could re-upload it somewhere else, it would be nice.
Best regards
Click to expand...
Click to collapse
I never realized it was one of those sites you have to pay at. Sorry.
Use this link instead
xunholyx said:
I never realized it was one of those sites you have to pay at. Sorry.
Use this link instead
Click to expand...
Click to collapse
I found and downloaded this file and also the file 1.21.708. on androidfilehost of Stifilz already, but both ZIP files are corrupted, dont know why, but both PC and my phone say so. Thats why im looking for another hosts.
Thanks sir you are nice
lilrice said:
I found and downloaded this file and also the file 1.21.708. on androidfilehost of Stifilz already, but both ZIP files are corrupted, dont know why, but both PC and my phone say so. Thats why im looking for another hosts.
Thanks sir you are nice
Click to expand...
Click to collapse
There not corrupted there signed.
I flashed it any way
It worked! Thank you ! Very happy to go back to MM
Cheers
Hi all,
Trying to return this phone to stock to use since my HTC 10 is playing up and not sure what to buy as a replacement, yet.
Anyway, it's soft bricked and unable to flash the RUU as it gives a Failed (remote: 22) error.
I believe it's because it has updated hboot and it can now no longer read the encrypted rom. To fix it I (think) need a ORANG001 OTA to flash. I have tried a Europe one but that fails.
Anyone know where I can get one?
Or how would I get SuperCID so I can flash any?
My knowledge falls down here so any help would be great
Bootloader is relocked.
Version: 0.5
Version-bootloader: 3.19.0.0000
Version-baseband: [email protected]
Version-main:
Version-misc: PVT SHIP S-ON
Product: m8ql_ul
Modelid: 0PKV10000
cidnu: ORANG001
Click to expand...
Click to collapse
Hello,
I think you have to:
- Unlock and S-OFF again your bootloader
- Try to downgrade it
- Flash ORANG001 CID through fastboot command prompt
- Flash through official RUU (or install the 0P6BIMG.zip that you can find inside from the bootloader)
- Maybe relock the bootloader if you want
You can take a look at this post for giving you an idea on how to downgrade (be careful that proposed ROMs are for Verizon M8 and won't work for yours):
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Hi John, I don't think we can S-OFF the M8s. It's not the same as the M8.