Can't update My device - One (M8) Q&A, Help & Troubleshooting

My HTC one m8 is S-OFF and it is SuperCID(11111111), I'm running the software 4.16.1540.8. I received a message to update my device and when try to do that, I get the 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...". Is there a way I can update my phone ?

MotoXor said:
My HTC one m8 is S-OFF and it is SuperCID(11111111), I'm running the software 4.16.1540.8. I received a message to update my device and when try to do that, I get the 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...". Is there a way I can update my phone ?
Click to expand...
Click to collapse
sorry cant help / suggest something that can help you as i am new also

MotoXor said:
My HTC one m8 is S-OFF and it is SuperCID(11111111), I'm running the software 4.16.1540.8. I received a message to update my device and when try to do that, I get the 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...". Is there a way I can update my phone ?
Click to expand...
Click to collapse
Wrong MID

The same me
My phone S-ON, supercid 11111111,MID 0P6B1000, I installed ROM 4.19.707.2, now I can't update ota to 4.19.707.4, I don't know CID or MID is reason I can't ota update, I can't change CID or MID because my phone S-ON

ckpv5 said:
Wrong MID
Click to expand...
Click to collapse
What do you mean by MID ? Are you referring to the super CID ? Do you suggest another CID ?

MotoXor said:
What do you mean by MID ? Are you referring to the super CID ? Do you suggest another CID ?
Click to expand...
Click to collapse
CID and MID are two different things.
Your SuperCID is good for any version but MID must be correct.
For 4.16.1540.8, the correct MID 0P6B12000 or 0P6B13000 for OTA to work.
Your current one most probably not these MID.
Boot to bootloader and check your current MID. Run command fastboot getvar mid
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
shotokan2011 said:
The same me
My phone S-ON, supercid 11111111,MID 0P6B1000, I installed ROM 4.19.707.2, now I can't update ota to 4.19.707.4, I don't know CID or MID is reason I can't ota update, I can't change CID or MID because my phone S-ON
Click to expand...
Click to collapse
Your MID is wrong for 4.19.707.2. The correct MID is 0P6B11000.
Your current MID 0P6B10000 is EU WWE version not Asia WWE.
How do you change to SuperCID ? It must have S-Off before.
Your current CID/MID combination is meant for EU WWE 4.16.401.10 then OTA to 4.16.401.13

Yes, I buy used phone that have supercid but S-ON, I flash RUU 4.19.707.2 to have Vietnamese language but can't update ota. So, can I reflash ROM 4.16.401.10 and update ota to 4.16.401.13 ? Thanks
ckpv5 said:
Your MID is wrong for 4.19.707.2. The correct MID is 0P6B11000.
Your current MID 0P6B10000 is EU WWE version not Asia WWE.
How do you change to SuperCID ? It must have S-Off before.
Your current CID/MID combination is meant for EU WWE 4.16.401.10 then OTA to 4.16.401.13
Click to expand...
Click to collapse

