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)
Related
Hello everyone.
Im new here and my english is not on the highest lvl, so pls be patient.
My problem with HTC Desire 816 is that I'm stuck in fastboot with no OS and S-ON, like below:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A5_UL PVT SHIP S-ON
HBOOT 3.19.0.0000
RADIO 1.101.1102.17.0506
OpenDSP v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 10 2014
I can't do anything on my phone (recovery, factory reset) cuz after hiting 'power' phone just reboot into bootloader again.
When i plug my phone via USB, windows 8.1 found my device and I have installed it as "Android Composite ADB Interface" and HTC Sync starts running (so it can see my phone).
But my biggest problem is now!
I have installed fastboot in version 1.0.31 and when my phone is pluged in and everything looks good, then commend "adb devices" nothing shows up.
My question is, how can I get my phone visible in adb ?
PS. I have installed cm12 and tried to get back to stock rom and recovery, but in one second in middle on the instalation, power in my house stops and everything just turned off.
And now I have this problem. It looks exactly the same when I had USB debugging turned off in cm12 .. computer and htc sync could see my phone, but adb couldn't.
Any ideas ?
Regards,
Jeremi
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
riggerman0421 said:
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
Click to expand...
Click to collapse
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
elcientifico said:
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Device was already locked. Still the same problem.
I have to bypass "signature checking" .. but how ?
PLS can anyone help me ? :crying:
themonsterkk said:
PLS can anyone help me ? :crying:
Click to expand...
Click to collapse
What exactly are you trying to do and what is the exact message your getting?
FoxyDrew said:
What exactly are you trying to do and what is the exact message your getting?
Click to expand...
Click to collapse
Im stuck in fastboot. Ive got S-ON, Tampered, relocked, Security Warning.
I found somewhere here that I have to flash via fastboot RUU with mainver >= my current mainver.
But problem is:
c:\adbfastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BFWW00545
(bootloader) imei: 352240067356325
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
As U can see above, version-main line is empty.
And after many tries flashing different roms, always the same info: FAILED (remote: 12 signature verify fail)
themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
From the screenshot you provided you are using the wrong command. To flash the recovery try this.
"fastboot flash recovery recovery_Stock.img"
Also the recovery_Stock.img file needs to be in your adbfastboot folder, and IIRC you need the bootloader unlocked to flash anything from fastboot.
themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
FoxyDrew said:
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
Click to expand...
Click to collapse
Ok, topic can be closed. I have done this.
But now, doesn't matter which custom rom I would flash, every time the same annoying problem with screen. My screen/touch doesn't work properly. I will say more. I can't do anything! Everything is poping out in one second..
****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.
BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.
Hi all,
So I have my old M8 doing nothing (switched to Note 4)...
It's running a custom venom rom, and basically I want to put it completely back to factory state.
If you could help a guy that's moderately good at this stuff, I would be greatly appreciated.
Thanks!!
Post the output from fastboot getvar all and we'll tell you what to do
Thanks for that, err - I haven't got the tools installed any more, could you point in the direction of the tools again sorry!
Ok, getvar just sits at waiting for device...?
Ok sorry, turns out I'm just rusty!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Done, and thanks!
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Shozuki said:
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Click to expand...
Click to collapse
No other way, only sunshine.
But you don't need S-Off to revert to stock with that thread guide, you need to relock bootloader then follow all the steps.
The only thing is without S-Off, your bootloader will show RELOCKED instead of LOCKED.
Ah cool, minor.
Thanks
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
EddyOS said:
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
Click to expand...
Click to collapse
Indeed, but I'm literally giving it my uncle and let him use it.
If I may ask one more thing though, when sending the ruu.zip
I get:
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 3(s)
Any ideas??
Thanks for your help sirs.
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
EddyOS said:
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
Click to expand...
Click to collapse
Unfortunately it's still unlocked, but I can't seem to change that either. I'm using minimal adb and fastboot, but the htc_bootloader is in the folder.
Am I supposed to use that from the start, as I only see reference in the final stage.
Apologies, if I'm misreading!
EDIT, I followed the guide starting with recovery which kept failing... That must be the issue...
from your guide EDIT: Thread I meant:
"Well lord knows what's going on here...
I started by flashing the recovery to the one linked here. It won't boot into recovery at all it just sits at "entering recovery..."
I was using a venom custom rom and TWRP 2.8.5.0 touch recovery.
I can boot into the phone, use fastboot and adb - but can't go any further in restoring the handset back to factory... All help appreciated."
ckpv5 said:
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Click to expand...
Click to collapse
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
Yeah, That guide is for EU M8's only...
really struggling getting mine back to factory...
crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
That depends. Are you s-off? If so, you can run a WWE RUU, and go back to basically stock. WWE is compatible with Rogers. You won't get OTAs though. You'll have to update firmware manually, but with s-off, that's easy to do.
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Shozuki said:
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Click to expand...
Click to collapse
What was it?
EddyOS said:
What was it?
Click to expand...
Click to collapse
Well basically I was following the instructions as if I were S-Off.
Instead I just to use: fastboot oem lock and completely skimmed over the text failing to read it!
My uncle is happy now and thats fine with me!
Thanks for your help!
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!!
Hello everyone, The story with my htc is that an error "Unfortunately settings has stopped" popped up so I went into bootloader and formatted the device, now once the device booted I couldn't get trough setup as the same message popped up over and over so couldn't do anything, then I decided to unlock the bootloader and install twrp so that a custom ROM would work, but once I installed twrp I wouldn't boot system or recovery... so I tried to flash stock recovery but that failed so clever and tired me relocked the device and now the device is relocked and when I attempt to unlock it fastboot claimed a "success" but phone still shows relocked and twrp doesn't want to flash
you must me curious why didn't I just flash the ruu? Well... for this device its cid is H3G__001 and if I can't find a ruu for that that would be correct with the details of the device that would be great
(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.12.771.10
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ca3c8ca2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Anyone any ideas on what I should do? :crying:
Anyone?
Maybe someone has the h3g uk ruu for the m8s?
0PKVIMG_M8_QL_UL_L50_SENSE60_H3G_UK_1.12.771.10_R [email protected]_15.00_016_F_release_450151 _combined_signed.zip
Or maybe someone with access to ir-file.com?
for RUU: https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If TWRP doesn't want to flash: You need HTC_Fastboot and NOT the regular Fastboot. ==> https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
twrp-3.0.2-0-m8ql.img is confirmed to work: https://basketbuild.com/devs/Captain_Throwback/One (M8S)/Recovery
jeroen_13 said:
for RUU: https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If TWRP doesn't want to flash: You need HTC_Fastboot and NOT the regular Fastboot. ==> https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
twrp-3.0.2-0-m8ql.img is confirmed to work: https://basketbuild.com/devs/Captain_Throwback/One (M8S)/Recovery
Click to expand...
Click to collapse
Thanks for the links but when i googled the first thing that popped up was ruu.lalleman.net and the ruu than im looking for if not there
But if i understand correctly from what your saying is that i can flash twrp with htc_fastboot with the bootloader relocked?
I will also try to flash the unlock_code.bin with the htc_ fastboot and ill reply on how it goes
the_ziom said:
Thanks for the links but when i googled the first thing that popped up was ruu.lalleman.net and the ruu than im looking for if not there
But if i understand correctly from what your saying is that i can flash twrp with htc_fastboot with the bootloader relocked?
I will also try to flash the unlock_code.bin with the htc_ fastboot and ill reply on how it goes
Click to expand...
Click to collapse
I linked ruu.lalleman.net because your were looking for your RUU.
You have to UNLOCK your bootloader again before flashing TWRP with HTC_fastboot
jeroen_13 said:
I linked ruu.lalleman.net because your were looking for your RUU.
You have to UNLOCK your bootloader again before flashing TWRP with HTC_fastboot
Click to expand...
Click to collapse
like the title of this thread and the first post on this thread says the phone doesn't want to unlock and I believe that its because of no recovery and what u are telling me I know from google and other xda threads so if I would really know how to solve this problem I wouldn't have made this thread
the_ziom said:
like the title of this thread and the first post on this thread says the phone doesn't want to unlock and I believe that its because of no recovery and what u are telling me I know from google and other xda threads so if I would really know how to solve this problem I wouldn't have made this thread
Click to expand...
Click to collapse
What error do you get while sending the unlock token?
Can you send me the cmd log ?
jeroen_13 said:
What error do you get while sending the unlock token?
Can you send me the cmd log ?
Click to expand...
Click to collapse
Well thats the thing cmd shows success
And the unlock_code.bin opens on the phone i press vol up to select yes press power than the phone reboots and still shows relocked
the_ziom said:
Well thats the thing cmd shows success
And the unlock_code.bin opens on the phone i press vol up to select yes press power than the phone reboots and still shows relocked
Click to expand...
Click to collapse
Ok so i bought a ir-file 30 day account downloaded the RUU and copied it to a sd card than i booted into bootloader and the process started... And tan the bootloader showed (after flashing the system.img like 6 times) that the process failed but i took my chances and rebooted the phone and now im writing this post from it [emoji2]. Thanks for help and if anyone has a similar problem than pm me withing 30 day and ill get you the RUU
Sent from my HTC One M8s using XDA-Developers Legacy app
Same problem, same RUU
Hi, if you could share the RUU will be great as I am having the same issue and it will be great to have my HTC back on tracks
Many thanks in advance
the_ziom said:
Thanks for help and if anyone has a similar problem than pm me withing 30 day and ill get you the RUU
Click to expand...
Click to collapse
Hi, have you by any chance seen my PM ?