Related
I'm currently trying to upgrade to the latest firmware and I'm having trouble with the process. I have the Bootloader unlocked and S-off. Any ideas on why the firmware zip is not flashing? Any help is appreciated, Thanks!
C:\adb>fastboot reboot
rebooting...
finished. total time: 5.554s
C:\adb>adb reboot bootloader
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
progressive_edm said:
I'm currently trying to upgrade to the latest firmware and I'm having trouble with the process. I have the Bootloader unlocked and S-off. Any ideas on why the firmware zip is not flashing? Any help is appreciated, Thanks!
C:\adb>fastboot reboot
rebooting...
finished. total time: 5.554s
C:\adb>adb reboot bootloader
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash zip C:\adb\firmware.zip
error: cannot load 'C:\adb\firmware.zip'
Click to expand...
Click to collapse
be abit clearer with what youre asking. are you trying to get the latest stock 4.2.2 that has recently came out? or are you actually trying to update the firmware?
Luke-b said:
be abit clearer with what youre asking. are you trying to get the latest stock 4.2.2 that has recently came out? or are you actually trying to update the firmware?
Click to expand...
Click to collapse
I'm trying to update the actual firmware (2.24.401.12)
progressive_edm said:
I'm trying to update the actual firmware (2.24.401.12)
Click to expand...
Click to collapse
in what format do you have this update you say you have a .ZIP what zip is this?
you say you are s-off so to get this update i would return your Rom and recovery both to stock and then check your Cid and if its available for you CID recieve the OTA update to change your CID and MID so you can receive it.
The OTA update will update everything. so your firmware, update it to 2.24.401.12 and also to the latest radio
Luke-b said:
in what format do you have this update you say you have a .ZIP what zip is this?
you say you are s-off so to get this update i would return your Rom and recovery both to stock and then check your Cid and if its available for you CID recieve the OTA update to change your CID and MID so you can receive it.
The OTA update will update everything. so your firmware, update it to 2.24.401.12 and also to the latest radio
Click to expand...
Click to collapse
I'ts the (2.24.401.12) firmware zip. Got it from Vomer's post if that helps http://forum.xda-developers.com/showthread.php?t=2183023&page=2496 . And i thought with having S-off you could just update without worrying about the Cid and Mid? I will take your suggestion into consideration, thanks.
Yes you can update the firmware without changing the cid and mid. But that only refers to the hboot. For full upgrade to 4.2.2 if it's not already available for your cid then you would need to change the cid and mid to receive it. And remember to have a stock recovery. There are guides available if you look through the thread about the update people have posted how to do this. It's Easiest and safest way to do this.
fastboot commands to run RUU files will get you into trouble
Sent from my HTC One using xda app-developers app
I re-locked my phone with a custom recovery and attempted to unlock again and goes through successful though the unlock screen does not show up.(Probably because I have no OS installed?)
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check [COLOR="DeepSkyBlue"]successfully[/COLOR]
OKAY [ 0.003s]
finished. total time: 0.144s
My current information is:
*** Tampered ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXX
imei: XXXXXXXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum:[COLOR="DeepSkyBlue"]GOOGL001[/COLOR]
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
Ive tried the method below with a few RUU's though I keep getting the error "FAILED (remote: 12 signature verify fail)" Their must some RUU that I can flash that correlates to my above information?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Code:
C:\Users\chanik\Desktop\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fa
stboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388870 KB)...
OKAY [ 15.220s]
writing 'zip'...
(bootloader) signature checking...
[COLOR="Red"]FAILED (remote: 12 signature verify fail)[/COLOR]
finished. total time: 53.263s
If someone could confirm I have fully bricked my device that be great so i can move on with my life
I foundout that i dont have a mainvar... is tjis bad?
ronniereiff said:
I foundout that i dont have a mainvar... is tjis bad?
Click to expand...
Click to collapse
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk
nkk71 said:
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Twrp, though i am unable to use it due to being relocked..
ronniereiff said:
Twrp, though i am unable to use it due to being relocked..
Click to expand...
Click to collapse
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please
nkk71 said:
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please
Click to expand...
Click to collapse
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread
ronniereiff said:
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread
Click to expand...
Click to collapse
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).
nkk71 said:
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).
Click to expand...
Click to collapse
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.
ronniereiff said:
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.
Click to expand...
Click to collapse
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.
nkk71 said:
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.
Click to expand...
Click to collapse
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.
ronniereiff said:
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.
Click to expand...
Click to collapse
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
I have successfully unlocked after flashing the 3.58.1700.5 kitkat firmware Just need to see how to get kitkat now
nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.
ronniereiff said:
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.
Click to expand...
Click to collapse
Cache unable to mount is ok, it's because it's wiped, so don't worry about that.
To be able to flash a 4.4 ROM, you need TWRP 2.6.3.3 or above, but since you're S-On you cannot flash a GPE 4.4 ROM as they require S-Off.
Use adb sideload, adb push, or OTG cable to get a ROM to TWRP.
Hit the thanks button if i've helped
nkk71 said:
Hit the thanks button if i've helped
Click to expand...
Click to collapse
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff
ronniereiff said:
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff
Click to expand...
Click to collapse
Can you post where did you get the rom you flashed?
It's been awhile since I've done any sort of updating on my HTC One and it's kind of worrying me now. Since I've got my phone, I've unlocked the boot loader, rooted it, installed TWRM as my recovery and I've used CyanogenMod's ROM's (now 4.4.2).
However, I've never once updated "firmware" because I'm not sure how. I've never really updated anything whatsoever apart from my ROM/TWRP and it's got me a bit worried that every thing is so out of date. I see that I'm supposed to update kernels, firmware, hboot, etc? Is this a huge deal and how do I do this safely?
Today I got super CID over with along with removed tampered from my bootloader screen. I'm also S-Off from moving to Kitkat CM.
Can someone please help me get my phone completely up to date? I also have this constant "Superuser binaries are out of date" pop up and when I reboot into TWRP, it doesn't download anything. It's annoying as ****.
Leather Sock said:
It's been awhile since I've done any sort of updating on my HTC One and it's kind of worrying me now. Since I've got my phone, I've unlocked the boot loader, rooted it, installed TWRM as my recovery and I've used CyanogenMod's ROM's (now 4.4.2).
However, I've never once updated "firmware" because I'm not sure how. I've never really updated anything whatsoever apart from my ROM/TWRP and it's got me a bit worried that every thing is so out of date. I see that I'm supposed to update kernels, firmware, hboot, etc? Is this a huge deal and how do I do this safely?
Today I got super CID over with along with removed tampered from my bootloader screen. I'm also S-Off from moving to Kitkat CM.
Can someone please help me get my phone completely up to date? I also have this constant "Superuser binaries are out of date" pop up and when I reboot into TWRP, it doesn't download anything. It's annoying as ****.
Click to expand...
Click to collapse
I would suggest going into superuser apk on phone and try updating binaries through that. If not when it goes to tqrp asking for binaries update try update on that. And if you go to bootloader. So restart phone while holding vol down. See what hboot and firmware it says. But if I'm honest I'm not sure if cm is different to usual stock roms
Sent from my C6833 using Tapatalk
Leather Sock said:
I also have this constant "Superuser binaries are out of date" pop up and when I reboot into TWRP, it doesn't download anything. It's annoying as ****.
Click to expand...
Click to collapse
if you're using superuser (as opposed to SuperSU), TWRP doesn't automatically go to the correct folder to install it, you need to manually (in TWRP) go to:
/data/data/com.koushidutta.superuser/files
then you will see superuser.zip which you can install to update binaries.
nkk71 said:
if you're using superuser (as opposed to SuperSU), TWRP doesn't automatically go to the correct folder to install it, you need to manually (in TWRP) go to:
/data/data/com.koushidutta.superuser/files
then you will see superuser.zip which you can install to update binaries.
Click to expand...
Click to collapse
Thank you so much. Alright, so the Superuser issue is now resolved and I know how to resolve it in the future now too! However, to give an idea of what I'm currently at, this is what my device is using in terms of what's shown on my bootloader screen thing:
M7_UL PVT Ship S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.17.3250.20
How bad is that?
Leather Sock said:
Thank you so much. Alright, so the Superuser issue is now resolved and I know how to resolve it in the future now too! However, to give an idea of what I'm currently at, this is what my device is using in terms of what's shown on my bootloader screen thing:
M7_UL PVT Ship S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.17.3250.20
How bad is that?
Click to expand...
Click to collapse
S-OFF = very good
what you need?
also please post (copy/paste) a "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
S-OFF = very good
what you need?
also please post (copy/paste) a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.17.3250.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.26.502.15
INFOversion-misc: PVT SHIP S-OFF
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3976mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.144s
nkk71 said:
S-OFF = very good
what you need?
also please post (copy/paste) a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
I just want to be up to date with all of the updates and stuff. I know there's "Hboot" updates and firmware updates and etc, etc. But, I don't know how important those are or what's best.
Leather Sock said:
I just want to be up to date with all of the updates and stuff. I know there's "Hboot" updates and firmware updates and etc, etc. But, I don't know how important those are or what's best.
Click to expand...
Click to collapse
what ROM you running / wanna run?
with S-Off you can upgrade/downgrade anything anytime you like, i (personal choice) use the collection of @vomer's guide (Section2): http://forum.xda-developers.com/showthread.php?t=2365506
I'm using 4.19.401.8 with ARHD 51.0 and working perfectly.
nkk71 said:
what ROM you running / wanna run?
with S-Off you can upgrade/downgrade anything anytime you like, i (personal choice) use the collection of @vomer's guide (Section2): http://forum.xda-developers.com/showthread.php?t=2365506
I'm using 4.19.401.8 with ARHD 51.0 and working perfectly.
Click to expand...
Click to collapse
So using different hboots/firmware upgrades is only to use different roms? I read somewhere that you're supposed to keep hboot up to date to newest version for performance increases and stuff. It's all very confusing to me.
Right now I'm using ARHD GPe 6.1 and it's not bad. I was using CM11 but I want to wait a few months for it to get a little more stable.
Bump please
Leather Sock said:
So using different hboots/firmware upgrades is only to use different roms? I read somewhere that you're supposed to keep hboot up to date to newest version for performance increases and stuff. It's all very confusing to me.
Right now I'm using ARHD GPe 6.1 and it's not bad. I was using CM11 but I want to wait a few months for it to get a little more stable.
Click to expand...
Click to collapse
so far (for the HTC One M7 at least) upgrading firmware is as mentioned in the OP of ARHD
Firmware package from here (recommended but not needed for now)
Click to expand...
Click to collapse
--> not necessary, but recommended.
recommended to have the firmware the same version as ROM, because as you mentioned (at least supposedly/theoretically) better performance, stability, battery, etc.
nkk71 said:
so far (for the HTC One M7 at least) upgrading firmware is as mentioned in the OP of ARHD
--> not necessary, but recommended.
recommended to have the firmware the same version as ROM, because as you mentioned (at least supposedly/theoretically) better performance, stability, battery, etc.
Click to expand...
Click to collapse
How do I install firmware upgrades? Do I have to reinstall the ROM after?
Leather Sock said:
How do I install firmware upgrades? Do I have to reinstall the ROM after?
Click to expand...
Click to collapse
you flash firmware in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip <name of firmware file>.zip
fastboot flash zip <name of firmware file>.zip <- yes TWICE!!
fastboot reboot-bootloader
since you're s-off, you can flash any firmware you like (upgrade & downgrade, signed or unsiged)
I usually use Vomer's firmwares from here: http://forum.xda-developers.com/showthread.php?t=2365506
(cause they have recovery.img and boot.img already removed, i'll get to that in a second)
But there are other, such as:
http://forum.xda-developers.com/showthread.php?t=2316726
or
http://xda7.androidrevolution.nl/db_mirror/Firmware/index.php?dir=HTC/HTC_One/ (those are original signed packages i think)
You should check the contents of the zip, for
recovery.img -> that would overwrite your custom recovery and you would have to flash it again
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
boot.img (the kernel) -> that would overwrite the kernel that comes part of the ROM
you either dirty-flash the ROM again, or extract "boot.img" from the ROM.zip and
fastboot flash boot boot.img
(that's boot NOT hboot, don't ever do fastboot flash hboot, EVER!!!)
you can also try different radios from here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable in custom recovery)
Does anyone know where I can get the lollipop RUU update for an unlocked Att HTC m7?
This is the stock RUU- RUU M7 UL JB 50 Cingular US 1.26.502.12 that flashes JB onto it. Need the Lollipop update
This is the radio :Radio 4A.14.3250.13
I tried both RUUs (ATT 7.23.502.1 did not work & HTC International 7.17.1540.7 did not work) on the HTC site and it didnt work the wizard said model error so am at a loss to which one it could be. Any help to locate the appropriate ROM for my phone please?
Quake105 said:
Does anyone know where I can get the lollipop RUU update for an unlocked Att HTC m7?
This is the stock RUU- RUU M7 UL JB 50 Cingular US 1.26.502.12 that flashes JB onto it. Need the Lollipop update
This is the radio :Radio 4A.14.3250.13
I tried both RUUs (ATT 7.23.502.1 did not work & HTC International 7.17.1540.7 did not work) on the HTC site and it didnt work the wizard said model error so am at a loss to which one it could be. Any help to locate the appropriate ROM for my phone please?
Click to expand...
Click to collapse
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
is for AT&T M7, what error did you get? post a "fastboot getvar all" excluding IMEI and s/n
and a screenshot of bootloader
Feedback 1 ATT HTC M7 Lollipop Update
is for AT&T M7, what error did you get? post a "fastboot getvar all" excluding IMEI and s/n
and a screenshot of bootloader[/QUOTE]
Thanks for the link the to the RUU. It didnt work I got an error. The displayed error 158 (invalid ROM).
Here are the screen shots ......................
nkk71 said:
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
is for AT&T M7, what error did you get? post a "fastboot getvar all" excluding IMEI and s/n
and a screenshot of bootloader
Click to expand...
Click to collapse
Quake105 said:
is for AT&T M7, what error did you get? post a "fastboot getvar all" excluding IMEI and s/n
and a screenshot of bootloader
Thanks for the link the to the RUU. It didnt work I got an error. The displayed error 158 (invalid ROM).
Here are the screen shots ......................
Click to expand...
Click to collapse
afaik, we need to be at least on kitkat firmware (at least 6.xx.xxx.x). to be able to flash lollipop RUU (7.xx.xxx.x)
Try to flash the 7.23.502.1 stock firmware first (complete firmware not firmware from ota) then the 7.23.502.1 RUU or try an older RUU like the 3.17.502.3 version.
Update 3.17.502.3 successful but stuck there no 7.23.502.1
alray said:
afaik, we need to be at least on kitkat firmware (at least 6.xx.xxx.x). to be able to flash lollipop RUU (7.xx.xxx.x)
Try to flash the 7.23.502.1 stock firmware first (complete firmware not firmware from ota) then the 7.23.502.1 RUU or try an older RUU like the 3.17.502.3 version.
Click to expand...
Click to collapse
Thanks @alray. I have been able to update to version 3.17.502.3 but when I try to update to lollipop 7.23.502.1 using the ATT HTC M7 RUU from the htc site it fails.
It gives me Unkown error 155. ''Connect USB cable to android device". I use fast boot and the installation wizard crashed with Windows message: '' htc fastboot.exe has stopped working''. I have tried several times making sure the android drivers have been installed. Should I check for some special drivers?
Please help to complete final update to lollipop.
Quake105 said:
Thanks @alray. I have been able to update to version 3.17.502.3 but when I try to update to lollipop 7.23.502.1 using the ATT HTC M7 RUU from the htc site it fails.
It gives me Unkown error 155. ''Connect USB cable to android device". I use fast boot and the installation wizard crashed with Windows message: '' htc fastboot.exe has stopped working''. I have tried several times making sure the android drivers have been installed. Should I check for some special drivers?
Please help to complete final update to lollipop.
Click to expand...
Click to collapse
Like I said above, you need to be at least on 6.xx.xxx.x or 7.xx.xxx.x firmware to be able to flash a 7.23.502.1 RUU. Flash the 7.23.502.1 firmware then flash the 7.23.502.1 RUU zip.
And the 155 error is a usb problem. Check you cable, check usb ports, make sure to be connected directly on the computer (not using any external usb hub)
How to flash firmware.zip
@alray can you show me how to flash the 1st stage firmware.zip (6xx.xxx.x) you sent unto the att m7 please? Want to sure to avoid bricking.
Quake105 said:
@alray can you show me how to flash the 1st stage firmware.zip (6xx.xxx.x) you sent unto the att m7 please? Want to sure to avoid bricking.
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then flash the ruu using htc_fatsboot. Download it and save it in the same folder you have your normal fastboot.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign.
So I started to read. First I've read that I need to unlock bootloader, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help
See comment in red below
qwe1234 said:
Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign. Indicating that your software partition isn't 100% stock. The ota update will only replace the required files to be updated, not the whole system. Before updating, the updater-script check integrity of all files to be updated. If only one of these file isn't as expected, the updater-script will abort and the update will not install ----> red triangle
So I started to read. First I've read that I need to unlock bootloader bootloader lock/unlock status isn't related to ota update, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device You don't need root to install firmware. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found indicating that you are not using the correct file. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference The sprint variant is a CDMA phone). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000 old bootloader version not matching your software version
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls twrp 2.5.0.0 is really outdated and won't work with recent files. Not a problem for now since you will not need to use twrp to fix it, just fyi
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help
Click to expand...
Click to collapse
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.
My friend Thank You very much for all the instructions... but...
Last step:
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Click to expand...
Click to collapse
ended with error ;(
fastboot gave following:
processing file 2/5...
error: cannot load 'C:\Users\x101ch\AppData\Local\Temp\tmpp6r0paxd'
htc_fastboot finished. total time: 297.909s
Phone restarted once in the middle like you said.
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
One more thing. I haven't noticed that you changed command from fastboot to htc_fastboot so I changed htc_fastboot file name to just fastboot and used command fastboot. Don't know if it matters...
qwe1234 said:
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
Click to expand...
Click to collapse
Now you probably understand why I said
if something goes wrong post here and wait (do not skip any steps).
Click to expand...
Click to collapse
Rebooting after a failed/incomplete flash can hard brick your phone. If you can't get fastboot connectivity again, there is not much you can do. Sorry
Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?
qwe1234 said:
Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?
Click to expand...
Click to collapse
maybe or let the battery drain then plug the phone again and try to boot in bootloader with vol down and power.
Ok. I will try to do that tomorrow and will post the result. Thanks again
Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult
qwe1234 said:
Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult
Click to expand...
Click to collapse
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)
alray said:
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s
qwe1234 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s
Click to expand...
Click to collapse
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work
alray said:
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work
Click to expand...
Click to collapse
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again
qwe1234 said:
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again
Click to expand...
Click to collapse
:good:
you're welcome!
So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?
qwe1234 said:
So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?
Click to expand...
Click to collapse
So it looks like I'm stupid.
I tried to unlock the phone. Again bootloader unlocked, phone rooted. I wanted to unlock it with terminal commands using HtcOMADM_SPCS but I cannot install it. I've installed twrp (this time version 3.1.1.0) but it keeps saying that footer is wrong and signature verification failed...
Any more help, please? ;(
Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
I'm getting crickets on my thread, and just needed a general confirmation on the process again since it's been awhile.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Just confirming the process you described would still work the same way.
Thanks!
alray said:
See comment in red below
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.
Click to expand...
Click to collapse
cloud66 said:
Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
Click to expand...
Click to collapse
Since yours is also a Sprint HTC One, yes the same procedure should work.
I'm getting crickets on my thread
Click to expand...
Click to collapse
quote me next time and I'll be notified, just like you did in this thread.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Click to expand...
Click to collapse
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img
alray said:
quote me next time and I'll be notified, just like you did in this thread.
Click to expand...
Click to collapse
Hey again. Alray can I ask you for a little bit more help? I've tried every way to sim unlock i found but without any success. Last method I used was from this video: https://www.youtube.com/watch?v=e6hHUae1TMs but when I want to run Unlock helper it crashes. Have no idea what am I doing wrong...;(
alray said:
Since yours is also a Sprint HTC One, yes the same procedure should work.
quote me next time and I'll be notified, just like you did in this thread.
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img
Click to expand...
Click to collapse
Hey so looks like I'm running into an issue when updating my firmware.
I'm getting this:
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware and no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues.
Also flashed twrp recovery without any issues.
Rom is still working, everything is still normal....
Thoughts?
Also wanted to add that I was able to update TWRP to 3.1 and flash ICE ROM 7.1.1 and gapps without any issues. So far running semi-stable.
Tried updating firmware with s-on after i re-locked my bootloader, but that did not work either. I was still getting some weird error so I unlocked my bootloader again and then was able to flash the nougat rom just fine. It's strange that it's working with such an older version of the firmware... oh well.
Will still hold out for any suggestions. I'm sure I will run into some issues soon with the firmware being that out-of-date. Signal issues, battery issues, etc.