shotokan2011 said:
Yes, I buy used phone that have supercid but S-ON, I flash RUU 4.19.707.2 to have Vietnamese language but can't update ota. So, can I reflash ROM 4.16.401.10 and update ota to 4.16.401.13 ? Thanks
Click to expand...
Click to collapse
You flashed 4.19.707.2 RUU or you restored a backup ? AFAIK RUU 4.19.707.2 won't run your device.
If the 4.16.401.10 is non-rooted ROM, yes you can do OTA to 4.16.401.13.
Later if you want, you can restore a backup 4.19.707.4 (I don't remember 4.16.401.x has Vietnamese language or not). You should see 4.19.707.4 backup in my thread later tonight or tomorrow - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

I flash RUU.exe 4.19.707.2 while old version is xx.401.xx, CID is 11111111, S-ON It's run good and I've used for 1 month Yesterday OTA have 4.19.707.4 I can't update, I think because my CID or MID number. This is my info about phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH52DWM01xxx
(bootloader) imei: 357336064xxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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
ckpv5 said:
You flashed 4.19.707.2 RUU or you restored a backup ? AFAIK RUU 4.19.707.2 won't run your device.
If the 4.16.401.10 is non-rooted ROM, yes you can do OTA to 4.16.401.13.
Later if you want, you can restore a backup 4.19.707.4 (I don't remember 4.16.401.x has Vietnamese language or not). You should see 4.19.707.4 backup in my thread later tonight or tomorrow - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse

ckpv5 said:
CID and MID are two different things.
Your SuperCID is good for any version but MID must be correct.
For 4.16.1540.8, the correct MID 0P6B12000 or 0P6B13000 for OTA to work.
Your current one most probably not these MID.
Boot to bootloader and check your current MID. Run command fastboot getvar mid
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
You're right. My MID is 0P6B10000. How do I change it to 0P6B12000 ?
Click to expand...
Click to collapse

shotokan2011 said:
I flash RUU.exe 4.19.707.2 while old version is xx.401.xx, CID is 11111111, S-ON It's run good and I've used for 1 month Yesterday OTA have 4.19.707.4 I can't update, I think because my CID or MID number.
Click to expand...
Click to collapse
OK .. never see a successful run of Asia WWE RUU on a EU WWE MID before.
Anyway .. you just confirm the original is x.xx.401.x. So if you flash a x.xx.401.x then you can do OTA to x.xx.401.x with no problem as long as the ROM is not rooted.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
MotoXor said:
You're right. My MID is 0P6B10000. How do I change it to 0P6B12000 ?
Click to expand...
Click to collapse
See this thread on how-to : http://forum.xda-developers.com/showthread.php?t=2708581

ckpv5 said:
OK .. never see a successful run of Asia WWE RUU on a EU WWE MID before.
Anyway .. you just confirm the original is x.xx.401.x. So if you flash a x.xx.401.x then you can do OTA to x.xx.401.x with no problem as long as the ROM is not rooted.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
See this thread on how-to : http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
I can't seem to find the code to change the developer edition. All codes are listed but mine :crying:

MotoXor said:
I can't seem to find the code to change the developer edition. All codes are listed but mine :crying:
Click to expand...
Click to collapse
-AT&T, unlocked, developer MID:

ckpv5 said:
-AT&T, unlocked, developer MID:
Click to expand...
Click to collapse
Thank you so much, that might help. I'll try that once I finish my issue with the adb shell since it doesn't show my device.

MotoXor said:
Thank you so much, that might help. I'll try that once I finish my issue with the adb shell since it doesn't show my device.
Click to expand...
Click to collapse
It finally worked. I appreciate your help

Hi,
I tried reinstalling ROM 4.16.401.10 (RUU.EXE) but it was an "error 140 bootloader version". I tried to recovery using TWRP as your post is restored version 4.16.401.10 but the information in OS bootloader is 4.19.707.2 and I still can not update via OTA, I restored by 4:19 .707.4 is ok but information in bootloader OS still 4.19.707.2. I do not understand why my current phone S-ON, supercid 11111111, MID 0P6B1000 can not install ROM RUU.EXE 401 , you can help me? I think that by version HBoot 319 is high? Can I fix this problem without S-OFF to downgrade HBboot, change CID,change MID?
ckpv5 said:
You flashed 4.19.707.2 RUU or you restored a backup ? AFAIK RUU 4.19.707.2 won't run your device.
If the 4.16.401.10 is non-rooted ROM, yes you can do OTA to 4.16.401.13.
Later if you want, you can restore a backup 4.19.707.4 (I don't remember 4.16.401.x has Vietnamese language or not). You should see 4.19.707.4 backup in my thread later tonight or tomorrow - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse

shotokan2011 said:
Hi,
I tried reinstalling ROM 4.16.401.10 (RUU.EXE) but it was an "error 140 bootloader version". I tried to recovery using TWRP as your post is restored version 4.16.401.10 but the information in OS bootloader is 4.19.707.2 and I still can not update via OTA, I restored by 4:19 .707.4 is ok but information in bootloader OS still 4.19.707.2. I do not understand why my current phone S-ON, supercid 11111111, MID 0P6B1000 can not install ROM RUU.EXE 401 , you can help me? I think that by version HBoot 319 is high? Can I fix this problem without S-OFF to downgrade HBboot, change CID,change MID?
Click to expand...
Click to collapse
Can you post your fastboot getvar all result (minus serial & imei no) ? I don't see in any of your previous post. Then we'll see what we can do.

Hi, This my phone information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH52DWMxxxx
(bootloader) imei: 3573360644xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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.008s
ckpv5 said:
Can you post your fastboot getvar all result (minus serial & imei no) ? I don't see in any of your previous post. Then we'll see what we can do.
Click to expand...
Click to collapse

I'm scare nothing much can be done without S-Off. Seems like you have the Asian WEE bootloader with wrong MID and that's why the 4.16.401.10 RUU failed to run
Have you try to run the SunShine apk and see whether it asks for payment ? If the previous owner use SunShine to S-Off, no payment is required for the second time.
(you need a rooted stock ROM for that)
You can't downgrade hboot without S-Off.
I still feel strange that you managed to run 4.19.707.2 RUU on a x.xx.401.x before.

Okay, I'll try to Re S-OFF because I've buy an old devide
ckpv5 said:
I'm scare nothing much can be done without S-Off. Seems like you have the Asian WEE bootloader with wrong MID and that's why the 4.16.401.10 RUU failed to run
Have you try to run the SunShine apk and see whether it asks for payment ? If the previous owner use SunShine to S-Off, no payment is required for the second time.
(you need a rooted stock ROM for that)
You can't downgrade hboot without S-Off.
I still feel strange that you managed to run 4.19.707.2 RUU on a x.xx.401.x before.
Click to expand...
Click to collapse

Related

How can I update my bootloader?

I'm on Paranoid ROM (last).
Bootloader 3.16.
I would like 3.19 or .18 in order to use Android 5.0 (CM 12).
Miqueas111 said:
I'm on Paranoid ROM (last).
Bootloader 3.16.
I would like 3.19 or .18 in order to use Android 5.0 (CM 12).
Click to expand...
Click to collapse
What exact variant do you have and have you achieved S-OFF yet ?
jball said:
What exact variant do you have and have you achieved S-OFF yet ?
Click to expand...
Click to collapse
I have the 3.16 bootloader, and I have no idea of S-OFF, so i guess I'm S-ON .
Miqueas111 said:
I have the 3.16 bootloader, and I have no idea of S-OFF, so i guess I'm S-ON .
Click to expand...
Click to collapse
Don't guess. Boot into bootloader, and it will say either s-on or s-off near the top.
By variant, jball is asking what carrier version or CID.
Flash the proper firmware package for your CID, if its in the collection:
http://forum.xda-developers.com/showthread.php?t=2696282
Or alternately return to stock ROM and stock recovery, than official OTA to update to hboot 3.17 then 3.19.
http://forum.xda-developers.com/showthread.php?t=2701376
redpoint73 said:
Don't guess. Boot into bootloader, and it will say either s-on or s-off near the top.
By variant, jball is asking what carrier version or CID.
Flash the proper firmware package for your CID, if its in the collection:
http://forum.xda-developers.com/showthread.php?t=2696282
Or alternately return to stock ROM and stock recovery, than official OTA to update to hboot 3.17 then 3.19.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I'm having the same issue as the OP. Trying to get to Lollipop from the latest Paranoid Android ROM. Here's the output of fastboot getvar all in the spoiler. Can you please tell me exactly what to do, in what order, and what specific files to flash in order to get my phone updated to a 5.0 ROM? I've been trying to follow this post, but something's just not clicking for me. I've already bricked my phone to the point where flashing the RUU from HTCDev was the only thing that'd save it - two separate times. Believe I am s-off, with TWRP 2.7.0.1 installed, but on the AT&T Stock ROM 1.58.502.1. Checked for OTAs, and I'm apparently up to date...
Code:
C:\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43NWM03051
(bootloader) imei: 358718050169510
(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: 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.020s
C:\One_M8_All-In-One_Kit_v\data>
@bassitone
How does anyone not know if they are S-OFF/S-ON ?
Did you buy your phone second hand ?
Do you know how to boot into hboot/bootlooader mode witch will inform you if your S-OFF or S-ON
Have you tried an up to date twrp cause the one your on is very old.
At&t is furthest from receiving OTA's in my opinion
jball said:
@bassitone
How does anyone not know if they are S-OFF/S-ON ?
Did you buy your phone second hand ?
Do you know how to boot into hboot/bootlooader mode witch will inform you if your S-OFF or S-ON
Have you tried an up to date twrp cause the one your on is very old.
At&t is furthest from receiving OTA's in my opinion
Click to expand...
Click to collapse
His fastboot getvar all output clearly states SECURITY - OFF ...... so he has an S-OFF device.
Mr Hofs said:
His fastboot getvar all output clearly states SECURITY - OFF ...... so he has an S-OFF device.
Click to expand...
Click to collapse
Right, yet he still states
"I believe I'm S-OFF"
jball said:
Right, yet he still states
"I believe I'm S-OFF"
Click to expand...
Click to collapse
Because I wasn't sure if something I did yesterday managed to undo my s-off status. First HTC device, and I went pretty far in restoring to stock
Thread cleaned.
Keep it CIVIL please.
bassitone said:
I'm having the same issue as the OP. Trying to get to Lollipop from the latest Paranoid Android ROM. Here's the output of fastboot getvar all in the spoiler. Can you please tell me exactly what to do, in what order, and what specific files to flash in order to get my phone updated to a 5.0 ROM? I've been trying to follow this post, but something's just not clicking for me. I've already bricked my phone to the point where flashing the RUU from HTCDev was the only thing that'd save it - two separate times. Believe I am s-off, with TWRP 2.7.0.1 installed, but on the AT&T Stock ROM 1.58.502.1. Checked for OTAs, and I'm apparently up to date...
Click to expand...
Click to collapse
I would suggest the following thread, which has explicit step-by-step instruction on how to update firmware:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
"3.28.1540 firmware only" file is what you want.

[Q] AT&T M8. Worst case scenario, basically. Phone recoverable?

****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.
BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.

[Q] Help needed! Red exclamation mark

I have Htc one m8 unlocked bootloader 3.19, was rooted but doesn't seem to be anymore. firmware is 4.16.401.10, supercid (was roger001). I'm not sure what I am doing wrong, I tried to flash a RUU after flashing the firmware first and i get an error 32-header error. Phone just reboots onto white HTC screen then gives me the red exclamation mark. Booting into recovery gives red exclamation mark. Not sure what else I can try, any suggestioins would be greatly appreciated. (note: tried to flash the RUU here I could be way off but I am stuck.)
Anyone have any assistance? I tried changed the mid so I could flash a RUU but still got the 32-header error. There has to be a simpler way to do this, I just want to get back to stock.
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong. I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work. I'll post that info in one sec
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Kevinj17 said:
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong.
Click to expand...
Click to collapse
Yes, that is incorrect. CID and MID need to match what the RUU is looking for. SuperCID will pass the CID check. But the MID check will still fail if you try to run the Euro RUU (MID = 06PB10000) on a Rogers version M8 (MID = 06PB16000).
Also, are you actually using the phone on Rogers' network? If so, I do not think that returning to stock Euro WWE version by RUU is what you want. From this webpage, it looks like Rogers uses Bands 4,7, and 17 for LTE. The Euro RUU will install a full stock image, including radio firmware, and according to these specs, the Euro version (EMEA) is missing 2 of the 3 bands (Bands 4 and 17) needed for LTE to work on Rogers network.
Kevinj17 said:
I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work.
Click to expand...
Click to collapse
What zip did you try to flash exactly?
---------- Post added at 09:41 AM ---------- Previous post was at 09:23 AM ----------
Kevinj17 said:
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Click to expand...
Click to collapse
That would just be the actual stock recovery program that installs of OTA updates, etc.
Its not the actual stock OS or firmware, if that is what you are thinking.
The red exclamation indicates you are already on a stock recovery. Flashing this won't help you at all.
Yeah haha I figured that out right after posting. Thanks though. I re-flashed TWRP now and gonna try restoring from a nandrod backup i found then flash the matching firmware. see how that goes. The similiar names is what throws me off sometimes, so many different recoverys n sh*t lol
I was tryign to use a sixaxis controller to play games but kept getting and error about 'position executable variables' when loading the sixaxis app so i downloaded something called 'bypass pie' and flashed it. Clearly i should have backed up first. It was just inpatient, but it unrooted my phone and stuff so i tried to restore from a backuop like 2 weeks ago and it was corrupt so it messed things up

my htc one_M8 didnot recived lollipop update ! ! ! help pleas.

Hi there I am new to HTC this is my firs HTC phone. I have HTC one m8 device with android 4.4.4 kit Kat and I want to update it to android 5 lollipop . when I go to settings and checking for updates it says (your phone is up to date there are no updates available for your phone ) I also tried HTC sync manger but with no luck so far .
So why there is no updates for my phone ?? ( I am not rooted or unlocked the boot loader)
Any way to download the Rom and install it via pc ?? (Program like Odin To install roms to htc ).
I am sorry for the bad English language because it's not my nature language .
kirkuk said:
Hi there I am new to HTC this is my firs HTC phone. I have HTC one m8 device with android 4.4.4 kit Kat and I want to update it to android 5 lollipop . when I go to settings and checking for updates it says (your phone is up to date there are no updates available for your phone ) I also tried HTC sync manger but with no luck so far .
So why there is no updates for my phone ?? ( I am not rooted or unlocked the boot loader)
Any way to download the Rom and install it via pc ?? (Program like Odin To install roms to htc ).
I am sorry for the bad English language because it's not my nature language .
Click to expand...
Click to collapse
Post the results of fastboot getvar all Delete the serial# and IMEI from the output. That is private information.
There may be an RUU that you could run to update, and your getvar will give the information that is needed to determine that.
xunholyx said:
Post the results of fastboot getvar all Delete the serial# and IMEI from the output. That is private information.
There may be an RUU that you could run to update, and your getvar will give the information that is needed to determine that.
Click to expand...
Click to collapse
thank you bro for replay i appreciate that ....
this the result of ( fastboot getvar all ) .
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.36.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
kirkuk said:
thank you bro for replay i appreciate that ....
this the result of ( fastboot getvar all ) .
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.36.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
I'm not sure that Lollipop is even available for the Middle East/Egyptian model. Your best bet would be to spend $25 for Sunshine S-Off, convert to superCID, and update with WWE/International firmware. You could also try to change your MID to 0P6B10000 and update that way, but there is a very real risk of bricking if you do that.
---------- Post added at 07:48 PM ---------- Previous post was at 07:22 PM ----------
You could also try this. No guarantees that it will work, but it might (your CID is listed as compatible, but the MID makes me wonder). You won't brick, you will just get error ouputs if it doesn't
Download this RUU.zip
Rename it to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your extSD.
Boot into bootloader and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash, power button to reboot)
That's it.
After you are done make sure to delete the renamed file from your SD card, otherwise every time you boot to bootloader it will try tro update again.
Good luck!
xunholyx said:
I'm not sure that Lollipop is even available for the Middle East/Egyptian model. Your best bet would be to spend $25 for Sunshine S-Off, convert to superCID, and update with WWE/International firmware. You could also try to change your MID to 0P6B10000 and update that way, but there is a very real risk of bricking if you do that.
---------- Post added at 07:48 PM ---------- Previous post was at 07:22 PM ----------
You could also try this. No guarantees that it will work, but it might (your CID is listed as compatible, but the MID makes me wonder). You won't brick, you will just get error ouputs if it doesn't
Download this RUU.zip
Rename it to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your extSD.
Boot into bootloader and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash, power button to reboot)
That's it.
After you are done make sure to delete the renamed file from your SD card, otherwise every time you boot to bootloader it will try tro update again.
Good luck!
Click to expand...
Click to collapse
thank you so much bro .
i will try that RUU and see if it worked and let you know. but i have a few questions .
1-do you think that update will effect on the radio or IMEI number ??
2-do i receive updates in the future ??
thanks again for helping me .
kirkuk said:
thank you so much bro .
i will try that RUU and see if it worked and let you know. but i have a few questions .
1-do you think that update will effect on the radio or IMEI number ??
2-do i receive updates in the future ??
thanks again for helping me .
Click to expand...
Click to collapse
Your radio version is the same as mine, and I'm on WWE so there is nothing to worry about there. You won't receive OTA updates MID. You can still update via RUU when the next version comes out, or you can get S-Off and just flash the firmware. I should have already let you know; and I am sorry that I forgot to mention it; but the RUU will wipe your phone so make sure you backup everything that is important to you. Make a backup to your extSD. That won't get wiped.
xunholyx said:
Your radio version is the same as mine, and I'm on WWE so there is nothing to worry about there. You won't receive OTA updates MID. You can still update via RUU when the next version comes out, or you can get S-Off and just flash the firmware. I should have already let you know; and I am sorry that I forgot to mention it; but the RUU will wipe your phone so make sure you backup everything that is important to you. Make a backup to your extSD. That won't get wiped.
Click to expand...
Click to collapse
a very big thanks to you bro i bothered you with my problem and questions and appreciate every word you wrote .it is ok that you didnot mentioned it will wipe my phone because i backed it up before .
xunholyx said:
Your radio version is the same as mine, and I'm on WWE so there is nothing to worry about there. You won't receive OTA updates MID. You can still update via RUU when the next version comes out, or you can get S-Off and just flash the firmware. I should have already let you know; and I am sorry that I forgot to mention it; but the RUU will wipe your phone so make sure you backup everything that is important to you. Make a backup to your extSD. That won't get wiped.
Click to expand...
Click to collapse
Hi. I don't mean to hijack this post or whatever but I have the same problem with the same MID and CID. I bought the phone from Riyadh and I am not receiving any OTA. I tried that RUU and it failed giving me the following error:
Code:
Model ID incorrect!
Update Fail!
Device halted due to Large Image update fail!
Press <POWER> to reboot.
EDIT: I did get the Stagefright fix by OTA if that helps somehow.
muftiazan said:
Hi. I don't mean to hijack this post or whatever but I have the same problem with the same MID and CID. I bought the phone from Riyadh and I am not receiving any OTA. I tried that RUU and it failed giving me the following error:
Code:
Model ID incorrect!
Update Fail!
Device halted due to Large Image update fail!
Press <POWER> to reboot.
EDIT: I did get the Stagefright fix by OTA if that helps somehow.
Click to expand...
Click to collapse
Yeah, I had a feeling that might happen.
xunholyx said:
Yeah, I had a feeling that might happen.
Click to expand...
Click to collapse
if i got same error did my phone will start as nothing happend and boots normal or i have to install new rom ??
kirkuk said:
if i got same error did my phone will start as nothing happend and boots normal or i have to install new rom ??
Click to expand...
Click to collapse
It'll boot up fine. Don't worry.
xunholyx said:
It'll boot up fine. Don't worry.
Click to expand...
Click to collapse
bro its failed and i got the same error as mentioned above . my device boot normal.thank you.
I hava the same problem. The Ruu you just provided was from the htc official rom downloads page right?
And, will this model effect the custom roms to be flashed?like would i be able to flash arhd on it (the same mid as OP and unlocked) without bricking it?
I thought samsung's variantd were insane but htc is driving me nuts ?
eatsleep said:
I hava the same problem. The Ruu you just provided was from the htc official rom downloads page right?
And, will this model effect the custom roms to be flashed?like would i be able to flash arhd on it (the same mid as OP and unlocked) without bricking it?
I thought samsung's variantd were insane but htc is driving me nuts ��
Click to expand...
Click to collapse
bro i am new to htc so i donot know much about htc and installing roms because i switched from samsung to htc . i think that RUU was official from htc but its failed to install on my htc one m8 because my device is made for middle east .i donot know if you can install it on your device or install custom roms on it .
eatsleep said:
I hava the same problem. The Ruu you just provided was from the htc official rom downloads page right?
And, will this model effect the custom roms to be flashed?like would i be able to flash arhd on it (the same mid as OP and unlocked) without bricking it?
I thought samsung's variantd were insane but htc is driving me nuts ��
Click to expand...
Click to collapse
It's a zip made from the official RUU.
It won't affect which ROMs you can flash.
If you have the same model as the OP, it won't work. You will need to get S-Off and change your MID first.
xunholyx said:
It'll boot up fine. Don't worry.
Click to expand...
Click to collapse
sorry bro for bothering you but is it safe to try this RUU
http://www.htc.com/us/support/htc-one-m8/news/
from htc website to update my phone ?? what happens if it fail to update ??
Hi there ...i have recived official OTA update android (5.0.2) in 11/26/2015 . Thanks to all of you .
kirkuk said:
sorry bro for bothering you but is it safe to try this RUU
http://www.htc.com/us/support/htc-one-m8/news/
from htc website to update my phone ?? what happens if it fail to update ??
Click to expand...
Click to collapse
I see you issue solved itself. But just FYI, the above RUU would not have worked on your phone. You can't just run any RUU, it needs to match your carrier ID (CID) and model ID (MID). You can change CID and MID, but only with s-off.
redpoint73 said:
I see you issue solved itself. But just FYI, the above RUU would not have worked on your phone. You can't just run any RUU, it needs to match your carrier ID (CID) and model ID (MID). You can change CID and MID, but only with s-off.
Click to expand...
Click to collapse
thank u for sharing us your experience .. the above RUU did not installed on my phone for the reasons that you wrote above ..i will try change the CID and MID to change my phone to GPE in the future if my phone not received the marshmallow update ...
i want 3.36.401.4 stock recovery my phone is rooted and i have the ota update so my phone is not updating

M8 Bricked while updating to Marshmallow.

Hi,
The other day i've tried to update my M8 to marshmallow via OTA and my device get bricked . . .
It is stucked on Android Recovery, and have tried everything. Ruu's, factory reset . . . everything. Ruu always gives me back error 155.
Don't know what else to do. It is new, but I think the people that sold it to me have changed things like CID and it have S-OFF.
I'll post the "fastboot getvar all" command results:
E:\Minimal ADB and Fastboot>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-OFF
(bootloader) serialno:
(bootloader) imei: ---------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can someone help me? :crying: Thanks!
I am having the same problem!! I installed the official update via the system update, installed then at the end it told me there is a problem with the OTA thing and that is it. Since then my device is bricked and I'm in between the recovery menu and the bootloader.
I don't wanna root my device and didn't try it. This sucks. I wish I can rollback this mess to Lollipop.
Moe88Saber said:
I am having the same problem!! I installed the official update via the system update, installed then at the end it told me there is a problem with the OTA thing and that is it. Since then my device is bricked and I'm in between the recovery menu and the bootloader.
I don't wanna root my device and didn't try it. This sucks. I wish I can rollback this mess to Lollipop.
Click to expand...
Click to collapse
I had a similar issue, bricked my HTC ONE M8 by updating through OTA.
But I got it fixed by flashing RUU through htc_fastboot.exe, it took a while but was effective.
In your case, if you need to find your right CID, first get your mid number and check if you can find a right CID to your MID, then write it through fastboot. Hope it can help you.
If you will need a detailed how to, let me know
azbtaurus said:
I had a similar issue, bricked my HTC ONE M8 by updating through OTA.
But I got it fixed by flashing RUU through htc_fastboot.exe, it took a while but was effective.
In your case, if you need to find your right CID, first get your mid number and check if you can find a right CID to your MID, then write it through fastboot. Hope it can help you.
If you will need a detailed how to, let me know
Click to expand...
Click to collapse
My CID is 11111111, it says so in the bootloader. Can you provide links on where to get the RUU and the flashing app? Thanks
The bootloader says LOCKED yet my device is the international variant. Is it related or does it mean that my bootloader is locked?
ramajo17 said:
Hi,
The other day i've tried to update my M8 to marshmallow via OTA and my device get bricked . . .
It is stucked on Android Recovery, and have tried everything. Ruu's, factory reset . . . everything. Ruu always gives me back error 155.
Don't know what else to do. It is new, but I think the people that sold it to me have changed things like CID and it have S-OFF.
I'll post the "fastboot getvar all" command results:
E:\Minimal ADB and Fastboot>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-OFF
(bootloader) serialno: FA44WWM07312
(bootloader) imei: ---------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can someone help me? :crying: Thanks!
Click to expand...
Click to collapse
Hey, I've made a simple research and found that your serial number belongs to HTC ONE M8 Taiwan version, so first you need to change your MID to 0P6B150 (optional but strongly advised for applaying offical updates) and then the CID to CHT__601 (Taiwan).
Only after this you need to find the right RUU and flash it, or use RUU.zip and flash it through htc_fastboot.exe
Hope it will be helpfull
---------- Post added at 09:52 AM ---------- Previous post was at 09:48 AM ----------
Moe88Saber said:
My CID is 11111111, it says so in the bootloader. Can you provide links on where to get the RUU and the flashing app? Thanks
The bootloader says LOCKED yet my device is the international variant. Is it related or does it mean that my bootloader is locked?
Click to expand...
Click to collapse
Send me your detailed phone information as it was shown in the first post of the thread so I can tell you how to change you CID and other identification numbers that in the end will let you apply the update
Having the original CID is very important, cuz your bootloader was relocked? otherwise they could've not changed you CID/
Check your serial information go to HTC Warranty Check - Lookup
this tell you right region information of your phone so you can easily find right CID and MID numbers of your phone
azbtaurus said:
Send me your detailed phone information
Click to expand...
Click to collapse
Can you walk me through it? When I connect my device to my laptop, it shows nothing. the HTC sync app fails to detect my phone as well.
But my bootloader detects it. It goes from FASTBOOT to FASTBOOT USB
azbtaurus said:
Hey, I've made a simple research and found that your serial number belongs to HTC ONE M8 Taiwan version, so first you need to change your MID to 0P6B150 (optional but strongly advised for applaying offical updates) and then the CID to CHT__601 (Taiwan).
Click to expand...
Click to collapse
That is wrong .. you need to see the CID/MID not the serial no.
He can flash the 6.12.401.4 RUU zip
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
ramajo17 said:
Hi,
The other day i've tried to update my M8 to marshmallow via OTA and my device get bricked . . .
It is stucked on Android Recovery, and have tried everything. Ruu's, factory reset . . . everything. Ruu always gives me back error 155.
Don't know what else to do. It is new, but I think the people that sold it to me have changed things like CID and it have S-OFF.
I'll post the "fastboot getvar all" command results:
E:\Minimal ADB and Fastboot>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-OFF
(bootloader) serialno:
(bootloader) imei: ---------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can someone help me? :crying: Thanks!
Click to expand...
Click to collapse
1. - remove the serial no. in your above post.
2. - Is the bootloader LOCKED or RELOCKED ? If it is UNLOCKED, relock it with command fastboot oem lock
3. - follow this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4 for the driver part
and this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6 for the RUU part
Moe88Saber said:
Can you walk me through it? When I connect my device to my laptop, it shows nothing. the HTC sync app fails to detect my phone as well.
But my bootloader detects it. It goes from FASTBOOT to FASTBOOT USB
Click to expand...
Click to collapse
1 - see the links in the end of #7 post? Go there and first get the drivers and adb-fastboot tools
once you get try command fastboot getvar all this will show you the detailed information of your device
2 - once done get HTC ONE M8 all in one tool kit, it would be easier for you to use instead typing commands all the time
3 - unlock your bootloader by following the instructions on the program listed above
4 - search for right CID number of your phone and write it by using command fastboot oem writecid (YOUR CID)
5 - relock bootloader
6 - flash the right RUU (check if it is right for your original new CID)
Keep in mind that I've done this on my own devices, and I don't take any responsibility in case if you get your device bricked
ckpv5 said:
That is wrong .. you need to see the CID/MID not the serial no.
He can flash the 6.12.401.4 RUU zip
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
1. - remove the serial no. in your above post.
2. - Is the bootloader LOCKED or RELOCKED ? If it is UNLOCKED, relock it with command fastboot oem lock
3. - follow this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4 for the driver part
and this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6 for the RUU part
Click to expand...
Click to collapse
I'm not the OP but I am experiencing the same issue. anyway...my bootloader is locked and it is connected to the ADB, getvar shows me some stats. I'm now downloading the RUU and will flash it afterwards. Thanks for your help.
Moe88Saber said:
I'm not the OP but I am experiencing the same issue. anyway...my bootloader is locked and it is connected to the ADB, getvar shows me some stats. I'm now downloading the RUU and will flash it afterwards. Thanks for your help.
Click to expand...
Click to collapse
You cannot simply flash the RUU .. the first question is .. is the RUU the right one for your device ?
You have SUperCID as you mentioned above .. what about the MID ?
Is it 0P6B10000 ? If yes .. then go ahead
ckpv5 said:
You cannot simply flash the RUU .. the first question is .. is the RUU the right one for your device ?
You have SUperCID as you mentioned above .. what about the MID ?
Is it 0P6B10000 ? If yes .. then go ahead
Click to expand...
Click to collapse
Sir, If you mean the modelid, then yes, it is 0P6B10000 and cidnum is 11111111
Should I go ahead?
Moe88Saber said:
Sir, If you mean the modelid, then yes, it is 0P6B10000 and cidnum is 11111111
Should I go ahead?
Click to expand...
Click to collapse
Yes.. sure
ckpv5 said:
That is wrong .. you need to see the CID/MID not the serial no.
He can flash the 6.12.401.4 RUU zip
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
1. - remove the serial no. in your above post.
2. - Is the bootloader LOCKED or RELOCKED ? If it is UNLOCKED, relock it with command fastboot oem lock
3. - follow this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4 for the driver part
and this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6 for the RUU part
Click to expand...
Click to collapse
Ok I'm downloading the RUU. I've tried to apply this RUU from computer but not worked, I hope it works with fastboot!
I'll tell you once is done, thanks!
Update info:
It gets stuck in "sending 'zip'... <53965 KB>
I've waited 20 minutes and nothing happens.
ckpv5 said:
yes.. Sure
Click to expand...
Click to collapse
yes!!! It lives! You are one magnificent human being! I am forever in your debt!:d:d
thank you thank you thank you
ramajo17 said:
Ok I'm downloading the RUU. I've tried to apply this RUU from computer but not worked, I hope it works with fastboot!
I'll tell you once is done, thanks!
Update info:
It gets stuck in "sending 'zip'... <53965 KB>
I've waited 20 minutes and nothing happens.
Click to expand...
Click to collapse
Have you install the fastboot/adb that linked above ?
Have you updated the HTC USB drivers, also linked above ?
Try with a Windows PC USB2.0
ckpv5 said:
Have you install the fastboot/adb that linked above ?
Have you updated the HTC USB drivers, also linked above ?
Try with a Windows PC USB2.0
Click to expand...
Click to collapse
Yes both things. I'll try to download the RUU again because when I try to unzip it on my PC it says that the file is corrupted.
Can be that the problem?
ramajo17 said:
Yes both things. I'll try to download the RUU again because when I try to unzip it on my PC it says that the file is corrupted.
Can be that the problem?
Click to expand...
Click to collapse
You can't extract/unzip an encrypted HTC RUU zip.
You never reply to my first question .. is your bootloader LOCKED, RELOCKED or UNLOCKED ?
If it is UNLOCKED .. I can suggest another method .. restore a TWRP backup.
If you have installed both adb/fastboot and latest HTC USB driver (and uninstall HTC Sync Manager) I don't see a reason why it cannot work for you when it worked for the other guy (post #14)
Do you have a microSD card ? You can do it different way.
ckpv5 said:
You can't extract/unzip an encrypted HTC RUU zip.
You never reply to my first question .. is your bootloader LOCKED, RELOCKED or UNLOCKED ?
If it is UNLOCKED .. I can suggest another method .. restore a TWRP backup.
If you have installed both adb/fastboot and latest HTC USB driver (and uninstall HTC Sync Manager) I don't see a reason why it cannot work for you when it worked for the other guy (post #14)
Do you have a microSD card ? You can do it different way.
Click to expand...
Click to collapse
Sorry, it is RELOCKED.
I'll try to do all from 0 again. If it does not work we can UNLOCK it and try the TWRP method you say?
Yes I do have an SD card in my phone, but my PC doesn't detect it and have no SD adapter. I've heard that there's some fastboot command "push" or something like that to put the RUU on it but don't know how it works.
Thanks for your time, I'm desperate. . .
You need to unlock bootloader to go with TWRP method.
Just try again ... with a Windows PC with USB2.0 (many people report USB3.0 is a hit and miss)
Make sure the HTC Sync manager is uninstalled after you install the driver.
ckpv5 said:
You need to unlock bootloader to go with TWRP method.
Just try again ... with a Windows PC with USB2.0 (many people report USB3.0 is a hit and miss)
Make sure the HTC Sync manager is uninstalled after you install the driver.
Click to expand...
Click to collapse
Can't believe it was de USB . . . Now is doing things, let's see
Update:
IT IS ALIVE!! The problem was de USB . . I was using the official one but didn't work.
Really big thanks!!

Categories

Resources