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
Related
Hello,
this is my first post here, and i'm sorry for my maybe bad english. I'm from Germany.
I have some Problems with my M8 and i try to depict it to you.
Hello there,
I have kind of a strange problem . I wanted to flash my HTC on a Ungebrandetete version .
I have S - OFF and the bootloader is unloked .
I flashed the following RUU from the collection : RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
after the flash process the HTC restarts , it optimizes 262 Apps , then comes quite normal the establishment of smartphones . and I can use the phone .
Once I restart the Phone I can see the HTC ONE logo and hear the boot sound and then nothing happens . If I put it back to factory reset in the bootloader , the phone starts again , optimizes the 262 apps and re- establishing the Phones .
I'm really on despair : here is an excerpt from my " GETVAR all "
Code:
(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: XXXXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
EDIT:
I just flashed the CM13.0 Nightly and that works wonderfully i can restart the phone and it starts normaly. But the last snapshoot form cm12.1, Viper ROM, GPE Rom starts only 1 time after flashing and then nothing.
So my guess is that it is up to the RUU , not fit ? I thought with S -OFF can I flash anything i want
greetings
Kryptik
no one any idea?
Kryptik86 said:
no one any idea?
Click to expand...
Click to collapse
Can't see what can be causing the issue, unfortunately. But I can offer up a few comments to your top post:
Kryptik86 said:
I thought with S -OFF can I flash anything i want
Click to expand...
Click to collapse
Not quite "anything". Yes, on past HTC devices s-off meant that all restrictions were lifted. But on this device, you still need to match CID and MID for signed RUUs, firmware, etc.
Kryptik86 said:
So my guess is that it is up to the RUU , not fit ?
Click to expand...
Click to collapse
Did the RUU run to completion without any error messages?
If so, the issue is not the right RUU.
redpoint73 said:
Can't see what can be causing the issue, unfortunately. But I can offer up a few comments to your top post:
Not quite "anything". Yes, on past HTC devices s-off meant that all restrictions were lifted. But on this device, you still need to match CID and MID for signed RUUs, firmware, etc.
Did the RUU run to completion without any error messages?
If so, the issue is not the right RUU.
Click to expand...
Click to collapse
The RUU ran to the end without error . The idea with the MID sounds ineressant , have already read how to change them . But if I have understood correctly you have to ROOT/ superuser rights? And the phone is in debug mode?
Kryptik86 said:
The RUU ran to the end without error . The idea with the MID sounds ineressant , have already read how to change them . But if I have understood correctly you have to ROOT/ superuser rights? And the phone is in debug mode?
Click to expand...
Click to collapse
Yes, you need to have s-off (which you do), root and in debug mode (as you will be using adb to issue the commands) to change MID.
But this is to run a different CID/MIDs RUU (different from your present CID, MID). Is that what you are talking about doing?
Note that changing the MID may brick the device, if you screw it up. So proceed with extreme caution, and follow instructions carefully (and only instructions for the M8). And you should note the existing MID, in case you need to change it back.
Also, flashing another CIDs RUU may change the network band support on the phone, as it flashes a different radio baseband.
What are you thinking of doing, exactly?
so i'm now @work i think i try it tomorow.
In first i will check my MID, and try to find out whats maybe wrong with it - or not.
i did CID change 2 or three times to super CID and to google CID and back to HTC__102 thats not a prob for me.
But in first i CHECK my MID and post it here, maybe someone know whats the Problem with the phone and the ROM's
i'm just wondering that Cyagenmod 13_nightly works without the 2nd boot problem.
I'm going crazy, thats my 2nd m8.
with my first M8 (main phone) i tryed nearly all custom roms, and now I'm on GPE 6.0. without any problems.
hope you can understand what i'm trying to say
greetings
kryptik
Kryptik86 said:
so i'm now @work i think i try it tomorow.
In first i will check my MID, and try to find out whats maybe wrong with it - or not.
But in first i CHECK my MID and post it here, maybe someone know whats the Problem with the phone and the ROM's
Click to expand...
Click to collapse
I think you are making up problems that don't exist (MID). Or at least thinking of "solutions" with no basis.
If the MID was wrong, the RUU would have failed (same as if the CID was wrong).
And the MID is correct, based on your getvar output posted in the top post (modelid).
MID won't affect custom ROMs.
Don't mess with the MID, for the reasons stated previously. I don't see how it will help you; and if you make a mistake you will brick.
yes, i thinking like you, there is no prob. with my mid.
so the searching going on
I would try the RUU again, maybe something didn't install correctly the first time.
redpoint73 said:
I would try the RUU again, maybe something didn't install correctly the first time.
Click to expand...
Click to collapse
i have tryed to Install this over 15 times. every time the same "error" after install the system starting normal.
after reboot nothing happen on the "HTC ONE" logo, only whey i do a factory reset, then it starts normal again, till i restart the phone next time.
yesterday i try to install a MIUI rom from XDA this one
and it works. so my thinking is, that is something with 5.X ROM's because it seems that only this not working.
MIUI = 4.4.4 = Work
CM12.1, VIPER ROM, STOCK, GPE 5.1 = 5.X = Don't work :silly: :crying:
CM 13 = 6.0 = Work
what do u thinking?
Kryptik86 said:
what do u thinking?
Click to expand...
Click to collapse
Don't know, its pretty puzzling. Especially since you have the error on full stock (RUU) and also on CM12.1.
I'm out of ideas, short of changing your CID/MID to flash another versions RUU (which seems pretty drastic).
push
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!!
Somebody can link me a Vodafone UK firmware zip, I have to flash it in RUU mode in order to make my phone working again.
Thank you in advance
Check post #1 and ask here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
I can't help much as I don't have a M8s
ckpv5 said:
Check post #1 and ask here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
I can't help much as I don't have a M8s
Click to expand...
Click to collapse
Yeah, checked multiple times, but I didn't find any proper files according to my problem. I mean , I've got the RUU files there, but I have to flash through ruu only the firmware zip because I've relocked the bootloader, and since I have wrong recovery flashed (simple M8 recovery) can't do anything else. I think this is the only solution.
Btw thanks for replying.
I don't get it ...
If there is RUU for your device version, use the RUU to fix the problem.
You don't need firmware.zip when there is RUU available (when you install the same version as your current firmware written on bootloader)
ckpv5 said:
I don't get it ...
If there is RUU for your device version, use the RUU to fix the problem.
You don't need firmware.zip when there is RUU available (when you install the same version as your current firmware written on bootloader)
Click to expand...
Click to collapse
I need the firmware cause the RUU for my HTC doesn't works, it starts flashing the file but shuts down with an error ... Sorry for not mentioning that . Flashing the firmware I think the only solution for me :/
Hi GombaFelho,
I had the same problem, always the wrong firmware error message.
I unlocked and did again an "oem lock". Check again the drivers for RUU.
In end it worked for me with the ARUWizard.exe and this version:
RUU_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161.1_Radio_1.0.U20410.1G50408_15.00_016_F_release_430447_signed
First there is a downgrade and after that you can uprade the software on the fly.
realclone1000 said:
Hi GombaFelho,
I had the same problem, always the wrong firmware error message.
I unlocked and did again an "oem lock". Check again the drivers for RUU.
In end it worked for me with the ARUWizard.exe and this version:
RUU_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161.1_Radio_1.0.U20410.1G50408_15.00_016_F_release_430447_signed
First there is a downgrade and after that you can uprade the software on the fly.
Click to expand...
Click to collapse
Hi ! Thanks for the answer
I tried that one too, but some magical way my update stuck at 0/8 so idk what should I do ..
I've read somewhere a solution for this, but can't remembere where
When you have that stuck problem, that's pc usb connection problem not RUU.
You need latest htc usb drivers and use usb2.0
Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
ckpv5 said:
When you have that stuck problem, that's pc usb connection problem not RUU.
You need latest htc usb drivers and use usb2.0
Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Click to expand...
Click to collapse
Tried it now, says the bootloader verison not correct... im really unlucky
Back to basic ... most important data in order to get help.
Post your fastboot getvar all result (remove serial & imei no.)
ckpv5 said:
Back to basic ... most important data in order to get help.
Post your fastboot getvar all result (remove serial & imei no.)
Click to expand...
Click to collapse
Okay, as soon as I can get my phone load up . Thanks for your patience and sorry for my idiotism..
EDIT : so here are the results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.21.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP102
(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: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Unfortunately neither firmware nor RUU available on the net for this version.
When you said you wait for it to load up .. are you saying your device is in working condition, only wrong recovery installed ?
ckpv5 said:
Unfortunately neither firmware nor RUU available on the net for this version.
When you said you wait for it to load up .. are you saying your device is in working condition, only wrong recovery installed ?
Click to expand...
Click to collapse
I shouldn't wait for anything , right ? I mean it's not that new phone, so I assume there aren't going to be a new firmware for this version...
It was in a working condition, but after I relocked the bootloader, it went off. Had to start with the Pow+Vol.Up+Vol.Down combo, it worked but now just stops at the HTC ONE screen...
Anyways I really appreciate that you took the time to help me
I was wondering if there is some way to unlock the bootloader without using the HTCDev ? (cause I can't factory reset my phone) that would be so good...
I have an M8s too, and had the same issue.
To fix this. First try to relock and unlock the your bootloader it will prompt yes or no bla bla... Tick yes
If none of this work. Install the latest recovery from lalleman's server and pick a custom ROM, I recommend CM12 since you don't a choice cause Pandora is a little buggy.
This should work for you. Good luck with that
Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.
ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.
Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.
You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.
hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip
ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1
ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same
alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan
alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14
Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu please help me
this are my fastboot getvar all value :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: ******
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
so my bootlader is locked with security warning and software status : modified
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
when i unplugged the phone from charger this problem occurred i didn't flash any RUU later and my phone is unrooted .
mamali0067 said:
when i unplugged the phone from charger this problem occurred .
Click to expand...
Click to collapse
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
mamali0067 said:
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
Click to expand...
Click to collapse
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
redpoint73 said:
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
Click to expand...
Click to collapse
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
mamali0067 said:
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
Click to expand...
Click to collapse
Is this a zip format RUU? If so, cut/paste the exact commands you used.
redpoint73 said:
Is this a zip format RUU? If so, cut/paste the exact commands you used.
Click to expand...
Click to collapse
yes the RUU is a zip file , but i flashed that RUU perefer in finding right RUU thread and faced with remote : 12 signature verify fail
mamali0067 said:
i flashed that RUU perefer in finding right RUU thread
Click to expand...
Click to collapse
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
redpoint73 said:
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
Click to expand...
Click to collapse
Okay dude , so help me here !
mamali0067 said:
Okay dude , so help me here !
Click to expand...
Click to collapse
You didn't provide the info I asked for: cut/paste the exact commands you used
redpoint73 said:
You didn't provide the info I asked for: cut/paste the exact commands you used
Click to expand...
Click to collapse
Yes , I have been cutted and pasted the command