Hi everybody,
Normally i dont get stuck but this time ive hit a rock, basically Ive got a HTC One which then had the bootloader unlocked and a GE ROM with CWM installed.
What I did was possibly stupid as i S-Offed to clear the tampered/relocked status and before running the stock RUU I relocked the bootloader and S-Oned (this is to later sell the handset as close to stock as possible).
What happens now is the phone will boot into the bootloader/fastboot with a TAMPERED/LOCKED/Security Warning status however any attempt to flash ZIP will backfire in signature verify failed.
Ive tried any number of RUU/img/recovery/ZIPs to get it functioning however the closest I've been is using the rom.zip from "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe" which stalled due to the main-version being above the RUU.
My info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
- to note it was ORANG001 before i changed the CID to HTC__001
From what i can tell as i cant boot into anything i cant get S-OFF or unlock the bootloader again, can anyone think of a way to either downgrade/edit the main-version or make it skip the check?
Thanks in advance
PaulusJ93 said:
Hi everybody,
Normally i dont get stuck but this time ive hit a rock, basically Ive got a HTC One which then had the bootloader unlocked and a GE ROM with CWM installed.
What I did was possibly stupid as i S-Offed to clear the tampered/relocked status and before running the stock RUU I relocked the bootloader and S-Oned (this is to later sell the handset as close to stock as possible).
What happens now is the phone will boot into the bootloader/fastboot with a TAMPERED/LOCKED/Security Warning status however any attempt to flash ZIP will backfire in signature verify failed.
Ive tried any number of RUU/img/recovery/ZIPs to get it functioning however the closest I've been is using the rom.zip from "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe" which stalled due to the main-version being above the RUU.
My info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
- to note it was ORANG001 before i changed the CID to HTC__001
From what i can tell as i cant boot into anything i cant get S-OFF or unlock the bootloader again, can anyone think of a way to either downgrade/edit the main-version or make it skip the check?
Thanks in advance
Click to expand...
Click to collapse
You need s-off to use that ruu (1.28.401) and you need to downgrade hboot to 1.44.
can you still boot in cwm? Why can't you unlock the bootloader again?
alray said:
You need s-off to use that ruu (1.28.401) and you need to downgrade hboot to 1.44.
can you still boot in cwm? Why can't you unlock the bootloader again?
Click to expand...
Click to collapse
It wont boot into anything but the bootloader, i cant unlock the bootloader as when trying to push the unlock code the error "FAILED (remote: unlock token check failed)" is generated.
In my current sticky situation would there be anyway to get an older hboot or the ENG hboot on the device?
PaulusJ93 said:
It wont boot into anything but the bootloader, i cant unlock the bootloader as when trying to push the unlock code the error "FAILED (remote: unlock token check failed)" is generated.
In my current sticky situation would there be anyway to get an older hboot or the ENG hboot on the device?
Click to expand...
Click to collapse
are you using the same token you used to unlock the bootloader for the first time?
alray said:
You need s-off to use that ruu (1.28.401) and you need to downgrade hboot to 1.44.
can you still boot in cwm? Why can't you unlock the bootloader again?
Click to expand...
Click to collapse
alray said:
are you using the same token you used to unlock the bootloader for the first time?
Click to expand...
Click to collapse
That is something i dont know as it wasnt me who unlocked it first, ive generated it twice from HTCDev and tried applying via Mac and Windows
PaulusJ93 said:
That is something i dont know as it wasnt me who unlocked it first, ive generated it twice from HTCDev and tried applying via Mac and Windows
Click to expand...
Click to collapse
can you post a screenshot of your cmd prompt?
alray said:
can you post a screenshot of your cmd prompt?
Click to expand...
Click to collapse
Added below for you
PaulusJ93 said:
Added below for you
Click to expand...
Click to collapse
and your unlock_code.bin was generated with this identifier token from htcdev?
alray said:
and your unlock_code.bin was generated with this identifier token from htcdev?
Click to expand...
Click to collapse
Yes, also done with an unlock_code.bin generated from the token on the last attempt before too.
sorry for the bump?
any further ideas? I've looked at possibly decrypting a rom.zip and altering the version numbers so it will play ball however again it looks like it will need S-Off to flash that edited zip without HTCs private encryption.
Can anyone help?
Im still stuck and unable to unlock the bootloader.
Related
Ok, this is my fasboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
My phone is back to completely stock now and I need to return to s-on for repairs
What does the dirty bootloader mean and how will that affect my phone if I do fastboot oem writesecureflag 3?
stovie_steve said:
What does the dirty bootloader mean
Click to expand...
Click to collapse
touch of jobo said:
The commit number refers to the code repository that devs at HTC use. Every time a dev commits code to the repo, that commit gets a unique number.
Their build server checks out the repo and adds the latest commit number to some macro or header, so that products can report it.
A dirty build only recompiles the files that were modified and their dependencies. A clean build removes all object code and recompiles everything.
So the commitno is an identifier that HTC devs can use to go back in time and checkout the exact same code that your hboot was built from.
Click to expand...
Click to collapse
stovie_steve said:
how will that affect my phone if I do fastboot oem writesecureflag 3?
Click to expand...
Click to collapse
It will turn you phone back to S-ON and it will look like this:
stovie_steve said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Lol I know it will do that, but will it result in a tampered message in my bootloader even if I'm completely back to stock, no modified hboot and locked bootloader?
stovie_steve said:
Lol I know it will do that, but will it result in a tampered message in my bootloader even if I'm completely back to stock, no modified hboot and locked bootloader?
Click to expand...
Click to collapse
it shouldn't
Many thanks for replying
I originally downgraded my hboot to 1.44 after getting s off with rumrunner. I then restored a 1.29 base nandroid and proceeded to take all the ota updates for my 02___001 cid. So this would have flashed stock Rom, stock recovery and stock hboot yes? So going to s on should work yes?
stovie_steve said:
Many thanks for replying
I originally downgraded my hboot to 1.44 after getting s off with rumrunner. I then restored a 1.29 base nandroid and proceeded to take all the ota updates for my 02___001 cid. So this would have flashed stock Rom, stock recovery and stock hboot yes? So going to s on should work yes?
Click to expand...
Click to collapse
yes it should work without any issue
It didn't work!
When I reboot my phone I got a message saying tampered detected - rebooting
Now my phone reads locked, tampered and s-on
stovie_steve said:
It didn't work!
When I reboot my phone I got a message saying tampered detected - rebooting
Now my phone reads locked, tampered and s-on
Click to expand...
Click to collapse
you should never have gone back to s-on, the only way to get rid of the tampered is to run a RUU, now you are s-on you will no longer be able to do this. so you will be stuck now with what you have I believe, you can remove tampered but you need to be s-off to run code.
sorry, believe you are stuck where you are.
scifitrekkie said:
you should never have gone back to s-on, the only way to get rid of the tampered is to run a RUU, now you are s-on you will no longer be able to do this. so you will be stuck now with what you have I believe, you can remove tampered but you need to be s-off to run code.
sorry, believe you are stuck where you are.
Click to expand...
Click to collapse
No I am not stuck where I am - I can unlock the bootloader again via HTC dev, install custom recovery and do a Guru reset to achieve S-off again. I've done this before.
I can get s-off again and I have a RUU for a stock european firmware. I can change my CID for HTC__001 and update right up to 3.62.401.1 firmware. That'll put my device to complete stock
Do HTC know that my device was originally locked to O2-UK?
If so, will o2 care that my phone is s-off? Cos I can get s-off and leave the bootloader locked
Hello,
I was trying to root my device, i unlocked bootloader and installed custom recovery, i did something wrong on the way and im not sure what.
currently the bootloader shows: "TAMPERED" and "RELOCKED".
i wanted to install RUU and i dont know what RUU i should install.
Thanks for helpers!
additional information :
fastboot getvar version-main
version-main:
***why is it blank??
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4D.18.3250.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4171mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alon121 said:
Hello,
I was trying to root my device, i unlocked bootloader and installed custom recovery, i did something wrong on the way and im not sure what.
currently the bootloader shows: "TAMPERED" and "RELOCKED".
i wanted to install RUU and i dont know what RUU i should install.
Thanks for helpers!
additional information :
fastboot getvar version-main ****why is
version-main: ****it blank??
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4D.18.3250.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: WHAT UP HOMIE
(bootloader) imei: DONT SEE THIS
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4171mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey,
Just unlock it again. You didn't flash the stock recovery.img so you can't boot up into your ROM. Just unlock it and go through the process again. I see you are using t-mobile. just head over to THIS THREAD find 'RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250 .20_10.40.1150.04_release_324846_signed.exe' and run the exe. hope this helps man.
WHOOPSIE/ EDIT: Forgot to mention the S-off thanks for pointin that out
Bllooi said:
Hey,
Just unlock it again. You didn't flash the stock recovery.img so you can't boot up into your ROM. Just unlock it and go through the process again. I see you are using t-mobile. just head over to THIS THREAD find 'RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250 .20_10.40.1150.04_release_324846_signed.exe' and run the exe. hope this helps man.
Click to expand...
Click to collapse
do i have to unlock and flash stock recovery to install the RUU?
thank u for the help.
alon121 said:
do i have to unlock and flash stock recovery to install the RUU?
thank u for the help.
Click to expand...
Click to collapse
1- edit your post and remove IMEI and s/n
2- ask whoever quoted you to do the same
3- that RUU is not going to work, because:
......a- you are S-On, and for a downgrade to work you need to be S-Off
......b- the RUU isnt even meant for your model !!!!!
Code:
modelid: PN0713000
cid: T-MOB010
you have MID PN0710000 !!!!
from hboot & radio, your firmware should be 2.24.111.5 (German T-Mobile right?) or close to that, recommend you get S-Off using rumrunner.
so unlock bootloader, get yourself a suitable rom, and achieve s-off using rumrunner.
nkk71 said:
1- edit your post and remove IMEI and s/n
2- ask whoever quoted you to do the same
3- that RUU is not going to work, because:
......a- you are S-On, and for a downgrade to work you need to be S-Off
......b- the RUU isnt even meant for your model !!!!!
Code:
modelid: PN0713000
cid: T-MOB010
you have MID PN0710000 !!!!
from hboot & radio, your firmware should be 2.24.111.5 (German T-Mobile right?) or close to that, recommend you get S-Off using rumrunner.
so unlock bootloader, get yourself a suitable rom, and achieve s-off using rumrunner.
Click to expand...
Click to collapse
I unlocked my bootloader and got s-off.
should i flash a custom recovery?
can u point me at a suitable rom so i wont get a wrong one?
thanks.
alon121 said:
I unlocked my bootloader and got s-off.
should i flash a custom recovery?
can u point me at a suitable rom so i wont get a wrong one?
thanks.
Click to expand...
Click to collapse
quick question: do you want (need) to go back to stock? or are happy with custom ROMs?
(basically: what do you the end result to be?)
nkk71 said:
quick question: do you want (need) to go back to stock? or are happy with custom ROMs?
(basically: what do you the end result to be?)
Click to expand...
Click to collapse
actually i dont really care, right now i just want to update my software to kitkat, and currently it doesnt let me.
alon121 said:
actually i dont really care, right now i just want to update my software to kitkat, and currently it doesnt let me.
Click to expand...
Click to collapse
well kitkat isn't out yet except for the US Dev Edition, but you can try any of the ROMs in the development section, you can use @ClydeB1 Index for a list of different ROMs (and other very useful links) http://forum.xda-developers.com/showthread.php?t=2438026
Since you're now S-Off you can also use latest GPE ROMs (as they require S-Off), and also can flash different firmwares;
I usually use firmwares from http://forum.xda-developers.com/showthread.php?t=2365506
and radios from here http://forum.xda-developers.com/showthread.php?t=2419699
Also, at the moment the recommended recovery to use is TWRP 2.6.3.3 http://techerrata.com/browse/twrp2/m7
or TWRP 2.6.3.4 http://techerrata.com/browse/twrp2/m7ul
After upgrade to 4.4 my phone started to reboot randomly and display "Process com.htc.dialer isn't responding", so i flashed hboot 1.44 and installed new ruu now phone after boot is stuck on black screen and i can see only top bar with icons.
Phone is S-OFF
UNLOCKED
not rooted
below getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4238mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.344s
Any help would be great.
Okay so i flashed it again with same ruu now it load lock screen and aftter unlock it only shows white htc logo and after couple minutes reboot, after one reboot it goes back to being stuck on black screen.
ol3k1990 said:
After upgrade to 4.4 my phone started to reboot randomly and display "Process com.htc.dialer isn't responding", so i flashed hboot 1.44 and installed new ruu now phone after boot is stuck on black screen and i can see only top bar with icons.
Phone is S-OFF
UNLOCKED
not rooted
below getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4238mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.344s
Any help would be great.
Okay so i flashed it again with same ruu now it load lock screen and aftter unlock it only shows white htc logo and after couple minutes reboot, after one reboot it goes back to being stuck on black screen.
Click to expand...
Click to collapse
download 4.19.401.9 no wipe firmware from here and flash it in fastboot RUU mode: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml
Code:
fastboot oem rebootRUU
fastboot flash zip (name of firmware).zip
fastboot flash zip (name of firmware).zip - [B]yes twice[/B]
[B][I]if successful at the end then[/I][/B]
fastboot reboot-bootloader
[B][I]if failed, report back here before doing anything else.[/I][/B]
now with your phone in fastboot USB mode still, download and run this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Seanie280672 said:
download 4.19.401.9 no wipe firmware from here and flash it in fastboot RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip (name of firmware).zip
fastboot flash zip (name of firmware).zip - [B]yes twice[/B]
[B][I]if successful at the end then[/I][/B]
fastboot reboot-bootloader
[B][I]if failed, report back here before doing anything else.[/I][/B]
now with your phone in fastboot USB mode still, download and run this RUU
Click to expand...
Click to collapse
Hi, thanks for replaying
I did everyting above and after installing new ruu now is still rebooting the only difference it isstuck on white htc screen after lock screen and the Process com.htc.htcdialer error is showing again.
ol3k1990 said:
I did everyting above and after installing new ruu now is still rebooting the only difference it isstuck on white htc screen after lock screen and the Process com.htc.htcdialer error is showing again.
Click to expand...
Click to collapse
can you post a new fastboot getvar all please ?
Seanie280672 said:
can you post a new fastboot getvar all please ?
Click to expand...
Click to collapse
My new getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ----------------
(bootloader) imei: ------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.284s
ol3k1990 said:
My new getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVE THIS
(bootloader) imei: REMOVE THIS
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.284s
Click to expand...
Click to collapse
remove your imei and serial number please like ive done in the quote.
well the firmware flash went fine, if you notice you are now on HBOOT 1.56 and also have a version main, did the RUU flash ok ?
Seanie280672 said:
remove your imei and serial number please like ive done in the quote.
well the firmware flash went fine, if you notice you are now on HBOOT 1.56 and also have a version main, did the RUU flash ok ?
Click to expand...
Click to collapse
It went perfectly fine
ol3k1990 said:
It went perfectly fine
Click to expand...
Click to collapse
I would have to say it sounds like you have some sort of hardware problem going on there, maybe a bad nand.
you could try flashing twrp recovery and then doing a full format (format data) then try all of the above again, see if that works, if it still fails then id say it was down to hardware.
Seanie280672 said:
I would have to say it sounds like you have some sort of hardware problem going on there, maybe a bad nand.
you could try flashing twrp recovery and then doing a full format (format data) then try all of the above again, see if that works, if it still fails then id say it was down to hardware.
Click to expand...
Click to collapse
Thanks for replaying again ,
The phone is still under guarantee so if that wont help i will try to get it back to locked and s-off and then send it for service.
ol3k1990 said:
Thanks for replaying again ,
The phone is still under guarantee so if that wont help i will try to get it back to locked and s-off and then send it for service.
Click to expand...
Click to collapse
yes you can do that, but you will have to flash an earlier firmware and ruu before going s-on, with the later ones, like the one you have on there now, going s-on brings back the tampered flag.
Seanie280672 said:
yes you can do that, but you will have to flash an earlier firmware and ruu before going s-on, with the later ones, like the one you have on there now, going s-on brings back the tampered flag.
Click to expand...
Click to collapse
So it should be alright if i flash hboot 1.44 and install the ruu i used earlier.
ol3k1990 said:
So it should be alright if i flash hboot 1.44 and install the ruu i used earlier.
Click to expand...
Click to collapse
which ruu did you use earlier ?
Seanie280672 said:
which ruu did you use earlier ?
Click to expand...
Click to collapse
Cant post links yet but full name is
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
ol3k1990 said:
Cant post links yet but full name is
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Click to expand...
Click to collapse
yup that will be perfect, downgrade your hboot to 1.44, run the ruu.zip, make sure your firmware is downgraded to, it should be and then remove tampered flag from the bootloader if its still there, then lock the bootloader and s-on.
Seanie280672 said:
yup that will be perfect, downgrade your hboot to 1.44, run the ruu.zip, make sure your firmware is downgraded to, it should be and then remove tampered flag from the bootloader if its still there, then lock the bootloader and s-on.
Click to expand...
Click to collapse
Thanks for help
HTC supports Rooting so warranty may still be ok. Depending on your provider honoring it is another thing but I'm sure you can go directly to HTC if your provider has a problem with it.
bornthor said:
HTC supports Rooting so warranty may still be ok. Depending on your provider honoring it is another thing but I'm sure you can go directly to HTC if your provider has a problem with it.
Click to expand...
Click to collapse
HTC will refuse to repair, and make you pay for repairs if you have TAMPERED or UNLOCKED or RELOCKED flags on your bootloader, they will shift all fault and blame onto you.
Seanie280672 said:
HTC will refuse to repair, and make you pay for repairs if you have TAMPERED or UNLOCKED or RELOCKED flags on your bootloader, they will shift all fault and blame onto you.
Click to expand...
Click to collapse
I guess if you have experienced this and or have been told this personally then you know. I'm looking at the htcdev site that says "not all claims... May be covered under warranty." it's worth a try if you can't resurrect it.
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Sean1971 said:
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Click to expand...
Click to collapse
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
alray said:
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
Click to expand...
Click to collapse
Great thanks for your help, I will give that a try today.
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Sean1971 said:
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Click to expand...
Click to collapse
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
alray said:
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
Click to expand...
Click to collapse
Thanks for your help, really appreciate it. See I said I was out of my depth ....
I tried Toweroot and that wouldn't work for my device, so then tried Kingroot and that sorted it so I was able to run Sunshine and I now have it S-OFF and Unlocked, I can now try to get it back to stock and get it network unlocked.
i attempted to unlock bootloader on my wife's old HTC M7 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
<<<I NOW KNOW WHAT THE ISSUE WAS, I WAS FLASHING RECOVERY FROM THE HTC M8, NOT M7>>>
any ideas?
gjw00 said:
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
Click to expand...
Click to collapse
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
Click to expand...
Click to collapse
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
alray said:
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
gjw00 said:
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
Click to expand...
Click to collapse
You can extract a firmware.zip (not an ruu) from an ota update and flash it to restore the stock recovery. You must use the right version. Waiting for your fastboot getvar all.
Sent from my HTC One using XDA Labs
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
gjw00 said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
7.21.980.51 is the latest version for vodap021 and can't find a 7.21.980.51 firmware.zip or ota.zip.
At least there is a 7.21.980.51 ruu on ir-file.com, bad news is that you must register to this website to be able to download (20$ for 30 days)
http://ir-file.com/show.php?token=32375
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
gjw00 said:
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
Click to expand...
Click to collapse
Yes, if you can capture the ota this is the best option (because its free). Look in your /download folder, you're looking for a long file name starting with "OTA_M7_UL_L50_SENSE60" and ending with ".zip". Save it on your computer and extract the "firmware.zip" file from it. Then reboot in RUU mode and flash the firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you should be able to unlock again.
it worked! thank you..