Related
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
LondonVirus said:
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
Click to expand...
Click to collapse
Give the result from command fastboot getvar version-main
Thant said:
Give the result from command fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
LondonVirus said:
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
Click to expand...
Click to collapse
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Thant said:
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Click to expand...
Click to collapse
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
LondonVirus said:
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
Click to expand...
Click to collapse
You have good hboot for sense 5 rom 4.2.2 install MaximusHD or ARHD or any sense 5 rom and you are ready to go.
I wanted a stock ROM, the Mrs is not very technical minded lol and a customer ROM won't help her, either TMO UK or in branded, where can I get the RUU for it?
Thanks all
Unfortunately T-Mobile skipped the sense 5, 4.2.2 update, I have the same device and cid and called them countless times, spoke to managers and had it escalated to the highest level only to be told they would not be updating past 4.1.1
Every other network pushed that but them, if you stick to stock T-Mobile ROM you would be missing 2 very important updates, one being the heartbleed patch.
Just grab MaximusHD from the development forum, its the best sense 5 ROM out there and has important ota updates too.
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
LondonVirus said:
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
Click to expand...
Click to collapse
NO S-OFF for HOX
Thant said:
NO S-OFF for HOX
Click to expand...
Click to collapse
I assume that HOX means Htc One X lol... so I will not be able to change the CID?
Any "re-pack" unedited versions of the genuine unbranded europe RUU that I can install via custom recovery?
Thanks again all
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
LondonVirus said:
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
Click to expand...
Click to collapse
Don't be confused mate..HOX can s-off but via java card( will cost money to make it).In here no have chance to be s-off.
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
LondonVirus said:
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
Click to expand...
Click to collapse
Never mind, seems to have worked lol
LondonVirus said:
Never mind, seems to have worked lol
Click to expand...
Click to collapse
Phone hanging on boot screen don't know why...
LondonVirus said:
Phone hanging on boot screen don't know why...
Click to expand...
Click to collapse
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Thant said:
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
LondonVirus said:
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
Click to expand...
Click to collapse
do it manually like I write you in my post not with flasher or tool
Thant said:
do it manually like I write you in my post not with flasher or tool
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------
C:\Android\sdk\platform-tools>fastboot flash zip rom.zip
sending 'zip' (716000 KB)...
OKAY [ 90.451s]
writing 'zip'...
(bootloader) Can not find [android-info.txt] in zipped image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 125.830s
---------------------------------------------------------------------------------------------------------------------
fastboot oem rebootRUU
fastboot flash zip rom.zip <----- This is Maximus HD....
and this is after a flashed the correct kernel/boot.img....
I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*ALSO I am currently on InsertKoin ROM* <--That might change something
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John
I've been S-Off since day one so double check everything but this will get you in the right direction. You need to S-off and unlock, flash an RUU and then relock (to remove the red text warning). Going back to S-on I understand is pretty dangerous and appears to be unnecessary. Go to this thread and start with the 3rd tutorial to re-S-off. If you can get S-off'd the rest should be pretty easy.
jman036 said:
I have been rooted for a few weeks and decided to go back. Well I had S-off but when I started the transition to stock I turned s-on and that is when the **tampered** flag came on. I stupidly continued using the code (fastboot oem lock) which gave me the **Relocked** status but now I have a security warning and It will ONLY boot into bootloader. I have tried multiple times re-flashing TWRP and I cant get it to go into recovery. From what I have read I need to flash stock rom onto it but I cant get into the recovery to flash or even sideload. So where should I go from here? Everything I need to do requires S-off and I cant seem to get it.
*HtcDev will not work for my phone.*
fastboot oem unlock gives ERR [command error]
Last flashed TWRP version was 2.7.0.1
Specs.
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
GetVar info below also.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3B6S906771
(bootloader) imei: 990004282795917
(bootloader) meid: 99000428279591
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4134mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
Oh! If someone would mind explaining what any of that means (even just an acronym) would help for me learning this!
Thank you in advance. John
Click to expand...
Click to collapse
That should be early enough to use Firewater on. Let me know if you run into problems because I can help via team viewer.
@pmterp & @dottat Thanks for the reply and that sounds like a good idea but I have to push the file via adb. I cannot get there because I am stuck in the fastboot section. So I don't think firewater or anything that uses adb will work.
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
You can go into ruu mode while s-on, but need a signed ruu. Last signed ruu we had was 2.x
Sent from my HTC6500LVWBLU using XDA Free mobile app
pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
That is RUU mode and will accept an RUU file to flash at this point. I believe Uzephi is correct that the RUU you flash must be signed (which I think is the same as encrypted). I'm not sure where you would find them but I'm sure Google will be your friend on that. Be careful what version you flash because I think it can cause problems if you move down. I'm not sure how open he is to helping via PM (he's super helpful but also very busy) but if it were me I'd reach out via PM to @santod040 and ask for advice. He's a highly skilled dev who's been with this device a long time.
I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.
tflogic said:
I think I might be in the same boat as jman036, only difference being that I'm on a later OS version (5.28.605.2). I've tried flashing signed RUUs for my particular OS version from both santod's and dottat's AndroidFileHosts but both give me this error:
"(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)"
Sucks man.
Click to expand...
Click to collapse
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Click to expand...
Click to collapse
Dang really? I thought they would be since they both have "signed" in the filenames.
HSM_M7_WL_K443_SENSE60_VZW_MR_VERIZON_WWE_5.28.605.2_HSM_Radio_1.13.41.0702_NV_VZW_4.64_002_release_387332_signed.zip
Click to expand...
Click to collapse
Any idea what to do then?
tflogic said:
Dang really? I thought they would be since they both have "signed" in the filenames.
Any idea what to do then?
Click to expand...
Click to collapse
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have one of each ?
---------- Post added at 10:58 PM ---------- Previous post was at 10:55 PM ----------
jman036 said:
I tried that command and it did do something different now. It is an all black screen with silver HTC however it is not doing anything.
Click to expand...
Click to collapse
See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340
dottat said:
Yes. Will fail. You should try installing the latest HTC sync and seeing if the repair button lights up for you on the home page of the app.
Click to expand...
Click to collapse
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?
tflogic said:
HTC Sync doesn't recognize the phone. Getting a "no phone connected" message. Any other ideas?
Click to expand...
Click to collapse
If installed drivers are correct htc sync will see the phone. I just responded to your post in a different thread. Can you try that first before we troubleshoot drivers?
pmterp said:
Crud. I don't remember if you can get to RUU mode without being S-off. In fastboot the command is fastboot OEM rebootRUU If you can then you could re-RUU but I'm thinking you have to be S-off to get there. Hopefully someone else will chime in with some better ideas.
Click to expand...
Click to collapse
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.
Uzephi said:
Both of their 5.28.605.2 ruus are decrypted and thus unsigned. You will get a signature check fail if you are s-on
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I cant seem to find any RUU files that match my phone!
dottat said:
Fastboot oem rebootRUU mode is supported in both s on/off scenarios. An s on user can always use this to reflash same firmware or even upgrading to newer firmware. Bootloader unlocked phones often take advantage of this before s off exploits are found.
Click to expand...
Click to collapse
Well I made it one step further with it recognizing that I have a phone connected but said "no software available."
I think if I can find a signed RUU file then I can fix this. I just have to find it.....
See if you can flash this zip while your phone is in this ruu mode.
Fastboot flash zip firmware3.zip
May require flashing twice.
https://www.androidfilehost.com/?fid=23681161096070340
Click to expand...
Click to collapse
Well I tried this and sadly I can send it but it always gets signature check fail. :/ (I ran it twice also)
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!!
I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
bavman said:
I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
Click to expand...
Click to collapse
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
DavidYouKnow? said:
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
Click to expand...
Click to collapse
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup: https://mega.nz/#!mYxDWApA!JbdLZAhYkz8fas5MpPfOQqGScikCLCmG21KBsjRJKQQ
Then use latest twrp recovery 3.0.2-0: https://dl.twrp.me/m8/twrp-3.0.2-0-m8.img.html and install it.
Here is the Stock Recovery that you need later: https://mega.nz/#!SUATBBbQ!-IUlr_tqnpkYFUM0bedRSRH3w__nCZjEAYls-5zncX4.
Then do this taken from this page: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
The basic idea is : fastboot flash recovery NameOfRecovery.img
2. Download TWRP backup - link in post #2 & post #3
3. Download stock recovery - link in post #4
4. Extract the downloaded x.xx.xxx.x_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
12. reboot - check for OTA, download, install
13. you may have multiple OTA when your device currently on a lower version
14. done
If you want to flash TWRP again, use the latest TWRP after last OTA
NOTE : There is no need to relock bootloader when doing the nandroid way to revert to stock and do OTA.
Click to expand...
Click to collapse
..............................................................................
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup:
********
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
Click to expand...
Click to collapse
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
Click to expand...
Click to collapse
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
redpoint73 said:
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
Click to expand...
Click to collapse
No i didnt guessing at the version number, i thought that he have a higher Firmware version. Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
ckpv5 said:
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
Click to expand...
Click to collapse
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
bavman said:
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
Click to expand...
Click to collapse
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
---------- Post added at 09:43 AM ---------- Previous post was at 09:38 AM ----------
DavidYouKnow? said:
Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
Click to expand...
Click to collapse
Restoring by RUU versus nandroid are two completely different things, and you should be careful not to confuse the two:
RUU re-writes all partitions, including firmware, so there is no chance of a mismatch between firmware and ROM. Therefore, you don't need to match the RUU version to firmware, as long as the RUU is equal or greater number than the current firmware on the phone (no "downgrading" with s-on). And with s-off, this requirement is removed entirely, so you can run any version RUU that matches your CID, MID.
Restoring by nandroid is a completely different animal. Nandroid just contains the ROM and kernel. It needs to match the firmware on the phone, otherwise it won't work properly.
redpoint73 said:
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
Click to expand...
Click to collapse
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
ckpv5 said:
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
Click to expand...
Click to collapse
Now I understand. Its confusing, since the 2 methods (both of which have you to credit) to return to stock are both referenced in this thread (another user references the nandroid method); and folks often use the term "firmware" incorrectly to refer to the ROM.
It also means that the user did not follow your instructions in Post #5 in the proper sequence. So RUU failing was inevitable, and easily avoidable; if they had followed your instructions in the proper order.
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