Related
Hi
i have HTC ONE GPE and i tried to downgrade the HBOOT
from 1.54 to 1.44 to change the CID but all my tries fail
can any one help me with this problem
irooon said:
Hi
i have HTC ONE GPE and i tried to downgrade the HBOOT
from 1.54 to 1.44 to change the CID but all my tries fail
can any one help me with this problem
Click to expand...
Click to collapse
If all you need to do is change your cid, you don't need to downgrade HBOOT. Just use the rumrunner technique to S-off (if you're not already) found here, and you should be fine.
kibmikey1 said:
If all you need to do is change your cid, you don't need to downgrade HBOOT. Just use the rumrunner technique to S-off (if you're not already) found here, and you should be fine.
Click to expand...
Click to collapse
i think GPE (Google play edition) no need S-off
if u know how just tell me
Sent from my HTC One using XDA Premium HD app
still waiting any answer
Sent from my GT-I9505 using XDA Premium HD app
irooon said:
still waiting any answer
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
No, you need s-off to make those sorts of changes
rider5512 said:
No, you need s-off to make those sorts of changes
Click to expand...
Click to collapse
i know no need for s-off but I'm still searching for the right HBOOT 1.44 i try three HBOOT and all give me error 'remote 99'
Sent from my HTC One using XDA Premium HD app
S-OFF IS REQUIRED TO DOWNGRADE.
Sent with pigeons.
how can i make s-off for googl play edition ?
Sent from my HTC One using XDA Premium HD app
i try too many HBOOT and the result is remote error and i modified the zip file to my phone id and all result is same plz anyone help
C:\Program Files\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip hboot_hexed_m7_wls.
zip
target reported max download size of 1526722560 bytes
sending 'zip' (485 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip hboot_hexed_m7_wls.
zip
target reported max download size of 1526722560 bytes
sending 'zip' (485 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip hboot_hexed_m7roger
s.zip
target reported max download size of 1526722560 bytes
sending 'zip' (485 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
Click to expand...
Click to collapse
I can't post links since I'm a new member, but....
Google Search: "How to Convert Your Google Play Edition HTC One into an HTC One with Sense & No Bloat"
search results should be from htc-one.wonderhowto
Step 2 tells you how to get hboot 1.44
It's probably your android.txt that is incorrect. Your MID (Model ID) has to match the one in the txt file.
irooon said:
i try too many HBOOT and the result is remote error and i modified the zip file to my phone id and all result is same plz anyone help
Click to expand...
Click to collapse
1- you NEED to be S-Off
2- why would you want to flash a Sprint hboot "hboot_hexed_m7_wls.zip" on your device
jambamochi said:
I can't post links since I'm a new member, but....
Google Search: "How to Convert Your Google Play Edition HTC One into an HTC One with Sense & No Bloat"
search results should be from htc-one.wonderhowto
Step 2 tells you how to get hboot 1.44
It's probably your android.txt that is incorrect. Your MID (Model ID) has to match the one in the txt file.
Click to expand...
Click to collapse
I'm doing all the steps and i change the MID on the HBOOT and all give me the same result
nkk71 said:
1- you NEED to be S-Off
2- why would you want to flash a Sprint hboot "hboot_hexed_m7_wls.zip" on your device
Click to expand...
Click to collapse
i try too many HBOOT to downgrade and i think for the HTC ONE GOOGLE PLAY EDITION no need for s-off
irooon said:
i try too many HBOOT to downgrade and i think for the HTC ONE GOOGLE PLAY EDITION no need for s-off
Click to expand...
Click to collapse
OK, maybe I should say it again, YOU CANNOT FLASH OR DOWNGRADE AN HBOOT (ESPECIALLY A HEX-EDITED UNSIGNED HBOOT) with S-ON.
Whether you have a HTC One M7_U, M7_UL, M7_WLS, M7 etc. etc. etc. running GPe, Sense, iOS, Ubuntu, Windows, or anything else you can think of.
Just go get S-Off and then you can flash whatever you want. And when/if you do, do some reading before you have a total brick on your hands.
Sorry if that sounds rude, but this is the fact.
nkk71 said:
OK, maybe I should say it again, YOU CANNOT FLASH OR DOWNGRADE AN HBOOT (ESPECIALLY A HEX-EDITED UNSIGNED HBOOT) with S-ON.
Whether you have a HTC One M7_U, M7_UL, M7_WLS, M7 etc. etc. etc. running GPe, Sense, iOS, Ubuntu, Windows, or anything else you can think of.
Just go get S-Off and then you can flash whatever you want. And when/if you do, do some reading before you have a total brick on your hands.
Sorry if that sounds rude, but this is the fact.
Click to expand...
Click to collapse
i already open the bootloader and root my device but i didn't see any one say that i should make s-off for the Google play edition any way if u know hot to do it just give me hint or link
and many thanks to ur replay
jambamochi said:
I can't post links since I'm a new member, but....
Google Search: "How to Convert Your Google Play Edition HTC One into an HTC One with Sense & No Bloat"
search results should be from htc-one.wonderhowto
Step 2 tells you how to get hboot 1.44
It's probably your android.txt that is incorrect. Your MID (Model ID) has to match the one in the txt file.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar modelid
modelid: PN0712000
finished. total time: 0.000s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip orig_hboot_1.44.000
0_M7_RUUmode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (486 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
Click to expand...
Click to collapse
i try it again to show u the result and i change the mid in the HBOOT info and zip it again and i flash it same result
irooon said:
i try it again to show u the result and i change the mid in the HBOOT info and zip it again and i flash it same result
Click to expand...
Click to collapse
Won't work with S-On. Don't waste you're time.
irooon said:
i already open the bootloader and root my device but i didn't see any one say that i should make s-off for the Google play edition any way if u know hot to do it just give me hint or link
and many thanks to ur replay
Click to expand...
Click to collapse
Check http://rumrunner.us it has packages for GPe 3.06.1700.10 and GPe 3.07.1700.10
EDIT: read and follow instructions to the letter!
Hit the thanks button if I helped
nkk71 said:
Won't work with S-On. Don't waste you're time.
Check http://rumrunner.us it has packages for GPe 3.06.1700.10 and GPe 3.07.1700.10
EDIT: read and follow instructions to the letter!
Hit the thanks button if I helped
Click to expand...
Click to collapse
==================== rumrunner S-OFF 0.1.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ---
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (5/120)
Waiting
[PN0712000-1.54.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (9/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
Click to expand...
Click to collapse
see what happen
irooon said:
see what happen
Click to expand...
Click to collapse
just a hunch, but do you have fastboot drivers installed?
yes and i unlock the bootloader and root the device
Sent from my GT-I9505 using XDA Premium HD app
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
hjjfffaa said:
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
Click to expand...
Click to collapse
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
fenstre said:
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
Click to expand...
Click to collapse
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
hjjfffaa said:
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
Click to expand...
Click to collapse
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
fenstre said:
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
Click to expand...
Click to collapse
But I can downgrade to 1.44 and that would allow me to S-On and get OTA updates right? Or am I totally wrong?
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
hjjfffaa said:
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
Click to expand...
Click to collapse
You have S-off which is good. I'm going to ask you to use the BS_US001 CID. Try downloading the 1.29.1540.17 zip from HTC Dev. Do a fastboot oem rebootRUU and flash the zip from there. It should prompt you to do this twice.
Sent from my HTC One using XDA Premium 4 mobile app
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
hjjfffaa said:
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2497712
You can follow that thread if you want to set the phone to locked.
I'm sorry I forgot about the 4.3 zip, use that one if you want to go straight to 4.3. Again, my apologies
Sent from my HTC One
I don't care if it says re-locked (so long as it functions how it should), I just want my Sense ROM. I already have the 4.3 Dev Edition zip, should I try flashing it with fastboot?
I tried flashing the 3.22.1540.1 zip and got this problem, which doesn't seem consistent with the one guide I've seen for this process.
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.663s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.625s
Click to expand...
Click to collapse
Try 'fastboot erase cache' and 'fastboot reboot-bootloader' before you 'fastboot oem rebootruu' and then run the fastboot flash zip filename.zip'
Sent from my HTC One
The results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.359s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.318s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
Could this be a result of the 1.54 bootloader?
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
Can you take an image of your bootloader for me real quick
gusto5 said:
Can you take an image of your bootloader for me real quick
Click to expand...
Click to collapse
Here you go.
hjjfffaa said:
Here you go.
Click to expand...
Click to collapse
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
gusto5 said:
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
Click to expand...
Click to collapse
Thanks for all your help. Trying a different USB port.
You were right, it did nothing.
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
You may be right. Let's have you downgrade the Bootloader to 1.44 and then try running the RUU again.
Just remember that you already have the right MID and CID. CID you changed yourself, MID already matches as the Google Play Edition shares the same MID as the Developer edition (and a few other North American HTC Ones).
Here are the (real) results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip hbootRUU.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.516s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
hjjfffaa said:
Here are the results:
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
Click to expand...
Click to collapse
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
gusto5 said:
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All right, should I add it to the android-text file though?
Hey guys so I have a lot of problems with my phone like the purple camera and my volume down broke. Ive been trying to fix it for ages and im finally up to the last step and its not working.
I'm trying to get S-ON and used the cmd "fastboot oem writesecureflag 3" but it gives me an error fail thing
C:\Users\Ivan\Desktop\ROOT>adb devices
List of devices attached
HT35DW923150 device
C:\Users\Ivan\Desktop\ROOT>adb reboot boatloader
C:\Users\Ivan\Desktop\ROOT>fastboot devices
HT35DW923150 fastboot
C:\Users\Ivan\Desktop\ROOT>fastboot erase chache
erasing 'chache'...
FAILED (remote: not allowed)
finished. total time: 0.014s
C:\Users\Ivan\Desktop\ROOT>fastboot erase cache
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.372s
C:\Users\Ivan\Desktop\ROOT>fastboot oem writesecureflag 3
...
(bootloader) partition sbl2 signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 0.086s]
finished. total time: 0.090s
C:\Users\Ivan\Desktop\ROOT>
So I dont know what to do from here, I hope you guys can help me out.
Send your phone without S On HTC check for unlocked relocked locked only
If Locked is there without tampered they will avail warranty
To remove Tempered and set Locked use Guru bootloader reset tool in TWRP
yatindroid said:
Send your phone without S On HTC check for unlocked relocked locked only
If Locked is there without tampered they will avail warranty
To remove Tempered and set Locked use Guru bootloader reset tool in TWRP
Click to expand...
Click to collapse
Are you sure that i can send my One with S-Off??
Raschild6 said:
Are you sure that i can send my One with S-Off??
Click to expand...
Click to collapse
in my country they check tempered and unlocked bootloader not for S Off or On
ask your friends in your country
yatindroid said:
in my country they check tempered and unlocked bootloader not for S Off or On
ask your friends in your country
Click to expand...
Click to collapse
no problem i have set S On, now my One is in the other hands i hope it comes back soon!!
Any luck on this front? I am getting the same message when trying to writesecureflag 3. Any ideas?
i had a mis-matching hboot version between my ROM and firmware. downgraded the firmware back to the version matching the ROM and i was able to get S-ON
you guys have a modded hboot in there (who knows what else is non-100%-stock),
consider yourself lucky that command does signature checks, otherwise you'd have an insta-brick paperweight on your hands.
I'm trying to get back to complete stock to grab OTAs for my HTC One m8. I have s-off and I was following the guide here http://venomroms.com/viperonem8_3-0-0-requirements/ and while following the guide and looking for my Main version number and CID Number the MainVer showed up as empty and my CID Number as SPCS_001. The CID does not match anything from here http://forum.xda-developers.com/showthread.php?t=2701376 What should I do next?
Use this guide:
http://forum.xda-developers.com/showthread.php?t=2826343
You'll need the latest RUU which can be found in the first post in the thread linked below. You can use the RUU for software version 3.31.651.2.
http://forum.xda-developers.com/showthread.php?t=2729173
I would also suggest sticking to the Sprint section.
You may do something to your phone that is not for the Sprint variant and really mess up your phone.
Magnum_Enforcer said:
Use this guide:
http://forum.xda-developers.com/showthread.php?t=2826343
You'll need the latest RUU which can be found in the first post in the thread linked below. You can use the RUU for software version 3.31.651.2.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
sadway15 said:
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
Click to expand...
Click to collapse
Ruu is used through a pc
sadway15 said:
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
Click to expand...
Click to collapse
The RUU will install the stock recovery. If you need info on how to run a RUU click the second link in my sig and read the RUU section.
Magnum_Enforcer said:
The RUU will install the stock recovery. If you need info on how to run a RUU click the second link in my sig and read the RUU section.
Click to expand...
Click to collapse
Okay so I think I get it now please confirm, I run the RUU with my PC then once its finished put the stock recovery corresponding to the RUU I installed in the phone then install the stock recovery using TWRP in my phone then I will have a stock htc rom with stock recovery and the phone will update from there.
sadway15 said:
Okay so I think I get it now please confirm, I run the RUU with my PC then once its finished put the stock recovery corresponding to the RUU I installed in the phone then install the stock recovery using TWRP in my phone then I will have a stock htc rom with stock recovery and the phone will update from there.
Click to expand...
Click to collapse
The RUU will put you back to completely stock...only difference is your bootloader will say ***RELOCKED*** instead of ***LOCKED***
BD619 said:
The RUU will put you back to completely stock...only difference is your bootloader will say ***RELOCKED*** instead of ***LOCKED***
Click to expand...
Click to collapse
Complete stock meaning stock rom and stock recovery right? Also what will happen if my bootloader is locked/unlocked?
sadway15 said:
Complete stock meaning stock rom and stock recovery right? Also what will happen if my bootloader is locked/unlocked?
Click to expand...
Click to collapse
Correct.
You will need to re-lock your bootloader to run the RUU if you are s-on, if s-off no need to re-lock.
BD619 said:
Correct.
You will need to re-lock your bootloader to run the RUU if you are s-on, if s-off no need to re-lock.
Click to expand...
Click to collapse
I'm trying to get to stock too but I'm s-on, besides locking the bootloader is there anything else I need to modify?
guissepi said:
I'm trying to get to stock too but I'm s-on, besides locking the bootloader is there anything else I need to modify?
Click to expand...
Click to collapse
No, just relock and run the RUU.
Magnum_Enforcer said:
No, just relock and run the RUU.
Click to expand...
Click to collapse
I tried relocking and when I ran the RUU this was the output:
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
guissepi said:
I tried relocking and when I ran the RUU this was the output:
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
Click to expand...
Click to collapse
Which RUU are you trying to run? Are you on Windows, and why are you trying to fastboot flash it? If you're on Windows simply double-click the RUU to start the installer. It's a exe file, unless you've pulled the ROM zip from the RUU file.
Also, since you've started a separate thread regarding this same issue, I would stick to it to minimize any confusion instead of posting back & forth. Makes it easier to keep up with what's going on
it's the non-hk from htc's page I'm on mac but I pulled the zip from the exe using parallels desktop, I could try doing it on parallels desktop with the windows exe though
Just upgraded my T-Mobile M9 to Marshmallow and have been playing around with it. I've flashed TWRP and ElementalX 4.00, but I can't root it. Every time I do, it fails to boot. With systemless, it bootloops, and with the standard method, it gets stuck on one of the boot screens. Please help!
ROOT
Hey friend had the same problem as you couldnt get root on TMO MM update, but finally got it this morning by flashing SuperSU v2.62 in recovery and it stuck, so search in SuperSU thread for link to it, hope this helps
I took the OTA then loaded TWRP 3.0 and loaded the SuperSU Beta (2.67 I believe) and had problems with boot loop. I went back into twrp and loaded the current stable ver 2.65 and it worked fine.
kelvin216 said:
Hey friend had the same problem as you couldnt get root on TMO MM update, but finally got it this morning by flashing SuperSU v2.62 in recovery and it stuck, so search in SuperSU thread for link to it, hope this helps
Click to expand...
Click to collapse
ThePhoneGeek said:
I took the OTA then loaded TWRP 3.0 and loaded the SuperSU Beta (2.67 I believe) and had problems with boot loop. I went back into twrp and loaded the current stable ver 2.65 and it worked fine.
Click to expand...
Click to collapse
Thanks, both of you guys. Finally got it rooted.
Can anyone details the steps for this
I have S-Off rooted stock 5.1 currently. I would like to do a clean install of MM and the re-root.
I assume I need to
1. Wipe phone with Twrp
2. Flash stock recovery (do I need to wipe again with stock?)
3. Take the OTA
4. Flash Twrp again
5. Flash SuperSU 2.6.5
Is that it?
DssTrainer said:
Can anyone details the steps for this
I have S-Off rooted stock 5.1 currently. I would like to do a clean install of MM and the re-root.
I assume I need to
1. Wipe phone with Twrp
2. Flash stock recovery (do I need to wipe again with stock?)
3. Take the OTA
4. Flash Twrp again
5. Flash SuperSU 2.6.5
Is that it?
Click to expand...
Click to collapse
OR just flash the MarshMallow RUU that's available and have have those steps taken care of. Then Install TWRP and SuperSU.
But as far as kernels go ElementalX didn't work for me.
@rgao007 how did the kernel work for you? I couldn't get Signal when I flashed it.
Tachi91 said:
OR just flash the MarshMallow RUU that's available and have have those steps taken care of. Then Install TWRP and SuperSU.
But as far as kernels go ElementalX didn't work for me.
@rgao007 how did the kernel work for you? I couldn't get Signal when I flashed it.
Click to expand...
Click to collapse
ElementalX worked fine for me. Are you sure you flashed 4.00?
Tachi91 said:
OR just flash the MarshMallow RUU that's available and have have those steps taken care of. Then Install TWRP and SuperSU.
But as far as kernels go ElementalX didn't work for me.
@rgao007 how did the kernel work for you? I couldn't get Signal when I flashed it.
Click to expand...
Click to collapse
Ok just tried flashing the RUU to my phone. It failed: Error 155 Unknown Error
Now my phone stuck at the download screen.
I followed RUU to try to recover and it tried again, but same error.
I'll better explain my current settings
HTC One M9 Tmobile 5.1
S-Off with Sunshine
TWRP installed and rooted
I want to goto Marshmallow. I know I can't take OTA so I downloaded the RUU here:
http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
Then tried to run it and update my phone.
So what did I do wrong and how can I get my phone back?
Thanks
-EDIT- from what i've read online I need to relock my bootloader. But not sure how to get out of this download mode screen. Holding the powerbutton for 30 secs does nothing.
DssTrainer said:
Ok just tried flashing the RUU to my phone. It failed: Error 155 Unknown Error
Now my phone stuck at the download screen.
I followed RUU to try to recover and it tried again, but same error.
I'll better explain my current settings
HTC One M9 Tmobile 5.1
S-Off with Sunshine
TWRP installed and rooted
I want to goto Marshmallow. I know I can't take OTA so I downloaded the RUU here:
http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
Then tried to run it and update my phone.
So what did I do wrong and how can I get my phone back?
Thanks
Click to expand...
Click to collapse
Wrong RUU there buddy, that's lollipop.
Heres the Marshmallow RUU
http://dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
Before flashing the RUU make sure you have the correct T-Mobile CID and MID.
Tachi91 said:
Wrong RUU there buddy, that's lollipop.
Heres the Marshmallow RUU
http://dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
Before flashing the RUU make sure you have the correct T-Mobile CID and MID.
Click to expand...
Click to collapse
Actually their page has been updated it seems. Same file name as the one you linked
http://screencast.com/t/FXrLl5tYoXB7
It's updated now and the file is the same as the one you linked.
Either way even if I was flashing lollipop again it still shouldn't fail.
Error 155 points to unlocked bootloader issues. Is that an issue? Do I need to re-lock to flash MM?
Do I need to flash stock recovery back first?
I set the mid and cid to tmobile when I first unlocked it.
---------- Post added at 10:16 PM ---------- Previous post was at 09:48 PM ----------
Ok I locked the bootloader, checked my MID and CID.. all looks correct
Code:
c:\sdk\platform-tools>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELock successfully...
OKAY [ 0.090s]
finished. total time: 0.091s
c:\sdk\platform-tools>fastboot devices
FA53XYJ12302 fastboot
c:\sdk\platform-tools>fastboot getvar mid
mid: 0PJA120
finished. total time: 0.003s
c:\sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.053s]
finished. total time: 0.054s
c:\sdk\platform-tools>
---------- Post added at 10:24 PM ---------- Previous post was at 10:16 PM ----------
Ok bootloader locked.... Just tried again.. Error 155 again
Maybe I need to flash stock recovery and try the OTA
---------- Post added at 10:32 PM ---------- Previous post was at 10:24 PM ----------
Ok now I see if you are s-off you shouldn't need to relock bootloader.
Then wtf.
DssTrainer said:
Actually their page has been updated it seems. Same file name as the one you linked
http://screencast.com/t/FXrLl5tYoXB7
It's updated now and the file is the same as the one you linked.
Either way even if I was flashing lollipop again it still shouldn't fail.
Error 155 points to unlocked bootloader issues. Is that an issue? Do I need to re-lock to flash MM?
Do I need to flash stock recovery back first?
I set the mid and cid to tmobile when I first unlocked it.
---------- Post added at 10:16 PM ---------- Previous post was at 09:48 PM ----------
Ok I locked the bootloader, checked my MID and CID.. all looks correct
Code:
c:\sdk\platform-tools>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELock successfully...
OKAY [ 0.090s]
finished. total time: 0.091s
c:\sdk\platform-tools>fastboot devices
FA53XYJ12302 fastboot
c:\sdk\platform-tools>fastboot getvar mid
mid: 0PJA120
finished. total time: 0.003s
c:\sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.053s]
finished. total time: 0.054s
c:\sdk\platform-tools>
---------- Post added at 10:24 PM ---------- Previous post was at 10:16 PM ----------
Ok bootloader locked.... Just tried again.. Error 155 again
Maybe I need to flash stock recovery and try the OTA
---------- Post added at 10:32 PM ---------- Previous post was at 10:24 PM ----------
Ok now I see if you are s-off you shouldn't need to relock bootloader.
Then wtf.
Click to expand...
Click to collapse
Either theres typo, but this is what I get for MID
Code:
C:\Users\lvale\Desktop>fastboot getvar mid
mid: 0PJA12000
finished. total time: -0.000s
Idk if RUU is that stingy for a couple extra zeros missing. Make sure you write the MID with all the zeros like mine.
Also try flashing the rom.zip itself. When the RUU opens up use TaskManager to find the file and in that same directory is a rom.zip and the HTC fastboot witch will allow you to use flash the rom.zip and youll see the verbose output instead of the RUU just saying it failed for whatever reason.
Save the fastboot.exe(In RUU temp folder) since its modified to allow you to flash huge zip files.
Tachi91 said:
Either theres typo, but this is what I get for MID
Code:
C:\Users\lvale\Desktop>fastboot getvar mid
mid: 0PJA12000
finished. total time: -0.000s
Idk if RUU is that stingy for a couple extra zeros missing. Make sure you write the MID with all the zeros like mine.
Also try flashing the rom.zip itself. When the RUU opens up use TaskManager to find the file and in that same directory is a rom.zip and the HTC fastboot witch will allow you to use flash the rom.zip and youll see the verbose output instead of the RUU just saying it failed for whatever reason.
Save the fastboot.exe(In RUU temp folder) since its modified to allow you to flash huge zip files.
Click to expand...
Click to collapse
Ok I'll try later today and let you know.
Thanks for the help
Ok I updated my mid and actually redownloaded the RUU file just in case.. This time all went perfect!
Thanks for your help! Funny that I was able to flash it initially without the missing zeros.. if that was the actual inhibitor... It was an unlocked AT&T model that I brought to Tmobile and after setting the MID and CID with less zeros, I was able to flash the tmus version of lollipop without issue.
In any case, Thanks all for the help Time for me to enjoy some marshmallow love
okay i can't get the MM RUU to install on my M9
I have a rooted stock rom
TWRP
S-ON and Bootloader unlocked
When i first ran the RUU I got error 131 Customer ID
So i checked my MID and CID, they seem okay.
I locked the bootloader and tried using the RUU again via download mode, same error
so I needed my phone back for work next the day so i unlocked my bootloader again and restored a recovery I created early. any ideas on what i should do?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar mid
mid: 0PJA12000
finished. total time: -0.000s
please help me. i have a htc one m9. t mobile, 0PJA120, it keeps restartin. how can i get its original zip file to flash. it is not recognising any pc through usb.